Track Facebook Ads in Pardot: a 4-step setup guide
Pardot can record Google Ads activity, but Facebook Ads activity does not arrive automatically. Without extra capture, a lead record shows who converted without showing which Facebook campaign, ad set or ad produced them. This guide explains how a website snippet, consistent UTM parameters and hidden form fields carry that information into Pardot, where it can be compared with other channels and carried through to opportunities, customers and revenue.
Why Facebook data is missing in Pardot by default
Pardot has built-in functionality for tracking Google Ads but nothing equivalent for Facebook Ads or other platforms, so Facebook-driven leads can look unattributed. The workaround is to capture the marketing source before the form is submitted and store it with the lead's contact details. A small website snippet does that work: it reads how the visitor arrived, categorises the visit into a standard channel, remembers the result in a cookie, and writes it into hidden fields when a form is completed. On submission, Pardot receives the attribution data alongside name, email and phone, making it available on the contact record and downstream in a CRM or BI tool.
Step 1: Install the snippet and add hidden fields
Install the snippet provided when the account is created. Depending on the website builder, it may be added through settings or through a tag manager such as Google Tag Manager. Then add five hidden fields to each relevant form: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3 and Channel Drilldown 4. Most form builders, including Pardot forms, Gravity Forms, Typeform and Jotform, support hidden fields, though the exact steps differ by builder. Check each form individually rather than assuming one form's setup covers the whole site.
Step 2: Tag Facebook Ads with UTM parameters
Add UTM parameters to every Facebook Ads destination URL so the arriving visit carries campaign detail. A consistent convention makes later reporting reliable: set UTM Medium to Paid Social, UTM Source to Facebook, UTM Campaign to the campaign name, UTM Term to the ad set name and UTM Content to the specific ad. Apply the same pattern across campaigns; changing the naming style between campaigns creates avoidable cleanup work later. Keep the values descriptive enough that a report reader can identify the campaign without opening Ads Manager.
Step 3: Let the snippet write attribution into the form
When a visitor arrives from a tagged ad, the snippet captures the UTM parameters and stores them in a cookie. As the visitor browses, the cookie retains the attribution, and if the visitor leaves and returns later it can still be present. When the visitor submits a form, the stored values are written into the hidden fields. For example, a visitor who clicks a Brand Campaign ad, lands on the homepage and requests a demo could produce Channel = Paid Social, Channel Drilldown 1 = Facebook, Channel Drilldown 2 = Brand Campaign, Channel Drilldown 3 = North America Ad Group and Channel Drilldown 4 = Green Ad. The same visit can also record the landing page URL and landing page group, such as a features page or a blog section, showing which content the ad sent the visitor to.
Step 4: Report on the data in Pardot and downstream
After submission, the Facebook Ads data derived from the UTM parameters appears in Pardot on the contact record next to the lead's other details. From there it can be passed to a CRM such as Salesforce or to a BI tool such as Tableau. That makes it possible to answer practical questions: how many leads came from Facebook Ads compared with Google Ads or SEO, how many opportunities and closed-won customers originated there, which campaigns produce the most opportunities, how close rates compare across sources, how much revenue was generated and what return ad spend produced. Before trusting reports, run a test submission from a tagged ad and confirm every hidden field arrives populated in Pardot.
What else the setup captures
Attribution is not limited to Facebook. The same setup records leads from other paid channels such as Google or LinkedIn Ads and from organic sources such as Organic Search, Organic Social and Direct, so channel comparisons use one consistent dataset. It also tolerates common UTM inconsistencies: if some campaigns use one spelling for a source and others use a variant, the visits can still be assigned to the correct channel, such as Paid Social. Landing page and landing page group capture adds a content view, showing whether blog or feature pages are converting the traffic they receive.
Three reports to build first
Three reports illustrate the value once data flows through. Leads by channel breaks lead volume down across all channels, revealing whether Facebook is outperforming or underperforming alternatives and where budget should shift. Customers by network separates results across Meta properties such as Facebook, Instagram, Messenger and WhatsApp, showing which network produces customers rather than only clicks. Revenue by campaign attaches revenue to each Facebook campaign; combined with spend, it shows which campaigns generate positive return and which do not.
Pre-launch checklist
Confirm the snippet is installed on every page with a form, not only the homepage. Confirm all five hidden fields exist on each form and use the exact expected names. Confirm every Facebook Ads URL carries the full UTM set using the agreed convention. Submit a test form from a tagged ad and verify the channel fields, landing page and landing page group in Pardot. Check that a visitor who browses several pages, or leaves and returns, still submits with the original attribution. Finally, build the three starter reports — leads by channel, customers by network and revenue by campaign — and review them before scaling spend.
| Hidden field | What it receives in the Facebook example | How to use it |
|---|---|---|
| Channel | Paid Social | Compare Facebook against search, organic and other channels |
| Channel Drilldown 1 | Identify the platform within the channel | |
| Channel Drilldown 2 | Campaign name, e.g. Brand Campaign | Report leads, opportunities and revenue per campaign |
| Channel Drilldown 3 | Ad set name, e.g. North America Ad Group | Compare ad sets within a campaign |
| Channel Drilldown 4 | Specific ad, e.g. Green Ad | Compare individual ads |
Values depend on the UTM parameters placed behind the ad; the example uses the recommended Facebook convention.
Frequently asked questions
Does Pardot track Facebook Ads natively?
Pardot is described as having built-in tracking for Google Ads but no equivalent built-in tracking for Facebook Ads or other advertising platforms, leaving Facebook performance unclear on the lead record.
Which hidden fields are needed on the form?
Add Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3 and Channel Drilldown 4 as hidden fields to the form that will receive the attribution data.
What UTM convention is recommended for Facebook Ads?
Use Paid Social for UTM Medium, Facebook for UTM Source, the campaign name for UTM Campaign, the ad set name for UTM Term and the specific ad for UTM Content.
Why does the data survive browsing before form submission?
Attribution details are stored in a browser cookie, so they persist while the visitor browses and can persist if the visitor leaves and returns later, before being written to the form on submission.
Where can the captured data be used after Pardot?
Once in Pardot, the data can be viewed on the contact record, sent to a CRM such as Salesforce, or connected to a BI tool such as Tableau for reporting.