top of page
kreate for events-02.png

Cross-domain tracking between the show site and the registration platform

Sep 24
5 min read

Updated: Oct 8

Two women view a MacBook Pro in a bright office, browsing Archiproducts furniture images.

The short version. Almost every show puts registration on a separate platform, often on a separate domain. Without cross-domain measurement configured, the analytics treats the handoff as a visitor leaving your site and a different visitor arriving at the platform. Every registration is then credited to your own domain as a referral, and the campaign that produced it disappears.

This is the second of the four faults we find most often in inherited show measurement, and it is the one that destroys data rather than inflating it, which makes it harder to notice, because nothing looks too good.

What actually happens at the handoff

A visitor arrives on the show site from a paid campaign. The analytics records the source correctly. They click through to register, and the registration form lives at a different domain, a platform subdomain, a vendor's own domain, a separate registration site.

Unless the two properties have been told they are part of one journey, the analytics on the receiving end sees a brand-new visitor whose referrer is your show site. The original campaign source is discarded at the boundary. The conversion is then attributed to a referral from your own domain.

The visitor experienced one continuous journey. Your measurement recorded two unrelated sessions.

The symptom, and how to recognise it

There is a specific and recognisable signature. If your last edition's report shows:


  • your own domain appearing as a large referral source, and

  • a paid campaign that appears to have driven substantial traffic and almost no registrations, while

  • the total registration number was nonetheless healthy

then check this before concluding the campaign failed. We have seen paid channels written off, and budgets reallocated on the strength of it, when the only thing wrong was a missing configuration.

The reason it survives so long is that the totals stay right. Registration count is accurate. Only the attribution is destroyed, and attribution is the part nobody audits until someone asks where the registrations came from.

How to check Cross-domain tracking in five minutes

Three checks, in order.

One — follow a live link. Click a paid link on the show site, proceed through to the registration form, and inspect the URL at each step. When you cross to the registration domain, look for whether a tracking identifier has been appended to the URL. If nothing carries across, nothing is linking the two sessions.

Two — look at your own referrals. Open the last edition's channel or referral report and look for your own domain. It should not be there in any volume. A show site appearing as one of its own top referrers is close to conclusive.

Three — compare the two totals. Take total registrations from the registration platform and total registration conversions from the analytics. If the platform's number is materially higher, sessions are being lost at the boundary rather than conversions being missed.

How to fix it

In descending order of preference.

Configure the cross-domain list on both properties. Every domain in the journey — show site, registration platform, any intermediate redirect domain — needs to be listed on both ends. This is the correct fix and it takes minutes when both parties cooperate.

Pass parameters through the handoff and reconcile server-side. Where the registration vendor will not add your measurement configuration — and some will not, particularly white-label platforms serving many organisers — append your campaign parameters to the handoff URL and have the platform store them against the registration record. You then join on the registration identifier afterwards. More work, entirely reliable, and it has the advantage of putting the source data inside the registration record where it belongs.

Use the platform's own source capture. Some registration platforms record a source field natively. Where they do, populate it from the URL and export it with the registration data. Weakest option, because the definitions rarely match your analytics, but far better than nothing.

The vendor conversation to have before the show

This is a contract question, not a technical one, and it is much easier before the platform is live.

Ask the registration provider four things in writing:

  1. Can we add our own measurement configuration to the registration pages?

  2. Will campaign parameters appended to the handoff URL be stored against the registration record and returned in the export?

  3. Does the registration identifier persist into the badge or attendance record?

  4. Can we get the registration export with source fields, on a schedule, during the campaign rather than after the show?

The third question is the one to insist on hardest, and it is not really about cross-domain tracking. Without that persistence nobody can measure registration-to-attendance, which means every cost-per-registration figure the campaign produces is a cost per promise rather than a cost per attendee.

Two adjacent things that break at the same boundary

Consent flows. If the registration platform runs its own consent banner with different defaults from the show site, the proportion of visitors measured changes at the boundary. That is not a cross-domain fault but it produces a similar-looking gap, and it will also break year-on-year comparison if the banner changed between editions.

Redirects in the path. Vanity URLs, link shorteners and marketing redirect rules frequently strip query strings. A redirect between site and platform can remove the very parameters you configured. Audit every hop and make each one preserve the query string.

What to do if you find this mid-campaign

Fix the configuration immediately — it takes minutes and every day it runs unfixed is a day of unattributable spend.

Then mark the period before the fix as non-comparable in writing, rather than presenting a comparison the data cannot support. A report saying "source attribution unavailable before this date, and here is why" is more credible than one that quietly reports a paid channel as having underperformed.

And do not retrospectively reallocate budget on the pre-fix numbers. That is the expensive mistake this fault causes, and it is usually made with confidence.

Start where we start

Before we take an engagement we run a paid diagnostic on the last edition, your own numbers, what they can and cannot support, and where the measurement breaks. You keep the report whether or not we work together, and if the finding is that you do not need an agency, that is what it will say. Harry Aloysius is the founder of Kreate for Events, the trade show marketing practice of Kreative Clan Private Limited, and works on organiser-side visitor acquisition and exhibitor renewal across the GCC, Africa and South Asia.

Sources. Freeman 2025 trends research, presented by Ken Holsinger, reported by Skift Meetings, 15 January 2026 · CEIR Q2 2025 Index Report, via IAEE · CEIR 2026 Marketing Spend Decision Report · CEIR Performance Benchmark Playbook, 2nd edition, July 2026 · UFI Global Exhibition Industry Statistics, data year 2024, published 20 May 2025 · UFI Global Exhibition Barometer, 36th edition (January 2026) and 37th edition (July 2026) · Lippman Connects, Benchmark & Trends in Attendee Acquisition, 2016 · AEO/AEV/ESSA with Oxford Economics and UFI, 2019 · RX Global, “Enhancing exhibitor success”. Figures marked as ours are Kreate’s own and are stated with their basis; where a figure is not yet auditable it is not stated.

 
 
 

Comments


bottom of page