UTM Tracking for Tradedoubler: How to Build and Validate Affiliate Campaign Links

How Tradedoubler’s tracking architecture interacts with UTM parameters

Tradedoubler is one of Europe’s largest performance marketing networks, founded in Stockholm in 1999 and operating across more than 15 European markets including the UK, France, Germany, Sweden, the Netherlands, Spain, and Poland. It connects advertisers (merchants) and publishers (affiliates, content sites, cashback networks, coupon aggregators) across retail, travel, financial services, software, and subscription products.

When a publisher promotes an advertiser’s Tradedoubler program via an affiliate link, the click routes through Tradedoubler’s track.tradedoubler.com tracking infrastructure. Tradedoubler records the click event for commission attribution using its internal event tracking system, then redirects the browser to the advertiser’s configured destination URL. Tradedoubler’s tracking system — which handles click recording and commission payouts — operates entirely separately from GA4 UTM tracking and does not depend on or interfere with UTM parameters.

The consequence for UTM tracking: UTM parameters belong on the destination URL you configure in the Tradedoubler advertiser portal for your program, not on the publisher-facing tracking link. The Tradedoubler publisher link is formatted and controlled by the platform; the destination URL is the configuration point you control as an advertiser. Paste the UTM-tagged destination URL generated by mlz build into your Tradedoubler program settings.

GA4 attribution works by reading utm_source, utm_medium, and utm_campaign from the URL at the moment the GA4 measurement tag fires. For a Tradedoubler-driven visit, this is after track.tradedoubler.com redirects and your destination page loads in the browser. If any redirect between the Tradedoubler forward and the final page load strips query parameters, GA4 records the session as Direct or Organic with no Tradedoubler attribution. Tradedoubler itself still tracks the conversion for commission purposes using its own click attribution.

Both attribution systems coexist independently: Tradedoubler tracks publisher commissions through its own click records; GA4 tracks channel attribution through UTM parameters on the destination URL. For the full context of UTM parameters and redirect chain validation across affiliate networks, see the UTM tracking for developers guide.

Building Tradedoubler destination URLs with mlz build

The most common UTM data quality problem in Tradedoubler programs is casing inconsistency across multi-country program configurations: one market uses utm_source=Tradedoubler (capitalized), another uses utm_source=tradedoubler, and a third uses utm_source=trade-doubler. GA4 is case-sensitive and records these as three separate traffic sources, making it impossible to report total Tradedoubler network performance accurately across European markets. mlz build eliminates this by enforcing lowercase-hyphenated values from structured input, regardless of what the operator types.

The standard naming convention for Tradedoubler programs is utm_source=tradedoubler or utm_source=tradedoubler-[country-code] for country-specific segmentation, utm_medium=affiliate, and utm_campaign=[program-name-or-season]. Use utm_content to differentiate between different creatives or promotional periods within the same program configuration.

$ mlz build \
  --url "https://shop.example.com/landing" \
  --source "tradedoubler" \
  --medium "affiliate" \
  --campaign "summer-sale-2026" \
  --content "uk-program" \
  --validate

{
  "tracked_url": "https://shop.example.com/landing?utm_source=tradedoubler&utm_medium=affiliate&utm_campaign=summer-sale-2026&utm_content=uk-program",
  "params": {
    "utm_source": "tradedoubler",
    "utm_medium": "affiliate",
    "utm_campaign": "summer-sale-2026",
    "utm_content": "uk-program"
  },
  "destination_url": "https://shop.example.com/landing",
  "link_id": "lnk_td_uk_ss26",
  "campaign_id": "cmp_summer-sale-2026",
  "stored": true,
  "created_at": "2026-07-02T10:00:00.000Z"
}

The tracked_url value is what you paste into the Destination URL or Landing Page URL field in the Tradedoubler advertiser portal when creating or editing your program. For multi-market programs running separate Tradedoubler programs per country, generate a distinct destination URL for each market using a country-specific utm_content or utm_source value:

For naming conventions and how consistent casing prevents GA4 data fragmentation across affiliate sources, see the UTM naming conventions guide. To generate destination URLs programmatically across a large Tradedoubler multi-market catalog via the REST API, see how to build UTM links programmatically.

Validating the Tradedoubler redirect chain with mlz check

Once you have a UTM-tagged destination URL, validate it end-to-end with mlz check before entering it into the Tradedoubler advertiser portal. mlz check follows the complete redirect chain from your destination URL, confirms the server responds with a 200, and verifies query parameters are not stripped at any hop. Run this before your Tradedoubler program goes live, and re-run it after any infrastructure change that touches URL handling on your site — particularly important for multi-market programs where different country servers may behave differently.

$ mlz check "https://shop.example.com/landing?utm_source=tradedoubler&utm_medium=affiliate&utm_campaign=summer-sale-2026"

{
  "url": "https://shop.example.com/landing?utm_source=tradedoubler&utm_medium=affiliate&utm_campaign=summer-sale-2026",
  "valid": true,
  "checks": [
    { "check": "url_format", "status": "pass", "message": "URL format is valid." },
    { "check": "ssl", "status": "pass", "message": "URL uses HTTPS." },
    { "check": "resolution", "status": "pass", "message": "Destination responded with 200.", "details": { "status_code": 200, "response_time_ms": 198 } },
    { "check": "redirects", "status": "pass", "message": "No redirects detected." },
    { "check": "response_time", "status": "pass", "message": "Response time: 198ms.", "details": { "response_time_ms": 198 } }
  ],
  "status_code": 200,
  "response_time_ms": 198,
  "validated_at": "2026-07-02T10:01:15.000Z"
}

A valid: true result means the destination URL resolves correctly and query parameters survive to the final page load. If valid is false, the checks array pinpoints the failing hop. The most common failure modes for Tradedoubler programs are GDPR consent management platform redirects, CDN geo-routing rules that behave differently per country, and e-commerce platform canonical URL enforcements. For a detailed walkthrough of diagnosing redirect chain failures, see how to check if a redirect strips UTM parameters.

Tradedoubler UTM tracking gotchas for advertisers

Configure UTM parameters on the destination URL, not on the Tradedoubler publisher link

Tradedoubler generates publisher-facing tracking links in a format controlled by the platform. As an advertiser, you do not directly control the structure of the publisher link. The configuration point you own is the Destination URL or Landing Page URL in the Tradedoubler advertiser portal for your program. Paste the UTM-tagged URL generated by mlz build there. When a publisher’s Tradedoubler link is clicked, the network routes through track.tradedoubler.com and forwards to your configured destination URL, delivering the UTM parameters to your landing page.

GDPR consent management platforms can redirect and strip query parameters

Advertisers operating in European markets often implement a GDPR consent management platform (CMP) as a pre-landing-page redirect: the visitor is shown a consent screen before reaching the product page. Some CMP implementations handle this redirect without forwarding the original query string, meaning UTM parameters present in the Tradedoubler destination URL are stripped before GA4 fires on the actual product page. This is particularly common with iframe-based or server-side CMP implementations. Test your destination URL with mlz check to confirm parameters survive the full chain, including any CMP redirect layer.

CDN geo-routing rules behave differently per country and can affect query parameter handling

Tradedoubler advertisers running multi-market programs across Europe often use CDN geo-routing to direct UK visitors to /uk/ paths and German visitors to /de/ paths. These CDN routing rules sometimes implement URL normalization that strips query strings during the country-specific redirect. A destination URL that validates correctly for UK traffic may fail for German traffic if the CDN applies different redirect rules per region. Validate representative destination URLs for each country-specific program using mlz check, particularly when CDN configuration is shared across markets.

Deep links in Tradedoubler programs need individual UTM validation

Tradedoubler supports deep links — publisher-created links pointing directly to specific product pages or category pages rather than a single program landing page. When publishers construct deep links, they may reference product page URLs on your site that have different redirect behaviors than your main landing page. E-commerce platform canonical URL enforcement that does not affect the homepage may strip query parameters on product category pages. Run mlz check against a representative set of product page URLs to confirm UTM parameter survival before enabling deep links in your Tradedoubler program.

Casing inconsistency across multi-market programs fragments GA4 reporting

Tradedoubler advertisers who run programs across multiple European markets often configure different destination URLs per country, sometimes introducing casing variations: utm_source=Tradedoubler in the UK program and utm_source=tradedoubler in the French program. GA4 is case-sensitive and records these as separate sources, making cross-market affiliate attribution impossible. mlz build automatically lowercases all input values and replaces spaces with hyphens, producing consistent output regardless of the input. For the full explanation of GA4 case sensitivity, see are UTM parameters case sensitive in GA4?

Frequently asked questions

Where do I add UTM parameters in the Tradedoubler advertiser portal?

In the Tradedoubler advertiser portal, navigate to your Programme settings and find the Destination URL or Landing Page URL field. This is where you paste the UTM-tagged URL generated by mlz build. The URL format is: https://shop.example.com/landing?utm_source=tradedoubler&utm_medium=affiliate&utm_campaign=summer-sale-2026. Tradedoubler will use this as the final destination when routing publisher clicks through its tracking redirect. For programmes with multiple creatives or seasonal landing pages, create separate programme configurations with distinct UTM-tagged destination URLs for each.

Does the Tradedoubler tracking redirect strip UTM parameters?

Tradedoubler’s track.tradedoubler.com redirect is designed to forward the advertiser-configured destination URL intact, including all query parameters. Parameter stripping typically occurs on the advertiser’s server side after Tradedoubler delivers the visitor: GDPR CMP implementations, CDN geo-routing rules, e-commerce platform canonical URL rewrites, or HTTP-to-HTTPS upgrade redirects that were not configured to preserve query strings. Run mlz check against your destination URL to confirm parameters survive the full chain to the final page load before activating your Tradedoubler programme.

What utm_source value should I use for Tradedoubler traffic?

Use utm_source=tradedoubler as the baseline for all Tradedoubler network traffic. For multi-market programs where you want to segment affiliate performance by country in GA4, use utm_source=tradedoubler-uk, utm_source=tradedoubler-de, and so on. Keep all values lowercase and hyphenated — mlz build enforces this automatically. Set utm_medium=affiliate consistently across all affiliate network traffic so GA4’s default channel grouping correctly identifies the Affiliate channel.

How do I track performance across different European markets in GA4?

Use either utm_content or a country-specific utm_source pattern to segment Tradedoubler performance by market in GA4. The utm_content=uk-program approach keeps the source consistent (utm_source=tradedoubler) while using the content dimension for country segmentation. The utm_source=tradedoubler-uk approach uses the source dimension itself for country segmentation and is better for programs where you want country-level attribution in GA4’s channel reports. Generate all destination URLs programmatically using mlz build to guarantee consistent casing and formatting across all market configurations.

Should I validate Tradedoubler destination URLs in an automated pipeline?

For programmes with a high volume of offers or multi-market configurations, automated validation is a practical safeguard. Use mlz check in a script that tests each destination URL before it is entered into the Tradedoubler portal, failing the submission if any URL returns valid: false. This prevents infrastructure changes — CDN geo-routing updates, CMP configuration changes, e-commerce platform upgrades — from silently breaking affiliate attribution across all active Tradedoubler market programmes. For a complete implementation guide including GitHub Actions workflow templates, see automating campaign link validation in CI/CD.