Import Data Into Pardot or Salesforce First?

November 18, 2022
Lead Management, Salesforce and Pardot, Salesforce Ben | The Drip

Should you import data into Pardot (Account Engagement), or Salesforce? In some scenarios, the answer will be clear, as one option will offer the functionality you need for a successful import. However, you’ll discover that there are different opinions on the topic – and that most of the time, the answer is up for debate.

Both Pardot (Account Engagement) and Salesforce have their own import tools – Pardot with its simple prospect import, and Salesforce with Import Wizard, Dataloader, among others.

So where should you import the data from events, purchased data, paid ads, etc.? Plenty has changed in the past few years, with additional considerations you previously didn’t exist. We weigh up each option – the ideal use cases, pros, and cons – to help you decide what’s best for your import.

The Case for Pardot Import

“Clients often use Pardot and Salesforce back to front. When new, unqualified prospect data is obtained, the prospect is often pushed into Salesforce first, assigned and then synced back towards Pardot. Salesforce becomes very busy with unqualified and incomplete lead records”
Tom Ryan, Founder, MarCloud Consulting.

There are a few good reasons why this should be avoided:

More effort for salespeople: Unqualified and incomplete lead records make a salesperson’s job harder because they have to sift through data, trying to distinguish between the quick wins and the untouched data.
Breeds a bad organizational culture: Sales will begin to not trust marketing qualified leads (that marketing have actually handed to sales), with the assumption that leads are merely a dumping ground.
Skews metrics: Lesser-known is how it impacts reporting stats in the Pardot lifecycle report and the velocity chart. These reports enable data-driven decisions. By uploading data into Salesforce first as an assigned lead, this causes Pardot to believe that the prospect has already achieved MQL status. As a result, the lifecycle report will increase the number of MQLs and the velocity chart will show an untrue Prospect > MQL conversion time.

Above: Pardot velocity chart. If it doesn’t look right, it probably isn’t.

The diagram below illustrates the journey new data should go through – with new prospect data always going straight into Pardot. Eventually, the prospect will tip over the lead qualification threshold (and only then) are they assigned to a user, automatically pushed to Salesforce.

Qualified leads can be worked by sales. Marketing can keep track of what’s going on because of the connector’s two-way sync. Once sales open an opportunity, this triggers the SQL status in Pardot. Campaign Influence will credit marketing for a share of the opportunity amount when the opportunity is closed won.

The Case for Salesforce Import

“Marketing is not an isolated business function. Instead, it’s a team that has to work ‘in sync’ with the rest of your organization. The simplicity of Pardot that we all appreciate, can quickly turn into its nemesis – especially when pitted against its big brother, Salesforce.”
Lucy Mazalon, former Pardot/Salesforce consultant, Founder, The DRIP.

The benefits raised for Pardot import are perfectly true, for businesses that are lean (marketing processes) and clean (databases).

Unfortunately, there is rarely a ‘one size fits all’ answer, which is the crux for uploading data into Salesforce.

Field-level validation: Validation rules are measures that are put in place to improve data quality. Field-level validation in Salesforce can be more tightly defined; the result is that data input into Salesforce is more thoroughly validated. Pardot’s simplistic checkbox setting ‘Validate this field on Import’ cannot rival Salesforce’s granularity. While this could be manageable in smaller teams who all understand their organization’s data standards, it’s not fail-safe. Resulting connector sync errors will throw a spanner in the works.

Deduplication: Similar to validation, Salesforce has more granular matching and duplicate rules to catch records that your organization considers duplicate. I’ve seen examples where a prospect syncs to Salesforce and creates a new lead, even when this individual exists in your database already (with a missing email, therefore, wasn’t known to Pardot). Allow Multiple Prospects with Same Email Address (AMPSEA) has complicated the picture. In swapping email address for CRM ID as the unique identifier in Pardot, “deliberate duplicates” can now sync to Pardot. You can imagine how you could go around in a nasty cycle if accidental duplicates aren’t caught in time.

Multiple data entry points: No doubt that your organization has an array of data entry points. To maintain data standards across systems, organizations choose a Salesforce-first approach when uploading masses of new data – this establishes the baseline of record completeness, etc.
Data compliance: Stricter controls have been enforced for data processing and storage. Pardot (and other platforms) as entry points reduces the risk of rogue data handling, such as storing non-consented personal information, or modifying records illicitly.
Types of enquiries: Not all leads are sourced by marketing. Inbound phone or email enquiries picked up by sales are going to touch Salesforce first, manually entered as lead records.
Campaign association: Uploading data straight into the Salesforce Campaign e.g. from an event, will be associated with the correct campaign. While this is possible from Pardot (via automation rules) it’s additional data admin that might slip people’s minds. If overlooked, this will make Campaign Influence reporting inaccurate, therefore missing out on the chance to prove marketing influence on the pipeline. Each campaign touchpoint should be associated with a Salesforce Campaign; if the prospect isn’t a Lead/Contact in Salesforce, they cannot be related as Campaign members.

Complex segmentation: Pardot segmentation tools cannot take every Salesforce object into consideration. Even with Pardot custom objects, the segmentation options are limited. Salesforce reports can be used for granular segmentation – including cross filters (that identify records with or without a related record).
B2B Marketing Analytics: On the topic of reporting, data reaches B2B MA via the Salesforce connector. The prospect data is packaged into datasets that are used for more powerful visualizations.

Tip: Hide Prequalified Data

To address the unqualified and incomplete records that clutter a salesperson’s workspace, use list views to show only relevant records to salespeople.

List views are simple to create, for example, ‘My Qualified Leads’ you can quickly add filters such as score >100, and/or grade A or higher.

Another option is to assign prequalified prospects to queues, which act as holding areas in your CRM, where records wait for someone to pick them up (or marketing to move), before they are assigned a specific record owner.

Import Data Into Pardot or Salesforce?

As we said, there is rarely a ‘one size fits all’ answer. Plenty has changed in the past few years, with additional considerations you previously didn’t exist. Your Pardot-Salesforce relationship may still fit the “ideal” prospect lifecycle, but there are numerous ways it doesn’t.

Pardot Import: Pros and Cons

✅ Easy to use interface.

✅ Accurate insights from the Pardot Lifecycle and velocity reports.

✅ Puts you into a good practice of leveraging Pardot forms.

❌ Connector sync errors can be caused by Pardot having more “loose” validation and deduplication capabilities.

Salesforce Import: Pros and Cons

✅ Stricter data validation and deduplication leads to less sync errors (if new Pardot data were to fail Salesforce’s standards when attempting to sync).

✅ Adheres to the baseline data standards, as Salesforce is typically the “source of truth” for multiple integrated platforms.

✅ Campaign association (multi-touch attribution) leads to better Salesforce Campaign Influence reports.

✅ Include more objects, and different object relationships (e.g. by using cross filters) with Salesforce reports, vs Pardot’s segmentation capabilities.

❌ Salesforce import tools come with a steeper learning curve.

❌ You may not have access to the data import tools (controlled by the Salesforce admin).

❌ Unqualified and incomplete lead records clutter Salesforce, unless you adjust the views that salespeople are working with (e.g. list view filters).

This Pardot article written by:

Salesforce Ben | The Drip

Lucy Mazalon is the Head Editor & Operations Director at Salesforceben.com, Founder of THE DRIP and Salesforce Marketing Champion 2020.

Original Pardot Article: https://www.salesforceben.com/the-drip/import-data-into-pardot-or-salesforce/

Find more great Pardot articles at www.salesforceben.com/the-drip/

Pardot Experts Blog

We have categorized all the different Pardot articles by topics.

Salesforce Ben | The Drip

Lucy Mazalon is the Head Editor & Operations Director at Salesforceben.com, Founder of THE DRIP and Salesforce Marketing Champion 2020.

Original Pardot Article: https://www.salesforceben.com/the-drip/import-data-into-pardot-or-salesforce/

Find more great Pardot articles at www.salesforceben.com/the-drip/

Import Data Into Pardot or Salesforce First?

The Case for Pardot Import

The Case for Salesforce Import

Tip: Hide Prequalified Data

Import Data Into Pardot or Salesforce?

Pardot Import: Pros and Cons

Salesforce Import: Pros and Cons

Salesforce Ben | The Drip

Pardot Experts Blog

Pardot Topic Categories

More Pardot Articles

Data Cloud & Account Engagement – What you need to know

Marketing Cloud Growth vs Account Engagement (Pardot)

Summer ’24 Broke Lead Assignment Notifications in Account Engagement

Using Engagement Studio Programs for Lead Assignment

How to generate content with Einstein Assistant in Pardot

Increase productivity with Sales Engagement Basic

Account Engagement’s Email Builder – New Email Experience

How to work with Person Accounts in Pardot

Salesforce Ben | The Drip

Pardot School