Will data cross over between Business Units?
Posted: Sun Dec 22, 2024 5:28 am
The default behaviour for prospects is to have a 1-1 relationship with Leads/Contacts. This obviously means that the default setup won’t work well for businesses that have lots of crossover between Business Units because it will create duplicates. I’m sure you’ll agree, we do not like duplicates.
If there is absolutely no crossover between PBU’s then good for you, things are a bit simpler.
If not, we need to configure Business Units phone number cambodia accordingly because we want that single view of the customer. We’ll need to amend the sync behaviour because we still want the score, Scoring Categories, and grades to appear on the Lead/Contact!
This will require custom development work so definitely make sure you have resources for this. The gist is:
We need to stop Pardot from syncing the packaged fields.
We’ll then lean on Marketing Data Sharing settings (it’s okay if there’s crossover between PBU’s, that’s expected).
We need to create a Custom Object in Salesforce for use on the Lead/Contact to show the marketing information and use the Pardot Export API to sync prospect field values from different Business Units.
Once configured properly, we will be able to see different scores/Scoring Categories/grades from each PBU!
Business Unit Switcher
The Business Unit switcher will allow users who have access to more than one Business Unit, to easily jump between these. It sounds simple, right?
When you do this, a number of things change on the Salesforce side. Taken from Salesforce documentation, the data that changes upon switching is:
Lead and Contact Visualforce pages
AddToPardotList
EngageCampaignsContactRecord
EngageCampaignsLeadRecord
Marketing Action Summary Contact
Marketing Action Summary Lea
Pardot Activities
Pardot List Membership
Pardot Social Data
SendPardotEmailContact
SendPardotEmailLead
Lightning actions and components
Send Engage Email (shows only the templates associated with the current business unit)
Add to Nurture Lightning (shows only the lists associated with the current business unit)
Send to Pardot (sends leads and contacts to the current business unit)
Send Pardot Email (shows only the templates associated with the current business unit)
Engagement History related lists and Lightning component (shows only the activities associated with the current business unit)
The easiest way to think about the above is what data is stored in Pardot?’ and that’s the data that will change.
Example of Business Switcher
Go forth and plan…
When it comes to successfully implementing Pardot Business Units, there’s still more to talk through, like B2B Marketing Analytics and Pardot Einstein but I hope this Pardot Business Units implementation guide has answered a lot of your questions! You should now be able to plan the ideal PBU setup for your business.
If you want to talk about Pardot Business Units for your company, then please get in touch, we love stuff like this.
If there is absolutely no crossover between PBU’s then good for you, things are a bit simpler.
If not, we need to configure Business Units phone number cambodia accordingly because we want that single view of the customer. We’ll need to amend the sync behaviour because we still want the score, Scoring Categories, and grades to appear on the Lead/Contact!
This will require custom development work so definitely make sure you have resources for this. The gist is:
We need to stop Pardot from syncing the packaged fields.
We’ll then lean on Marketing Data Sharing settings (it’s okay if there’s crossover between PBU’s, that’s expected).
We need to create a Custom Object in Salesforce for use on the Lead/Contact to show the marketing information and use the Pardot Export API to sync prospect field values from different Business Units.
Once configured properly, we will be able to see different scores/Scoring Categories/grades from each PBU!
Business Unit Switcher
The Business Unit switcher will allow users who have access to more than one Business Unit, to easily jump between these. It sounds simple, right?
When you do this, a number of things change on the Salesforce side. Taken from Salesforce documentation, the data that changes upon switching is:
Lead and Contact Visualforce pages
AddToPardotList
EngageCampaignsContactRecord
EngageCampaignsLeadRecord
Marketing Action Summary Contact
Marketing Action Summary Lea
Pardot Activities
Pardot List Membership
Pardot Social Data
SendPardotEmailContact
SendPardotEmailLead
Lightning actions and components
Send Engage Email (shows only the templates associated with the current business unit)
Add to Nurture Lightning (shows only the lists associated with the current business unit)
Send to Pardot (sends leads and contacts to the current business unit)
Send Pardot Email (shows only the templates associated with the current business unit)
Engagement History related lists and Lightning component (shows only the activities associated with the current business unit)
The easiest way to think about the above is what data is stored in Pardot?’ and that’s the data that will change.
Example of Business Switcher
Go forth and plan…
When it comes to successfully implementing Pardot Business Units, there’s still more to talk through, like B2B Marketing Analytics and Pardot Einstein but I hope this Pardot Business Units implementation guide has answered a lot of your questions! You should now be able to plan the ideal PBU setup for your business.
If you want to talk about Pardot Business Units for your company, then please get in touch, we love stuff like this.