Xola → Adobe Analytics · Conversion tracking
Connecting Xola to Adobe Analytics
Xola books tours and activities where capacity is fixed by the boat, the van or the guide, so the goal is not maximum bookings but the right bookings at the right price. Adobe Analytics processes data on the way in through rules you configure, which means the same event can be recorded differently by two report suites and both will look authoritative. The join between them succeeds or fails on one thing: whether the Experience Cloud ID, plus whatever eVar you designate reaches the Xola booking before the conversion happens, because Adobe Analytics can only match a conversion it can tie back to a click it recognizes.
✓ 30-minute call · No commitment · You leave with a written remediation plan even if we’re not the right fit.
Written guarantee
95%+ conversion accuracy on Xola → Adobe Analytics
Measured against your own order records at handover. Miss it and we keep working at no cost until it’s met.
Built on — and certified for — the platforms that matter
Stape
Pro Partner
Meta
Tech Provider
Tag Manager
TikTok
Events API
Microsoft
UET Partner
CAPI Partner
CAPI Partner
Built on the same partner stack used by enterprise DTC brands.
By the numbers
No fake testimonials.Just the math.
70+
Platforms supported
Shopify · Woo · Magento · BigCommerce · 65 more
8+ / 10
Meta EMQ guaranteed
in writing — keep working free until hit
2–4d
Build to live
accurate data flowing within 7 days
$0
Monthly fees, ever
one-time fixed price · you own the stack
400d
Cookie lifetime
max RFC 6265bis allows · 57× Safari ITP
9
Ad channels covered
Meta · Google · TikTok · MS · LI · Pin · Snap · Reddit · X
95%+
Tracking accuracy
verified vs Stripe · GA4 · ad-platform reports
30 min
Free founder call
no SDR · no pitch deck · written remediation plan
Every figure above is either a commitment we put in writing or a countable fact. What your own setup is losing is not on this list, because we haven’t measured it yet — that happens on the call, against your own order records.
Real clients · real videos · real outcomes
Don’t take our word for it. Watch the receipts.
Founders, marketers, and agency owners describing the before-and-after of their Xola → Adobe Analytics tracking rebuild — in their own words, on camera.
Why this join usually fails
The Experience Cloud ID, plus whatever eVar you designate never reaches Xola
The single most common cause. The checkout runs in a Xola-served frame, and a meaningful share of activity bookings are made by one person for a whole group.
Bookings counted, participants ignored
Optimizing on booking count teaches the platform that a one-person booking is as good as a twelve-person one. It will then find you a great many solo travellers.
Processing rules rewriting data before anyone sees it
Rules run before storage and are frequently configured years earlier by someone who has left. A campaign variable can be overwritten, defaulted or dropped on the way in, and the reports will look consistent and be wrong.
Nothing reconciles afterwards
An upload that succeeds is not an upload that matched. Use a raw data feed or Data Debugger to see what actually arrived, not the processed report. Those are different things and only one of them shows the truth.
Architecture
How Xola and Adobe Analytics actually connect
Two systems that know nothing about each other. Everything below exists to give them one shared reference.
Step 1
Xola holds the truth
One booking can be one person or twelve. Counting bookings rather than participants makes a family reunion and a solo traveller identical conversions against wildly different revenue.
Step 2
Adobe Analytics needs a click to match
An eVar with the right persistence and allocation, an event configured in the report suite, and processing rules that do not quietly rewrite what arrived.
Step 3
The identifier is the bridge
The Experience Cloud ID, plus whatever eVar you designate, captured at the visit and carried into the Xola booking. Without it there is nothing to join on and no tool fixes that.
Step 4
The event source decides reliability
Send bookings valued at the total paid, with participant count as a separate field.
Step 5
Deduplication at the destination
Adobe deduplicates on purchase ID for orders. Omit it and a customer refreshing a confirmation page records the order again, which is the single most common inflation in Adobe implementations.
Diagnose it honestly
Working vs. broken, side by side
Both states look identical from the Adobe Analytics dashboard, which is why this runs for months before anyone notices.
Normal — not a fault
The Experience Cloud ID, plus whatever eVar you designate present on the booking
Visible on the record itself in Xola, not merely captured somewhere on the site.
Sent from the Xola booking record
Server-side, so it does not depend on the customer's browser still being there.
Deduplicated correctly
Adobe deduplicates on purchase ID for orders. Omit it and a customer refreshing a confirmation page records the order again, which is the single most common inflation in Adobe implementations.
Reconciles with the source
Adobe Analytics's count and Xola's records agree within a few percent over a closed window.
Actually broken
The Experience Cloud ID, plus whatever eVar you designate missing on most records
The checkout runs in a Xola-served frame, and a meaningful share of activity bookings are made by one person for a whole group.
Sent from the browser
Anyone who closes the tab, blocks the script or converts without a page load is invisible. Optimizing on booking count teaches the platform that a one-person booking is as good as a twelve-person one. It will then find you a great many solo travellers.
Counted twice, or not at all
Rules run before storage and are frequently configured years earlier by someone who has left. A campaign variable can be overwritten, defaulted or dropped on the way in, and the reports will look consistent and be wrong.
Nobody has reconciled it
The dashboard shows a number and no one has compared it to Xola. A wrong number that nobody checks is indistinguishable from a right one.
Diagnostic sequence
Diagnostic order
Each step rules out a class of cause. Run them in order and the last one usually has a single explanation standing.
- 1
Count bookings carrying the Experience Cloud ID, plus whatever eVar you designate
The ceiling on everything else. Do this before debugging anything downstream.
- 2
Follow one real conversion end to end
From the ad click through Xola and into Adobe Analytics.
- 3
Compare booking count against participant count by campaign
The ratio varies by source far more than most operators expect, and it decides where budget should go.
- 4
Read the processing rules and the eVar allocation settings
Before debugging the tag. On mature Adobe implementations the explanation is upstream of the browser far more often than in it.
- 5
Read the match rate, not the success message
Use a raw data feed or Data Debugger to see what actually arrived, not the processed report. Those are different things and only one of them shows the truth.
Source-of-truth validation
How it gets proven
Against Xola's own records, not against either platform's dashboard.
- The Experience Cloud ID, plus whatever eVar you designate confirmed present on a live booking.
- A real conversion followed from click through Xola to Adobe Analytics.
- Orders reconciled against the raw feed with purchase ID deduplication verified, then against the processed report suite.
- Departed bookings reconciled at total value against imported conversions.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later.
Straight talk
When you don't need this
Worth reading before paying anyone, including us.
- If Adobe Analytics already reports conversions that reconcile against Xola's records within a few percent, this join is working and there is nothing to buy.
- Measure identifier coverage yourself first — pull your last hundred bookings and count how many carry the Experience Cloud ID, plus whatever eVar you designate. Ten minutes, free, and it tells you whether any of this is worth doing.
- If every booking is a fixed single seat, count bookings and skip the participant dimension entirely.
- If you are already on GA4 and not obliged to use Adobe, running both means two versions of every number and a standing argument about which is right.
Who this is for
Honest about who we’re a fit for.
We don’t take every project. Here’s how to tell if we’re right for you.
You’re a great fit if…
- You run Xola → Adobe Analytics (or are migrating to it)
- You spend $5K+/month on paid ads (Meta, Google, TikTok, Microsoft, LinkedIn)
- Your reported ROAS doesn’t match what your bank account is saying
- You want to own your tracking stack — no monthly SaaS fees forever
- You have 2–4 days to do this once and never think about it again
Skip us if…
- You spend less than $500/month on paid ads (browser pixel is fine)
- You want a SaaS dashboard with monthly fees forever (Triple Whale, Hyros)
- You need attribution modeling — we fix the data foundation, not multi-touch reports
- You want a 6-month enterprise consulting engagement (we ship in 4 days)
- You expect us to manage your ad accounts (we don’t — that’s a different service)
If you’re still unsure,book the call anyway— we’ll tell you straight whether we can help.
What working looks like
The Experience Cloud ID, plus whatever eVar you designate on every booking
Server-sideCaptured before the conversion and stored where it survives.
Conversions arriving in Adobe Analytics
8+ EMQThe hit is processed through VISTA and processing rules, lands in the report suite, and becomes available under whatever allocation the eVar specifies.
Reconciled against the source
DedupedXola's own records are the reference, not either dashboard.
What gets built
Identifier capture into Xola
Capture on your own domain before the frame loads, and attach the identifier to the booking so participant count and total value travel with it.
Event source: the Xola booking record
Send bookings valued at the total paid, with participant count as a separate field.
Dispatch to Adobe Analytics
Server-side via the Data Insertion or Edge API, with the ECID and the configured variables.
Reversals where they exist
Cancellations and weather cancellations reverse. In outdoor activities the second category is not small.
Pick the package that fits your ad spend
Fixed-fee, no surprises. If your ad spend is meaningful,server-side tracking is what we recommend— it’s the only setup that survives iOS, Safari ITP and ad blockers.
Browser-side starter
Wires the join and verifies it on a live conversion. Honest about its ceiling where the source can only be read from the browser.
- The join built and tested end to end
- Verified on a real conversion
- Reconciled against the source's own records
- Written handover
1st-party server-side
Save $18K–$120K over 5 years vs Triple Whale / Hyros
The join built server-side from the source's own records, so it does not depend on a browser being present when the conversion happens.
- Events sourced from the system of record, not the browser
- Identifier captured and persisted end to end
- Deduplicated at the destination
- Reversals wired where the source supports them
- 95%+ accuracy guaranteed in writing
Full 1st-party stack
Every destination fed from one place, plus monitoring so a broken join surfaces in days rather than at quarter end.
- Everything in 1st-party server-side
- All paid destinations from one container
- CRM and offline loop
- Refunds and cancellations reversed everywhere
- Monitoring per destination
Not sure which tier fits?Book a 30-min scoping call— we’ll tell you straight, no upsell pressure.
How it works
Built in 2–4 days. Accurate data within 7.
We deliver the entire 1st-party server-side stack in 2–4 business days. You start collecting accurate, deduped conversion data the moment it goes live — and within 7 days every signal is flowing cleanly to Meta, Google, TikTok and the rest.
Kickoff + audit
30-min call. We map your current pixels, GTM, dataLayer, consent setup, and ad-platform integrations. You get a written report of every leak.
Build the stack
Server-side GTM container deployed on your subdomain. Meta CAPI · Google EC · TikTok Events API · Microsoft UET wired. Identity match + dedup configured.
QA + go-live
Live-fire test purchases across every funnel step. Meta EMQ verified at 8+. Tag Assistant + Pixel Helper passes. Side-by-side report delivered.
Verify accuracy
Your data flows clean. Within 7 days every signal — Meta, Google, TikTok, Microsoft — is fully accurate. Notion runbook + Loom walkthrough handoff.
Got questions?
The honestanswers.
No buzzwords, no upsell. If we don’t know, we say so.
01Why aren't my Xola conversions showing in Adobe Analytics?
Almost always because the Experience Cloud ID, plus whatever eVar you designate never reached the Xola booking. The checkout runs in a Xola-served frame, and a meaningful share of activity bookings are made by one person for a whole group. Measure coverage before debugging the dispatch.
02What identifier does Adobe Analytics need?
Identity is the ECID, with visitor stitching configurable on top. The click identifier is not native — it lives in an eVar you assign, with an expiry and an allocation model you choose, and those two settings silently decide what your attribution reports say.
03Where should the event come from?
The Xola booking record. Send bookings valued at the total paid, with participant count as a separate field.
04How do I know it worked?
Use a raw data feed or Data Debugger to see what actually arrived, not the processed report. Those are different things and only one of them shows the truth.
Still have questions?Book a 30-min call— bring them all.
The call
What happens on your free 30-min call
No pitch deck, no SDR, no upsell pressure. Founder-led. Bring your ad-platform screens and yourXola → Adobe Analytics setup — we’ll work through it together.
Min 1–5
We get the lay of your store
What you sell, what you spend on ads, who handles dev. Quick context-gathering — no questionnaire upfront.
Min 5–15
We audit your tracking live
Screen-share. We open your Meta Events Manager, GTM, and ad reports. You see exactly which conversions are leaking.
Min 15–25
We map a fix
What needs rebuilding, what stays. The exact Xola → Adobe Analytics setup we'd ship and what it would recover for you.
Min 25–30
Decide. Or don’t.
If we're a fit, we send a 1-page proposal in writing. If not, you walk away with a free remediation plan you can hand to anyone.
Get Xola and Adobe Analytics joined properly
Book a free 30-minute call. We measure your identifier coverage live on your own account, and you leave with a written plan — including the option that you don't need us.
Free · 30-min consultation · No commitment · Replies in under 2 hours · Available worldwide via WhatsApp
Using Xola for bookings? How Xola bookings get tracked end to end
95% tracking accuracy guarantee
Free 30-min consultation · from $400 · 1st-party server-side
95% guarantee · from $400
