Blocked before they leave
Content blockers stop requests to third-party pixel domains. A request to your own domain is not third party, so it is not on those lists.
Server-side tracking · runs on your own Cloudflare account
Tracking that actually arrives.
Content blockers, Safari and closed tabs quietly drop browser pixels. TRACSA collects each event once on your own domain and delivers it from your server to every ad and analytics tool — consent enforced, duplicates removed, and a record of what each tool answered.
- GA4
- Google Ads
- Meta
- Snapchat
- TikTok
- more coming
Three quiet leaks
None of them show up as an error. The numbers simply come in low.
Cut short by Safari
Cookies written by scripts are capped at seven days. Customers who come back next month look like new visitors, and the first ad that found them gets no credit.
Lost at the till
The order page is the one people close fastest, and the one that matters most. Orders sent from your backend do not depend on a tab staying open.
One event in, every tool out
Keep the dataLayer you already have. TRACSA does the rest on the way through.
-
1
Your site
One tag in
<head>. It reads your existing data layer, plus clicks and pages you never tagged. -
2
Your domain
Events go to
t.yoursite.com, a Cloudflare Worker in your own account. Not to Google or Meta. -
3
Consent and mapping
Your consent tool decides who gets what. Emails and phone numbers are hashed the way each vendor requires.
-
4
Every tool
Sent server to server, with one event ID shared with your browser pixel so nothing is counted twice.
Press a button. Watch what each tool receives.
This is the real mapping, with the field names each API expects. Flip consent and watch the tools change.
Acme Storedemo
Runner 2
€129.90 · red
Click a button to send one event.
No more “it should be working”
Every event keeps its answer from every tool. When a number looks wrong, you look it up instead of guessing.
- The exact request TRACSA built, with credentials hidden.
- What the tool said back, in its own words.
- Which events consent stopped, and why.
- What a tool refused, so you can fix the cause.
What you get
Not a pipe with a config file. The whole job, from finding your events to proving they landed.
AutoDL
Scans your live site, finds the tags and data layer already there, watches what happens when you click, and writes the rules for you.
Chrome extension
Run that scan on any page, even ones that block bookmarklets, and read the server's answer per tool while you browse.
Consent, enforced
Your banner decides. Each tool gets full data, stripped data, or nothing. Google Consent Mode is read automatically.
Counted once
One event ID is shared with your browser pixels, and the same order sent twice is dropped for 48 hours.
Stage, then Live
Publish runs your checks, stores a version, then tests the mapping with sample events. Promote when it passes, or roll back.
Nothing lost when a tool is down
Failed deliveries are tried again five times over six hours. What never gets through is listed for you to fix and replay.
TRACSent, our own consent banner
An add-on, priced separately. A banner that asks once, keeps the answer on your own domain, tells every tool what each visitor agreed to, and records decisions without storing anyone's address.
AI that does the setup with you
Ask in plain words, with your own ChatGPT, Claude, Gemini or Grok key. It checks your setup, explains problems, and proposes changes as buttons you approve one by one, each with an undo.
Many sites, one place
Agencies and groups keep every client or domain in one workspace, each with its own page counts, so you can see which sites are healthy at a glance.
Built for a team
Accounts with roles, company sign-in, write keys per source, and an audit log that names the person, not a shared token.
Web, apps and backend
A browser tag, Kotlin and Swift SDKs, a JavaScript SDK for Node and edge, and a plain HTTP endpoint for everything else.
Where it sits
| Browser pixels only | Hosted CDP | TRACSA | |
|---|---|---|---|
| Runs on your own domain | No | Usually extra | Yes |
| Survives content blockers | No | Yes | Yes |
| You hold the data and the keys | No | On their servers | Your Cloudflare account |
| Cost as you grow | Free, but lossy | Per event | Your Cloudflare bill |
| Answer from each tool, per event | No | Sometimes | Always |
| Finds the events you forgot to tag | No | No | AutoDL |
| Code you can read and change | No | No | Yes |
Hosted platforms do more than TRACSA in some areas — warehouse loading, audience syncing and support contracts among them. If you want those today, buy them. If you want your own tracking to arrive and to see proof, this is lighter.
What it costs
Two bills, and the smaller one usually surprises people. Running it is paid to Cloudflare, not to us, and comes to a few dollars a month at normal shop volumes. TRACSA is the plan below — run it yourself for nothing, or have it run for you.
A page view, an add to cart and an order are three events. A busy shop doing 30,000 orders a month lands near 3 million.
Cloudflare, paid to Cloudflare$5.25
TRACSA, self-hostedFree
Total to run it yourself$5.25 a month
Self-hosted
You deploy it, you run it.
Free
Your Cloudflare bill only
- Every feature of the tool itself. Optional add-ons are licensed separately.
- The whole code, yours to change.
- Deploy in three steps, about ten minutes.
- Questions answered in the repository.
Managed
One shop or site. We keep it running.
€149/month
Billed monthly. Cancel any month.
- Set up in your own Cloudflare account, so the data stays yours.
- Your tools connected and your events mapped for you.
- Updates, monitoring and the delivery queue watched.
- Answers by email within one working day.
Agency
Several brands or clients.
€599/month
Up to 10 sites. More by arrangement.
- Everything in Managed, for every site.
- New client sites set up for you.
- A named person, and a call when you need one.
- Reports you can put your own name on.
TRACSent is TRACSA's own consent banner, an add-on priced separately from the plans above. It is licensed per site, runs on your own server like the rest, and keeps consent records without storing anyone's address. Ask us about it.
What the others list, at a million events a month
| Tool | List price | What that buys |
|---|---|---|
| Stape | $20/month | Server-side GTM hosting, 500,000 requests. Their servers. |
| Addingwell | €90/month | Server-side GTM hosting, 1,000,000 requests. Their servers. |
| RudderStack | $265/month | A full customer data platform, 1,000,000 events. Their servers. |
| TRACSA self-hosted | about $5/month | Everything, on Cloudflare, in your own account. |
| TRACSA managed | €149/month + about $5 | The same, set up and watched for you. Still your account. |
Published list prices, checked 26 September 2026; check them yourself before you decide. They are not the same product: Stape and Addingwell host server-side GTM, RudderStack is a customer data platform with warehouse loading and audiences that TRACSA does not have. What TRACSA gives you instead is ownership — the code, the keys and the infrastructure stay yours.
Prices exclude VAT. Cloudflare bills you directly for what the Worker uses. One-off work — moving from another tool, a tracking plan, training your team — is quoted separately.
Start where you like
Take the free path and pay nothing. If it earns its place, ask us to run it. Nothing is locked: the managed plan uses the same code in your own Cloudflare account, so you can take it back whenever you want.
- No per-event price, at any plan.
- No seat count. Invite your whole team.
- Your credentials and your data stay in your account.
Managed and Agency plans: email hello@example.com
Deploy it yourself
3 steps
- Deploy the Worker to Cloudflare.
- Add two secrets, create your account.
- Paste one tag in
<head>.
Questions people ask
Does this replace Google Tag Manager?
No. Keep pushing to your dataLayer exactly as you do now. TRACSA reads those pushes and takes over the sending. Most shops need no new pushes at all, because the GA4 e-commerce preset already covers them.
What about consent and privacy law?
You decide what each tool may receive; TRACSA enforces it on every event and records the decision. Contact details are hashed before any tool sees them, and never go to GA4 at all. That is a tool, not legal advice — your privacy counsel still sets the rules.
Will my numbers double if I keep the pixels?
No. TRACSA sends the same event ID your browser pixel uses, which is how Meta, TikTok and Snapchat remove the duplicate. The same order sent twice to TRACSA is dropped for 48 hours.
Do I need a developer?
For ten minutes, to paste the tag and point a subdomain at the Worker. After that the rules are point and click, and AutoDL suggests most of them by watching your own site.
What happens when a tool has an outage?
The event is kept and tried again after 30 seconds, 2 minutes, 10 minutes, 1 hour and 6 hours. Anything that still fails is listed with the reason, so you can fix the cause and send it again.
Is it finished?
It delivers to GA4, Google Ads, Meta, Snapchat and TikTok today, with accounts, roles, write keys, encrypted credentials and a retry queue. Microsoft Ads, LinkedIn, Pinterest and warehouse exports are not built yet. The roadmap is in the repository, honest about what is missing.
Find out what you have been missing.
Open the dashboard, scan your own site with AutoDL, and see which of your buttons send nothing at all.