01 / NATIVE REPORTING
What Wix Forms and Wix Analytics show natively
Wix Analytics is useful for aggregate reporting: traffic sources, campaign reporting where supported, and Form submissions grouped by traffic source. That helps a business see channel patterns without inspecting every submission.
Aggregate reporting answers questions such as “How many Form submissions came from Paid Search?” It should not be dismissed or replaced when that is the decision a marketer needs to make.
02 / THE MISSING CONTEXT
What changes when you need individual lead attribution
Consider a visitor who opens a Wix landing page with these literal URL parameters and then submits a supported native Wix Form:
- utm_source
- utm_medium
- cpc
- utm_campaign
- emergency_plumbing
- utm_term
- plumber_near_me
- utm_content
- ad_variant_2
The business question is no longer only how Paid Search performed in aggregate. It is whether this exact Form/customer action can be reviewed with the marketing context that was available for its visit and conversion path.
utm_term and utm_content remain literal tagged values. They are not guaranteed Google Ads keyword or advertising-platform creative enrichment.
03 / OPTIONS
Options for tracking Wix Form UTMs
- 01
Use Wix native aggregate reporting
Choose this when traffic-source trends and total Form performance answer the business question. It is the lowest-complexity path and stays within native Wix reporting.
- 02
Build a custom implementation
A qualified developer can capture campaign parameters, respect consent, correlate a visitor with a Form event, choose storage, and build a review workflow. The design must handle missing context, identity changes and privacy requirements.
- 03
Evaluate Wix App Market attribution tools
Compare supported Wix products, data fields, consent behavior, action coverage, retention, review workflow and support. Do not assume every tool supports every Form or third-party app.
- 04
Use UTM Contact Attribution
This product is designed to connect available marketing context with supported native Wix customer actions, including Wix Forms, and keep the action related to a Wix Contact when correlation is available.
04 / PRODUCT FLOW
How UTM Contact Attribution works
- 01Tagged visit
- 02Wix Form
- 03Wix Contact
- 04Customer Action
- 05Stored attribution
- 06Dashboard
The flow depends on available campaign context, the site's consent configuration, browser state, a supported native Wix Form action and successful product correlation. A captured relationship describes the available path; it does not prove that the campaign caused the action.
05 / AVAILABLE FIELDS
What can be captured
utm_sourceThe tagged source, such as google or newsletter.
utm_mediumThe tagged delivery method, such as cpc or email.
utm_campaignThe campaign name chosen in the URL.
utm_termThe literal term value in the tagged URL, not API keyword enrichment.
utm_contentThe literal content value in the tagged URL, not creative-platform enrichment.
gclidA Google click identifier when it is present and available.
06 / ATTRIBUTION VIEWS
First, Last and Conversion Touch
Initial available discovery context
Helps review how the related contact first arrived when that context exists.
Latest available context
Shows the most recent known campaign context before the supported action.
Context attached to this action
Keeps the available attribution associated with the specific supported Form action.
07 / TEST THE PATH
How to test Wix Form campaign context
- 01
Create a tagged destination URL
Use the free UTM Builder and choose values your team will recognize.
- 02
Open the real Wix landing page
Confirm the destination loads and the expected parameters remain in the address.
- 03
Submit a test through a supported native Form
Use test data, follow the site's consent flow, and avoid placing personal information in campaign parameters.
- 04
Review the action, contact and attribution
Check what context is actually available. Missing data can be a valid result of consent, browser or correlation conditions.