Running ads to an embedded registration form
Running ads to an embedded registration form
If an ad sends participants to your website and the DistantRace registration form is embedded there, the ad parameters stop at your page. They do not enter a plain iframe.
Without the tracking embed, DistantRace has no click ID. Click-based attribution fails, and the Google Ads offline import has no click data to use. This is the most common reason tracking appears not to work on an embedded registration page.
Copy the tracked registration embed #
Path: Event → Settings → Embedding
- Find Registration embed with ad-click tracking.
- Use the provided Copy button.
- Replace the plain registration iframe on your website with the copied snippet.
- Give the snippet to the person or agency maintaining your website if you do not manage it yourself.
[SCREENSHOT: Event → Settings → Embedding showing Registration embed with ad-click tracking and its Copy button beside the plain iframe option]
Copy the snippet from your console. Do not recreate or retype it.
Parameters the snippet forwards #
The tracking embed forwards:
- Google:
gclid,wbraid,gbraid - Meta:
fbclid - Microsoft:
msclkid - TikTok:
ttclid - Campaign tags:
utm_source,utm_medium,utm_campaign,utm_term,utm_content
The captured snapshot is kept for 24 hours and tied to the organization whose page the visitor landed on. The first ad click that leads to an order is the one stored.
Consent still applies #
Forwarding ad parameters does not bypass cookie consent. Google Ads, Meta Pixel, TikTok Pixel, and Microsoft Advertising (UET) tags require marketing-cookie consent; GA4 requires analytical-cookie consent.