google / cpc
Use utm_source=google and utm_medium=cpc. Keep auto-tagging requirements separate; a GCLID and UTM values can serve different reporting needs.
GUIDES / CAMPAIGN SETUP
Practical setup guidance for carrying useful campaign context into a Wix site.
Start hereStart with a clean destination URL, choose a stable source and medium, and use one campaign name across ads and reporting. The generated URL should lead to the real Wix landing page that precedes the supported customer action.
Use the canonical Wix page visitors should reach. Preserve legitimate existing query parameters.
Keep source and medium values consistent. Use a campaign value that a marketer can recognize later.
Open the URL, confirm the destination loads, and verify the address contains the expected encoded parameters.
After consent and platform conditions are satisfied, review attribution attached to the Wix Form, Booking, Chat or Stores Order.
Use utm_source=google and utm_medium=cpc. Keep auto-tagging requirements separate; a GCLID and UTM values can serve different reporting needs.
Use a consistent source for Meta traffic and reserve campaign, term and content for the campaign, audience and creative distinctions your team actually reviews.
Use utm_source=bing and utm_medium=cpc when that matches the reporting convention used across the account.
Use the sender or publication as the source, email as the medium, and a campaign value tied to the send or sequence.
These URL conventions do not guarantee that every visit or action can be attributed. Consent, missing parameters, redirects, browsers and platform behavior can affect the available context.
LEAD SOURCE / ACTIONS
See how one Wix contact can have multiple supported customer actions with separate available attribution.
Read the lead-source guideAGGREGATE / INDIVIDUAL
Use aggregate reporting for trends and individual context when a specific supported action needs review.
Compare the workflowsWIX FORMS
Connect tagged campaign context to a supported individual Form action.
Read the Forms guideWIX BOOKINGS
Separate native source totals from context retained for one supported Booking action.
Read the Bookings guideWIX STORES
Review campaign context for a supported checkout action without implying revenue or ROAS attribution.
Read the Order guideGOOGLE ADS / GCLID
Understand Google Ads conversion tracking, Wix aggregate reporting, literal UTM values and captured GCLID context.
Read the Google Ads guideUTM Contact Attribution supports native Wix Forms, Wix Bookings, legacy Wix Chat, qualifying Wix Smart Chat and Wix Stores Orders. Smart Chat requires a submitted qualifying contact form; anonymous messages are not attributed. Third-party apps are not automatically supported.