How to Track the Marketing Source of Wix Bookings

Wix Bookings Analytics already reports traffic sources for website bookings. Action-level attribution answers a narrower question: what available campaign context accompanied this supported Booking action?

01 / NATIVE REPORTING

What Wix Bookings Analytics shows natively

Bookings Analytics reports booking performance and, for bookings made after a site visit, aggregate traffic sources such as referring sites. It also separates booking channels such as web, Wix apps, external apps and manual orders.

Use that native view when the question is how booking volume or source groups perform overall. UTM Contact Attribution is not a replacement for Bookings Analytics.

02 / TWO LEVELS

Aggregate source reporting versus one Booking action

AGGREGATEWhere did website bookings come from overall?

Native Bookings Analytics is designed for source patterns across bookings.

INDIVIDUAL ACTIONWhat context accompanied this supported Booking?

Action-level attribution keeps available marketing context beside the specific supported action.

03 / ILLUSTRATIVE JOURNEY

A tagged consultation campaign to a Wix Booking

Illustrative setup—not a customer result or fabricated case study.

utm_source
google
utm_medium
cpc
utm_campaign
consultation_search
utm_term
business_consultant
utm_content
ad_variant_2
  1. 01Tagged visit
  2. 02Wix Booking
  3. 03Available attribution

When attribution data is available and correlation succeeds, the product can retain that marketing context with the supported Booking action.

04 / AVAILABLE FIELDS

Campaign fields that can be captured

utm_source

Literal tagged source.

utm_medium

Literal tagged medium.

utm_campaign

Literal campaign name.

utm_term

Literal URL value, not keyword API data.

utm_content

Literal URL value, not creative API data.

gclid

Captured Google click identifier when available.

05 / ATTRIBUTION VIEWS

First, Last and Conversion Touch

FIRST TOUCH

Initial available context

The earliest retained discovery context related to the Contact when available.

LAST TOUCH

Latest available context

The most recent retained context before the supported action.

CONVERSION TOUCH

This Booking action

The available context associated with the specific supported Booking.

06 / KNOWN LIMITS

Availability and contact correlation are not guaranteed

Campaign parameters can be missing because of consent choices, redirects, browser restrictions, platform behavior or an untagged visit. The Booking-to-Contact relationship can also be incomplete in some cases, so the product does not promise contact resolution for every booking.

Recorded attribution describes available context and a correlated relationship. It does not prove causation.

07 / TEST THE PATH

Build and test a Booking campaign URL

  1. 01

    Create the tagged destination

    Use the UTM Builder with a real Wix landing page.

  2. 02

    Complete a test Booking

    Follow the site's consent flow and use a supported native Wix Bookings path.

  3. 03

    Review what is available

    Check the action, attribution and Contact relationship; missing context is a valid outcome.

WIX-NATIVE ATTRIBUTION

Connect the campaign to the customer action.

UTM 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.