OutboundEngine and Salesforce
If you're new to PieSync, this guide will you get started with the essentials.
When you sync OutboundEngine with Salesforce, you can customize the following three elements to your sync.
- Sync direction
- Connection rules
- Field mappings
There is no one typical use case, no one best practice that can be documented to sync Salesforce and OutboundEnging. We'll provide various different tips, rules, and field mappings for you to draw inspiration from. You don't have to use them all!
It starts by choosing the direction of your sync. Depending on how OutboundEngine and Salesforce are implemented in your org, you can consider three different settings.
- Most customers opt for a two-way sync, allowing records to be modified by PieSync in either system. This is the setup we see most commonly as it would enable contacts to move from Salesforce into OutboundEngine as well as the other way round.
- You could choose for a strict one-way sync. Imagine you only want to sync certain OutboundEngine contacts tagged in a certain way move into Salesforce. You don't want data flowing back. Ever.
- Of course there's the opposite way too. For example, a Salesforce Audience can define which data can move into OutboundEngine to become contacts there. We will cover more possible filters in the next part on Rules.
On to the connection rules. These define which contacts are in scope of the sync. In a secondary use case, rules are capable of translating Salesforce states into OutboundEngine states or vice versa. Rules come with filters and actions.
With this setup, PieSync would create in OutboundEngine any newly created Salesforce contacts (1), as well as in fact create any existing OutboundEngine contacts (2). Once they are created or identified, it would update and keep those contacts in continuous sync (3). It would do the same in the other way round, requiring PieSync to identify which contacts are potentially already present in both systems.
Underneath the rules, we give you some easy toggles to play around with to tweak your connection even more.
Only sync contacts with an email address
'Avoid Duplicates' is enabled in the configuration set-up so that PieSync will only sync contacts that have an email address. We use the email address as the main identifier for a contact in order for us to prevent creating duplicates and to match and enrich contacts where possible in both applications.
Default field mappings
The field mapping defines how contacts will sync. A huge time & lifesaver in PieSync is that most of these are automatically set for all basic contact fields that Salesforce & OutboundEngine share by default.
Typically it's best to keep these default field mappings all activated as they represent the essential contact attributes that you would not want to grow out of sync in any circumstance.
Customizable field mappings
Field mapping also includes ability to include the mapping of Number of children, a field that can be created in OutboundEngine as well. Mappings are fully customizable not only before setting up a new sync, but it can also be modified for an ongoing sync.
PieSync syncs more than just OutboundEngine
Being able to sync Salesforce with OutboundEngine aids in frictionless selling because it keeps the underlying contact data in sync, and saves time in manual import/export operations.
That ease of use & data consistency comes in handy as well when syncing contacts to a billing app, or a secondary CRM, a VOIP system, or even another dedicated marketing platform.
PieSync is not only a turnkey solution to sync Salesforce and OutboundEngine exclusively. In fact, it solves a data problem that goes beyond these two apps. On average, users tend to connect 3-4 applications all through PieSync.