Using most recently updated record values
Posted: Sun Dec 22, 2024 8:54 am
When using the most recently updated record values, once again the same theory applies but based on which platform is most recent.
If the values between Salesforce and Pardot are in conflict once synced, it will take into account which platform is using the most recently updated record.
However, if a value in Salesforce is empty and isn’t in Pardot but Salesforce has the most recently updated record, Pardot’s value will overwrite the empty value in Salesforce. This should now be making sense to why and how this is the case.
As this can constantly change, depending phone number in cambodia on your users’ input, there are some good examples of when to use this setting, such as:
You are not confident about which platform you consider to be a master.
When phone numbers are changing constantly.
Your network of users are spread geographically and interacting with the same data.
Scenario example
To thank your VIP clients, each year you buy them a gift at Christmas. In order to tailor to their likes and interests you create a custom field to input what you pick up through conversations throughout the year. A marketing user sets the ball rolling by adding BEER into the field and both systems update. Middle of the year approaches and a sales user speaks to them and updates the field to FINE WINE and both systems once again update. A few weeks prior to purchasing, a marketing user then changes this because the key client has emailed in and says CHEESE. The field is updated to become CHEESE in Pardot and both systems update. The team gathers up the data and purchases a delightful cheese board for their VIP client.
In this scenario there is no need for an IF layout as both platforms had been syncing since the start of the year and the use of team collaboration led to knowing what exactly the client wanted, whether it was at the start, middle or prior to Christmas.
A great and simple approach of data being collected throughout the process by both teams, that may indeed generate new business.
Exceptions for sync behaviours
There are some exceptions that sync behaviours take into consideration, some exist in proprietary fields, fields that relate to the prospect (owner).
Email address
As the relationship between the CRM and Pardot is 1:1 it is advised to have one email address. In order to become a prospect, Pardot requires a number of fields, one being email address. As this is key to a prospect’s record this can’t be changed and the sync between the two will always use Pardot’s value.
However, if you have a number of employees that use the same email address within your platform then an alternative option may need to be considered. To allow multiple prospects with the same email address you must select the option: automatically change email addresses in Pardot to reflect changes in Salesforce, this is found in the Salesforce-Pardot Connector Settings.
Opted out/do not email
This is an important feature, especially given GDPR regulations. If a prospect has opted out, which sync value takes president?
When the opted-out field is selected on a prospect’s record, both platforms will regress and change to a preferred value. Admins can override this but of course, it is not advised.
The nuances of Pardot to Salesforce sync behaviours can be a challenge for many users. Hopefully, this post has helped you to better understand how syncs behave and the control you have over these settings.
If you’re experiencing sync errors or would like technical support from a team of Pardot specialists you can contact us for a chat.
If the values between Salesforce and Pardot are in conflict once synced, it will take into account which platform is using the most recently updated record.
However, if a value in Salesforce is empty and isn’t in Pardot but Salesforce has the most recently updated record, Pardot’s value will overwrite the empty value in Salesforce. This should now be making sense to why and how this is the case.
As this can constantly change, depending phone number in cambodia on your users’ input, there are some good examples of when to use this setting, such as:
You are not confident about which platform you consider to be a master.
When phone numbers are changing constantly.
Your network of users are spread geographically and interacting with the same data.
Scenario example
To thank your VIP clients, each year you buy them a gift at Christmas. In order to tailor to their likes and interests you create a custom field to input what you pick up through conversations throughout the year. A marketing user sets the ball rolling by adding BEER into the field and both systems update. Middle of the year approaches and a sales user speaks to them and updates the field to FINE WINE and both systems once again update. A few weeks prior to purchasing, a marketing user then changes this because the key client has emailed in and says CHEESE. The field is updated to become CHEESE in Pardot and both systems update. The team gathers up the data and purchases a delightful cheese board for their VIP client.
In this scenario there is no need for an IF layout as both platforms had been syncing since the start of the year and the use of team collaboration led to knowing what exactly the client wanted, whether it was at the start, middle or prior to Christmas.
A great and simple approach of data being collected throughout the process by both teams, that may indeed generate new business.
Exceptions for sync behaviours
There are some exceptions that sync behaviours take into consideration, some exist in proprietary fields, fields that relate to the prospect (owner).
Email address
As the relationship between the CRM and Pardot is 1:1 it is advised to have one email address. In order to become a prospect, Pardot requires a number of fields, one being email address. As this is key to a prospect’s record this can’t be changed and the sync between the two will always use Pardot’s value.
However, if you have a number of employees that use the same email address within your platform then an alternative option may need to be considered. To allow multiple prospects with the same email address you must select the option: automatically change email addresses in Pardot to reflect changes in Salesforce, this is found in the Salesforce-Pardot Connector Settings.
Opted out/do not email
This is an important feature, especially given GDPR regulations. If a prospect has opted out, which sync value takes president?
When the opted-out field is selected on a prospect’s record, both platforms will regress and change to a preferred value. Admins can override this but of course, it is not advised.
The nuances of Pardot to Salesforce sync behaviours can be a challenge for many users. Hopefully, this post has helped you to better understand how syncs behave and the control you have over these settings.
If you’re experiencing sync errors or would like technical support from a team of Pardot specialists you can contact us for a chat.