---
title: Embedding registration with ad-click tracking
description: Forward ad click and UTM parameters from your website into an embedded DistantRace registration form
order: 3
---

# Embedding registration with ad-click tracking

If an ad sends participants to your own website, its click parameters land on that page rather than on distantrace.com. An embedded DistantRace registration form needs the ad-click tracking snippet to receive those parameters.

## Copy the tracking embed

**Path:** Console → competition → Settings → competition settings page → **Iframe Embedding** card

Copy **Registration embed with ad-click tracking** and use it **instead of** the plain registration iframe.

The snippet builds the iframe and forwards these ten allowlisted parameters from your website's page URL into the embedded form:

- `gclid`, `wbraid`, `gbraid`, `fbclid`, `msclkid`
- `utm_source`, `utm_medium`, `utm_campaign`, `utm_term`, `utm_content`

Without this snippet, ad click data from the page containing the iframe does not reach DistantRace.

<!-- Screenshot placeholder: Capture the Iframe Embedding card on a demo competition settings page. Show the plain registration iframe and the Registration embed with ad-click tracking snippet so organizers can distinguish them. Exclude real event or organization secrets if any are present. -->

## Ads that link directly to DistantRace

You do not need the snippet when an ad links directly to a DistantRace event page. DistantRace captures allowlisted parameters from that URL automatically and keeps them through login and payment for up to 24 hours.

The data remains bound to the organization whose page the participant landed on. The first capture attached to an order wins.

## For your marketing agency: verify the setup

1. Open the page that contains the embed with `?gclid=TEST123&utm_source=google` added to its URL.
2. In the browser developer tools, confirm that the iframe URL contains both parameters.
3. Complete a paid online test registration after accepting marketing cookies. In Google Ads, confirm that the conversion uses the DistantRace order code as its transaction ID.
4. Fetch the [conversion feed URL](conversion-feed-and-attribution-exports.md) and confirm that it contains the expected header and a data row.

<!-- Screenshot placeholder: Capture browser developer tools on the test host page. Show the host URL containing gclid=TEST123 and utm_source=google and the embedded iframe URL carrying both parameters. Crop out unrelated requests, account data, and any feed token. -->

## Privacy and consent

DistantRace's privacy policy describes this processing in section 3.12, **advertising campaign attribution data**. The browser conversion tag fires only when the participant accepted marketing cookies.

Attribution is limited to the ten parameters above, the landing page path, and capture time. It does not include names, email addresses, or other personal details.

## Related

- [Google Ads conversion tracking for your event](index.md)
- [Conversion feed and attribution exports](conversion-feed-and-attribution-exports.md)
- [Embed domains for iframes](../embed-domains-for-iframes.md)