Lead Routing Basics for Pardot Admins: A Strategy Guide

 

This session covers the essential lead routing capabilities within Pardot and Salesforce, providing admins with a framework to strategize and implement robust lead assignment processes, emphasizing data integrity and system alignment.

Key Takeaways

 

• Data is Key: Before setting up any routing, you must first map your entire data flow to understand all connected systems and potential data conflicts (e.g., picklist value formatting).

• New Only: Pardot can only assign owners to net new Leads/Contacts. It cannot reassign an existing record; any subsequent ownership changes must happen in Salesforce.

• Mixed Methods: You are not limited to one routing method; you can use any combination of Pardot features (Engagement Studio, Completion Actions) and Salesforce features (Assignment Rules, Queues).

• Sync Queue is Critical: Regularly checking the sync queue is mandatory for any Pardot Admin to quickly identify and resolve data disagreements between Pardot and Salesforce.

Phase 1: Data Flow Review

 

The first step in planning lead routing is to understand exactly how data enters and flows through your system.

The Reality of Data Flow

 

While marketers often think data simply flows from a form to Pardot to Salesforce, the reality is much more complex. Data can flow from various sources, including manual imports, AppExchange integrations, customer support systems, partner portals, and event platforms (like Zoom or On24).

Questions to Guide Your Strategy

 

• Source Documentation: Document every avenue leads are coming from (forms, APIs, imports) to create a comprehensive data flow map.

• Source of Truth: Is Salesforce intended to be the source of truth for all leads, or does Pardot hold unqualified prospects?

• Sync Health: Is anything currently stuck on the sync queue (disagreements between Pardot and Salesforce data)?

Phase 2: Database Health Check

 

A healthy database is crucial for effective routing. Use the Pardot UI to quickly identify orphaned or unassigned records.

• Orphaned Prospects (Not in Salesforce): Filter the prospect list for “Prospects not in Salesforce.” These records are sitting in Pardot but have never been pushed to Salesforce.

• Unassigned Prospects: Filter the list for “Unassigned prospects.” Even if a record is synced, it may not have an owner if routing rules weren’t set, or if the previously assigned user is inactive. Admins must have a process to reassign records from inactive sales reps.

• Sync Errors: Check Pardot Settings > Connectors > salesforce.com to find the section on Sync Errors. A high number of errors (e.g., tens of thousands) indicates severe, ongoing data disagreement issues (e.g., duplicates, picklist mismatches, field type conflicts) that must be resolved.

Phase 3: Lead Routing Mechanisms

 

You can mix and match any of these Salesforce and Pardot features to achieve your desired routing logic.

Salesforce Components (Fastest Options)

 

• Queues: A waiting room built in Salesforce and mapped to Pardot. Multiple reps are assigned to the queue, and they claim new leads. This is ideal for collective ownership.

• Lead Assignment Rules: A layered funnel set up in Salesforce. Leads that match the top layer are assigned and exit the funnel. This is the fastest routing solution, ideal for organizations with strict Service Level Agreements (SLAs) under five minutes.

• Users: Assigning directly to one mapped Salesforce user.

Pardot Components (Flexible Options)

 

• User Groups (Round-Robin): A group assignment system that distributes new leads evenly in a sequential, round-robin manner. This is built specifically on the Pardot side.

• Completion Actions: Assignment logic applied directly to an individual form or file. This offers the most flexibility per asset. The con is that the admin must remember to set it up every time the asset is created or cloned.

• Automation Rules: Global rules that apply across the entire Pardot instance, regardless of the source. Quick global approach. The drawbacks are the limited number of active rules per account and the inability to control the precise order of operation if multiple rules could apply.

• Engagement Studio: A visual, flow-based approach that uses steps to assign leads based on branching logic (region, product, etc.). It is great for complex or prioritized routing and is very visual for order of operations. Con: It is the slowest option and the most time-consuming to set up.

Phase 4: Strategy Questions Before You Build

 

Before implementing the build, answer these questions to ensure system alignment and scalability:

• Ownership: Who officially owns the responsibility for maintaining the routing logic (Sales, Salesforce Admin, Marketing)?

• Sales Structure: Is the sales organization divided by region, territory, or product? The routing solution must align perfectly with this structure.

• Restructuring Frequency: If territories are restructured often, it is generally better to keep the complex logic in Salesforce (Assignment Rules) for easier editing and agility.

• Lead Volume: What is the average lead volume? This dictates whether you need to use User Groups to distribute the load evenly or if direct assignment is appropriate.

• User Mapping: Are all required sales users mapped and active in Pardot? If not, the records cannot be assigned and will become unassigned prospects.