Traffic Sources: How Wix Customer Attribution Works

Traffic-source answers depend on the evidence that survives the real visit and is eligible for the Customer Action. A platform name, click identifier or missing UTM tag is never enough to invent a source.

THE EVIDENCE MODEL

Start with what the visit actually supplied.

An attributed Customer Action has eligible marketing evidence connected to it. The Dashboard can show the available Traffic source, medium, campaign, keyword / creative and touch details; it does not reconstruct values that were never captured.

Attributed

The Customer Action has eligible source, campaign or external-referrer evidence. Read the displayed values literally.

Direct

A valid visit snapshot had no campaign or external referrer. Direct does not mean Unknown. Missing UTM parameters alone do not prove Direct because an eligible external referrer may still exist.

Unknown or unavailable

The action exists, but a source or touch value cannot be classified or matched reliably from the eligible evidence. “Unknown” is an explanation of unavailable evidence, not a platform the app guessed.

No eligible snapshot

No eligible visitor attribution snapshot was available for the action. This is a diagnostic condition, not a selectable Dashboard status. It can leave attribution fields unavailable or the action outside an attributed view.

Consent can restrict whether marketing evidence is captured or eligible. Respect the visitor’s choice; do not infer denied or missing data.

SOURCE REFERENCE

Use explicit tags before assumptions.

Traffic sourceEvidence that is safe to useWhat the Dashboard can support
Google AdsExplicit values such as google / cpc; a captured gclid may also be present.Paid Search is a useful convention when the medium explicitly says paid search. A GCLID alone is not an Ads API lookup or proof of the campaign name.
Microsoft / Bing AdsExplicit values such as bing / cpc.Paid Search is supported by the UTM evidence. msclkid is not in the app’s verified captured-field set and is not promised here.
Facebook or Instagram AdsExplicit source plus a paid medium such as paid_social.Paid Social only when the tags supply paid evidence. A social click identifier or referrer alone does not prove an ad.
LinkedIn or TikTok AdsExplicit platform source plus paid_social or another documented paid convention.Paid Social when the surviving UTM values say so. The app does not invent campaign names from a referrer.
Google or Bing OrganicAn available search-engine referrer, or an explicit privacy-safe organic convention.Organic Search only where eligible evidence identifies that path. Referrer loss can make the source unavailable.
Facebook or Instagram OrganicAn eligible social referrer or explicit values such as instagram / organic_social.Organic Social where the evidence remains available. In-app browsers and redirects can remove referrer context.
Email marketingA tagged link such as newsletter / email with a campaign value.Email from the literal tags. Avoid adding manual UTMs when the email platform already adds them.
YouTubeExplicit tagged values, or an eligible external referrer.Classification depends on the evidence: a paid-video tag, organic-social convention or referral is not interchangeable.
Other websitesAn eligible external referrer, ideally reinforced by a controlled referral UTM link.Referral or the literal tagged source when available. The referring domain is not automatically a campaign name.
DirectA valid visit snapshot with no campaign and no external referrer.Direct. It is a positive evidence condition, not a synonym for missing UTMs or Unknown.
UnknownInsufficient eligible evidence to determine a source reliably.Unavailable or Unknown context; never replace it with a guessed platform.

The Dashboard primarily exposes the literal source and medium it retained. Labels such as Paid Search, Paid Social, Organic Search, Organic Social, Email and Referral are safe interpretations only when the available evidence supports them; they are not promised as universal automatic UI categories.

WORKED EXAMPLE

From a tagged Google Ads visit to a Wix Form.

A visitor opens a Wix landing page with utm_source=google, utm_medium=cpc, utm_campaign=fall_service, an optional term and creative label, then submits a supported native Wix Form in the same eligible browser path.

Source / Medium

google / cpc, when those values survive and are eligible.

Campaign

fall_service, the literal campaign label supplied by the link.

Keyword / Creative

The literal term and content values when provided; not automatic advertising-platform enrichment.

Customer Action

The supported Wix Form action.

Contact

The associated Wix Contact when identity resolution is available.

Result

The action’s review state, separate from its traffic source.

Date

When the supported Customer Action was recorded.

TOUCHES + RESULT

Keep attribution views separate from business assessment.

First Touch

The earliest available captured marketing context for the eligible related visitor or contact path—not automatically the first-ever browser snapshot.

Last Touch

The most recent available captured marketing context before the review point.

Conversion Touch

The available marketing context associated with this qualifying Customer Action.

One customer journey, three attribution viewsIllustrative example, not customer data
  1. Visit from a Google Ads link

    google / cpc

    First Touch

  2. Later visit from an email link

    newsletter / email

    Last Touch · Conversion Touch

  3. Wix Form submitted

    Customer Action

First Touch
The earliest available captured marketing context. In this journey: the Google Ads visit.
Last Touch
The most recent available captured context before the review point. In this journey: the email visit.
Conversion Touch
The available context associated with this Customer Action. In this journey: the email visit that preceded the form.

The three views can point to the same visit: with a single visit before the action, all three show that visit. Visits count within the 90-day attribution window, and the values shown depend on the eligible snapshots actually retained.

For example, an eligible paid-search visit followed by an eligible email visit and then a supported action can leave Paid Search as First Touch, Email as Last Touch, and the context tied to the action as Conversion Touch. The exact displayed values depend on the eligible snapshots actually retained.

Not reviewed

The business owner has not assessed the action.

Order

A qualifying native Wix Order can carry the effective Order result; the Dashboard control can also record an owner’s Result assessment.

Not an order

The action was assessed as not producing an order.

Result is not a traffic source. A Form, Booking or Chat action is not automatically a sale, and Result does not calculate revenue or prove causation.

LIMITS + NEXT STEPS

Why fields can be unavailable.

  • UTM parameters may be missing, misspelled, duplicated, stripped or incorrectly encoded.
  • A source can be known while campaign, keyword or creative remains not-set because those values were not supplied.
  • Browsers, apps, shorteners and redirects can limit or remove referrer evidence.
  • Consent denial can prevent the relevant marketing context from becoming eligible.
  • A returning visitor can have multiple eligible visits; the touch views depend on the retained path, not a guessed first-ever visit.
  • Direct and Unknown are distinct: Direct has a valid no-campaign/no-external-referrer snapshot, while Unknown lacks enough reliable classification evidence.

DIRECT ANSWER

Understand why a Wix Customer Action is attributed, Direct or missing usable source context.

How Wix traffic-source and customer attribution evidence is interpreted.

KNOWN LIMITS

Read the result narrowly.

Attribution is evidence-based rather than complete or causal. Consent, redirects, browser state, returning visits, missing tags, unavailable referrers and action eligibility can limit the context attached to a Customer Action.

NEXT ACTION

Continue with the next relevant Help task.

Use the Help navigation to keep campaign setup, testing and troubleshooting connected.

Help Center