First-party tracking with Pardot means two things that happen in different places: the click is captured and the Lead is sent to Meta from the server that renders your landing page, while Pardot keeps the record, the owner and the pipeline stages. Pardot sits after the form submission, so the cookie and the identifiers have to exist before the lead ever reaches it.
Where each piece lives
| Step | Where it happens | What it holds |
|---|---|---|
| Click on the ad | your landing page domain | fbclid in the URL, ad ID in the parameters |
| Cookie set | the HTTP response that renders the landing page | a first-party HttpOnly click cookie, no redirect |
| Form submitted | the same server | the lead record and a lead ID |
| Lead sent to Meta | that server, through the Conversions API | event_id, hashed email and phone, fbc, fbp, IP, user agent |
| Lead becomes a prospect | Pardot | contact data, custom fields for the IDs, owner, stage |
| Stage sent back | an integration on the Pardot side | one event per stage change, with a match key |
The order explains the usual failure. Teams ask Pardot for better attribution, and Pardot has nothing to give, because the click data was never stored on the domain that could keep it.
1. Set the click cookie on your own domain
WebKit’s tracking prevention treats cookies by who writes them. A cookie created by JavaScript is deleted after 7 days without interaction with the site, and when ITP detects a click ID in the URL, cookies that JavaScript creates on that landing page are capped at 24 hours. fbclid is a click ID.
A cookie set in an HTTP response escapes those caps, unless the request goes to a subdomain that resolves through a CNAME to a third party, or to a third-party IP address. Then it is capped at 7 days as well.
That is why a server-side tag manager on a subdomain can still lose the click while a cookie set by the landing page host keeps it. Serve the landing page from your own domain, set a first-party HttpOnly cookie in the same response that renders it, and skip the redirect hop that would start a new request context. The rules are laid out in server-side tracking for Facebook ads.
2. Put the identifiers on the prospect
A lead that reaches Pardot with a name, an email and nothing else is a contact. A lead that reaches it with the ad ID and Meta’s lead ID is a cost per lead with a creative behind it.
Store these as custom fields, in text format:
- Meta’s lead ID, from the form or the Graph API read.
- The ad ID, and the ad set and campaign IDs if you report at those levels.
fbclid, as captured on the click, kept for audit.fbcandfbp, the values Meta expects unhashed.- The form ID, when several forms feed the same Pardot instance.
Text matters. A numeric field turns a long identifier into a rounded one, and every later match fails quietly.
If your forms are Pardot-hosted, the same rule applies one level up: Pardot’s form handler receives the POST on your domain, so make sure the handler passes the hidden fields into the prospect record instead of dropping them.
3. Send the Lead from your server
The Conversions API call is small and specific. For a Lead from a landing page form, send:
event_nameset toLead,action_sourceset towebsite;event_id, which should be the lead ID your server created;- email and phone, normalized and hashed with SHA-256;
fbcandfbp, not hashed;- the visitor’s IP address and user agent, not hashed, captured at submission;
- an
external_id, where Meta recommends hashing.
If the Pixel also fires, give it the same ID: fbq('track', 'Lead', {}, { eventID: 'lead_7f3a91' }) in the browser and the same string as event_id on the server. Meta keeps one copy when the event names and the IDs match and both arrive within 48 hours. Without a shared ID, one lead counts twice and the CPL in Ads Manager looks better than it is.
The order of work is worth repeating: let the server create the lead first, use its ID as event_id, and pass the same ID to the browser. A server that sends the Lead the moment the form arrives usually beats the browser event, and deduplication on fbp or external_id generally works only when the browser copy comes first.
4. Get the leads into Pardot
Before you build anything, search Meta’s CRM directory on the Instant forms screen, CRM setup tab. If Pardot appears there, connect it from Business Suite and map the fields. If it does not, you have three routes: middleware such as Zapier or Make, a webhook of your own, or a scheduled Graph API read.
A webhook is the shortest path to Pardot with the IDs intact, because the payload tells you which ad, form and Page produced the lead before anything else touches it. The setup needs a Meta app, App Review for the lead ads permission, Business Verification, and a token whose owner holds leads access. The step-by-step version is in setting up a Facebook lead ads webhook.
Whichever route you use, mind the window: Meta keeps Instant Form leads downloadable for 90 days, and a route that depends on someone remembering an export loses everything after that.
5. Send stages back to Meta
The stage events are what make the qualified leads goal usable, and since April 2026 new campaigns need a Conversions API integration for it.
- Send one event per stage change, starting with the raw lead.
- Keep
event_timeafter the lead was created and no more than 7 days before you send it. - Keep batches small: a single bad event discards the whole batch.
- Upload at least daily, and send every change, not just the latest stage.
- Validate with at least 7 days of data and at least two funnel stages.
Size the job by changes, not by leads. A lead that moves through several stages produces one event per move, so the volume your integration posts is a multiple of the lead count, and it climbs exactly when the pipeline is working.
What this does not fix
- Consent. Meta says the Conversions API is not designed to bypass App Tracking Transparency or the ePrivacy Directive, and server events follow the same opt-outs as Pixel events.
- Attribution windows. Server events are attributed under the same setting as Pixel events.
- Modelled conversions. Meta may still model where data is partial.
- Events with no identifiers. An event Meta cannot match to an account is attributed to nobody.
The rest of the questions on this, from match quality scores to deduplication tests, are collected in Meta Pixel, Conversions API and attribution, and the browser half of the setup is in Meta Pixel setup.
DropCPL takes the part Pardot cannot do: the landing page is served from the tracking domain, the click cookie is first-party and HttpOnly in the same response, and each lead goes to Meta server-side with the ad and the landing page attached, so the record Pardot receives already carries the IDs the pipeline needs.