DIRECT ANSWER
Add campaign and creative context to Demand Gen website destinations.
Google Demand Gen UTM setup.
APPLICABILITY + PREREQUISITES
Use this only for a click that reaches Wix.
Demand Gen ads with a website Final URL across eligible YouTube, Discover, Gmail, Maps and Google Display Network inventory.
- 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 → select Demand Gen → Settings or the relevant ad → URL options; confirm the final website URL on every asset format.
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=paid_social&utm_campaign={campaignid}&utm_content={creative}Use as a Final URL suffix when the account exposes that field, or attach the same verified values through the supported URL options for the ad.
DYNAMIC VALUES
What can resolve after the click.
Use generally supported {campaignid}, {creative}, {device} and location IDs where applicable. Demand Gen explicitly does not support {placement}, {target}, {keyword}, {ifsearch:…}, {ifcontent:…}, {network} or {targetid}.
The platform token before an eligible live click.
A synthetic illustration only. The local Builder cannot predict a real platform value.
EXCEPTIONS + COMMON MISTAKES
Test the actual campaign path.
A view, Gmail expansion or other in-platform engagement does not create a Wix visit. Image/video reporting in Google Ads is not a promise that this app identifies the served asset.
Do not reuse a Search suffix with {keyword}; test the resolved website click after platform processing.
VALIDATE IN WIX
From resolved landing URL to customer action.
- 01
Use the platform’s URL test when available, then open one authorized real click.
- 02
Confirm the Wix landing page loads and the expected resolved keys remain in the address after redirects.
- 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.
- 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