AEM → TikTok · Conversion tracking
Connecting Adobe Experience Manager to TikTok Events API
AEM sits inside the wider Adobe stack, which usually means Adobe Analytics is already in place and answering a different question from your ad platforms. TikTok's audience skews to exactly the browsers and app contexts where browser-side tracking performs worst. The join between them succeeds or fails on one thing: whether the ttclid reaches the commerce order behind AEM before the conversion happens, because TikTok 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 AEM → TikTok
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 AEM → TikTok tracking rebuild — in their own words, on camera.
Why this join usually fails
The ttclid never reaches AEM
The single most common cause. Dispatcher caching in front of AEM serves stored output, the Adobe data layer has its own conventions that may not carry your identifier, and enterprise release cycles slow every iteration.
Three systems that will never agree
Adobe Analytics, your commerce system and your ad platforms each measure differently. The useful work is deciding which answers which question, not forcing them to match.
The ttclid is lost in the in-app browser
TikTok traffic arrives through an in-app webview whose storage behavior is inconsistent. An identifier captured but not immediately persisted server-side often is not there by the time the conversion happens.
Nothing reconciles afterwards
An upload that succeeds is not an upload that matched. TikTok Events Manager shows received events and their match status. As with Meta, arriving is not the test — deduplicated and matched is. Reconcile TikTok's reported conversions against the source system for the same window.
Architecture
How AEM and TikTok actually connect
Two systems that know nothing about each other. Everything below exists to give them one shared reference.
Step 1
Adobe Experience Manager holds the truth
In most AEM deployments the commerce engine is separate, and Adobe Analytics reports on its own model with its own attribution. None of those three will agree by default and that is expected rather than broken.
Step 2
TikTok Events API needs a click to match
TikTok matches server events using ttclid where available, falling back to hashed contact information. Both should be sent — the fallback is what carries the events where the click ID did not survive.
Step 3
The identifier is the bridge
The ttclid, captured at the visit and carried into the commerce order behind AEM. Without it there is nothing to join on and no tool fixes that.
Step 4
The event source decides reliability
Send from the commerce layer, server-side. Dispatcher caching makes any per-request template logic unreliable.
Step 5
Deduplication at the destination
TikTok deduplicates on event_id, the same pattern as Meta: the pixel and the Events API must send the same event_id for the same conversion. Mismatched IDs mean double counting.
Diagnose it honestly
Working vs. broken, side by side
Both states look identical from the TikTok dashboard, which is why this runs for months before anyone notices.
Normal — not a fault
The ttclid present on the order
Visible on the record itself in Adobe Experience Manager, not merely captured somewhere on the site.
Sent from your commerce system's order event
Server-side, so it does not depend on the customer's browser still being there.
Deduplicated correctly
TikTok deduplicates on event_id, the same pattern as Meta: the pixel and the Events API must send the same event_id for the same conversion. Mismatched IDs mean double counting.
Reconciles with the source
TikTok's count and Adobe Experience Manager's records agree within a few percent over a closed window.
Actually broken
The ttclid missing on most records
Dispatcher caching in front of AEM serves stored output, the Adobe data layer has its own conventions that may not carry your identifier, and enterprise release cycles slow every iteration.
Sent from the browser
Anyone who closes the tab, blocks the script or converts without a page load is invisible. Adobe Analytics, your commerce system and your ad platforms each measure differently. The useful work is deciding which answers which question, not forcing them to match.
Counted twice, or not at all
TikTok traffic arrives through an in-app webview whose storage behavior is inconsistent. An identifier captured but not immediately persisted server-side often is not there by the time the conversion happens.
Nobody has reconciled it
The dashboard shows a number and no one has compared it to Adobe Experience Manager. 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 orders carrying the ttclid
The ceiling on everything else. Do this before debugging anything downstream.
- 2
Follow one real conversion end to end
From the ad click through AEM and into TikTok.
- 3
Map which system answers which question before building
In an Adobe stack this framing saves more time than any implementation detail.
- 4
Measure ttclid capture rate on TikTok traffic specifically
Not on all traffic. TikTok's in-app browser is the failure case, so a healthy overall capture rate can hide a poor one on exactly the traffic that matters.
- 5
Read the match rate, not the success message
TikTok Events Manager shows received events and their match status. As with Meta, arriving is not the test — deduplicated and matched is. Reconcile TikTok's reported conversions against the source system for the same window.
Source-of-truth validation
How it gets proven
Against Adobe Experience Manager's own records, not against either platform's dashboard.
- The ttclid confirmed present on a live order.
- A real conversion followed from click through AEM to TikTok.
- Deduplication confirmed in Events Manager, and ttclid capture rate measured on TikTok traffic specifically.
- Conversions confirmed sourced from the commerce system, with the Adobe Analytics difference explained rather than reconciled.
- 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 TikTok already reports conversions that reconcile against Adobe Experience Manager'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 orders and count how many carry the ttclid. Ten minutes, free, and it tells you whether any of this is worth doing.
- If Adobe Analytics already answers your reporting needs, the remaining work is only feeding ad platforms — a much smaller scope.
- If TikTok is a small share of spend, the effort is hard to justify. It pays when TikTok is a channel you are actively scaling.
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 AEM → TikTok (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 ttclid on every order
Server-sideCaptured before the conversion and stored where it survives.
Conversions arriving in TikTok
8+ EMQEvents appear in TikTok Events Manager, deduplicated against the pixel, and become usable for optimization.
Reconciled against the source
DedupedAdobe Experience Manager's own records are the reference, not either dashboard.
What gets built
Identifier capture into AEM
Capture the identifier server-side and persist it to the commerce order, and if you use the Adobe client data layer, add the identifier explicitly rather than assuming it propagates.
Event source: your commerce system's order event
Send from the commerce layer, server-side. Dispatcher caching makes any per-request template logic unreliable.
Dispatch to TikTok
Server events to the TikTok Events API with the ttclid, hashed contact information and a matching event_id.
Reversals where they exist
Handled at the commerce layer.
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 AEM conversions showing in TikTok?
Almost always because the ttclid never reached the commerce order behind AEM. Dispatcher caching in front of AEM serves stored output, the Adobe data layer has its own conventions that may not carry your identifier, and enterprise release cycles slow every iteration. Measure coverage before debugging the dispatch.
02What identifier does TikTok need?
The ttclid — TikTok's click identifier, appended to your landing page URL and also stored in the _ttp cookie. TikTok additionally matches on hashed email and phone. In-app browser behavior makes ttclid capture more fragile than the equivalents on other platforms, so persisting it server-side as soon as it is seen matters more here than elsewhere.
03Where should the event come from?
Your commerce system's order event. Send from the commerce layer, server-side. Dispatcher caching makes any per-request template logic unreliable.
04How do I know it worked?
TikTok Events Manager shows received events and their match status. As with Meta, arriving is not the test — deduplicated and matched is. Reconcile TikTok's reported conversions against the source system for the same window.
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 yourAEM → TikTok 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 AEM → TikTok 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 AEM and TikTok 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
95% tracking accuracy guarantee
Free 30-min consultation · from $400 · 1st-party server-side
95% guarantee · from $400
