Display / GDN Tracking and Migration

Existing Display campaigns remain editable during Google’s phased migration; new Display creation is moving into GDN inventory inside Demand Gen.

Open the UTM Builder

DIRECT ANSWER

Keep an existing Display campaign’s Wix-bound URL tracking intact through migration.

Google Display tracking and Demand Gen migration.

APPLICABILITY + PREREQUISITES

Use this only for a click that reaches Wix.

Existing eligible Display campaigns and their transition to Demand Gen—not obsolete new-campaign instructions.

  • Use the real HTTPS Wix landing page.
  • Confirm the campaign surface permits an external website destination.
  • Keep campaign values free of personal data.
  • Grant the advertising consent required by the live site before expecting capture.

EXACT NAVIGATION

Where to configure it.

Campaigns → filter Campaign type: Display → open Settings/URL options. If eligible, Campaigns → select campaigns → Edit → Upgrade to Demand Gen.

Platform labels can vary by account, objective, rollout or region. Use the cited current help page when the field is not visible.

VERIFIED TEMPLATE

Copy the correct output type.

utm_source=google&utm_medium=display&utm_campaign={campaignid}&utm_content={creative}

Use the existing campaign’s supported Final URL suffix or tracking template. After migration, verify the resulting Demand Gen URL options and landing page again.

Open the campaign-aware UTM Builder

DYNAMIC VALUES

What can resolve after the click.

Existing Display may use {campaignid}, {creative}, {placement}, {network} and contextual values when supported. Demand Gen removes placement, network, keyword, target and targetid ValueTrack support.

TEMPLATE VALUE{campaignid}

The platform token before an eligible live click.

RESOLVED VALUE123456789

A synthetic illustration only. The local Builder cannot predict a real platform value.

EXCEPTIONS + COMMON MISTAKES

Test the actual campaign path.

Google began the migration-tool rollout in June 2026; migrated campaigns cannot be reverted. A click can reach Wix; an impression cannot.

Do not instruct users to create a retired subtype or assume every old macro survives migration.

VALIDATE IN WIX

From resolved landing URL to customer action.

  1. 01

    Use the platform’s URL test when available, then open one authorized real click.

  2. 02

    Confirm the Wix landing page loads and the expected resolved keys remain in the address after redirects.

  3. 03

    In the same browser and consent state, complete one supported native Wix Form, Booking, legacy Chat, qualifying Smart Chat or Stores checkout Order action. Smart Chat requires the submitted contact-form path.

  4. 04

    Review only the values actually present in UTM Contact Attribution. Missing context can be a valid result.

The app does not call the advertising platform API, upload conversions, calculate revenue/ROI/ROAS, identify every served asset or stitch devices.

OFFICIAL SOURCES

Evidence used for this guide.

Last verified: October 18, 2026. Screenshot status: no authenticated account screenshot published; written navigation uses the cited official documentation.

NEXT ACTION

Build, click and verify one controlled URL.

Generate the right output, test the real landing path and then complete one supported native Wix action.

Open UTM Builder