How to Track the Source of Wix Leads and Customer Actions

01 / TWO QUESTIONS

Two reporting questions businesses often confuse

A / AGGREGATEWhich channel generates more conversions?

Wix Analytics is useful for source, campaign and conversion trends across groups of visits and actions.

B / INDIVIDUALWhere did this specific lead or customer action come from?

Action-level attribution is useful when the marketer needs available campaign context beside a supported Form, Booking, Chat or Order.

Neither question replaces the other. Aggregate reporting helps allocate attention across channels; individual context helps review the quality and history of particular supported actions.

02 / MARKETING CONTEXT

What counts as marketing context

utm_source

Tagged source.

utm_medium

Tagged medium.

utm_campaign

Tagged campaign.

utm_term

Literal tagged term.

utm_content

Literal tagged content.

gclid

Available Google click identifier.

Direct or untagged traffic may have no campaign parameters. “Direct” is a reporting condition, not proof that no prior marketing influenced the visitor.

03 / EXAMPLE WORKFLOW

A service-business journey with more than one action

Example workflow—not a customer case study or promised result.

01Google Ads tagged visit
02Wix Form
03Later Wix Booking
04Related Wix Contact

The Form and Booking are separate supported customer actions. When context and correlation are available, each action can retain its own attribution instead of forcing the contact into one permanent source label.

04 / ONE-TO-MANY MODEL

Why one Contact can have multiple actions

CONTACTOne Wix Contact

ACTIONSMany supported actions

ATTRIBUTIONAvailable context per action

A person might submit a Form, return later for a Booking, and complete a qualifying Smart Chat contact form. Treating every action as the same “lead source” can hide useful differences. The action record preserves the available context for that event while the Wix Contact relationship keeps the customer history connected. An anonymous Smart Chat message is not an attributed action.

05 / SUPPORTED ACTIONS

Supported native Wix customer actions

01Wix Forms
Supported native Form submissions.
02Wix Bookings
Supported confirmed Booking actions.
03Legacy Wix Chat (CHAT)
Supported legacy Chat actions where required event information is available.
04Wix Smart Chat (S-Chat)
Eligible after a qualifying Smart Chat contact form is submitted and correlated with a Wix Contact. Chat messages alone are not attributed.
05Wix Stores checkout Orders
Supported order events received from Wix Stores.

“Lead” is not used here as a universal label for every action. Third-party form, booking, chat and commerce apps are not automatically supported.

06 / AVAILABILITY LIMITS

When attribution can be unavailable

CONSENT

Marketing storage may be gated

The site's consent configuration and the visitor's choice can limit available context.

MISSING CONTEXT

Tags may not exist

Untagged links, redirects and removed parameters can leave no campaign values to associate.

BROWSER STATE

Browsers change what persists

Privacy controls, cleared storage and device changes can interrupt the attribution path.

CORRELATION

Identity may not connect

Unsupported actions or insufficient Wix contact/event information can prevent an action relationship.

Attribution describes recorded context. It does not establish causal proof, guarantee every action will be attributed, or calculate revenue or ROAS.