Ad blockers erase up to 40% of your events. TrackAPI recovers them all — server-side, through your own domain, invisible to any blocker.
No credit card · 2,500 free events · Cancel anytime
Your site
SDK + GTM
First-party CNAME
TrackAPI
Server-side
simultaneous
Your site
SDK + GTM
First-party CNAME
TrackAPI
Server-side
simultaneous
Client-side tracking
0.0 EMQ
high cost per conversion
With TrackAPI
0.0 EMQ
maximum optimization
What can't be seen can't be blocked — and can't be charged to you.
Your events travel through your own subdomain — the browser treats them as your site's traffic. No ad blocker can tell the difference. Your data always arrives.
Automatic deduplication with a unique event_id across pixel and CAPI — Meta receives clean data and optimizes better. You pay per deduplicated conversion, not per fire or retry.
A single SDK fire delivers simultaneously to Meta CAPI, TikTok Events API and GA4 — and counts as one event, with no per-destination cost. No separate setup, no extra latency.
Import our GTM template, paste your Project ID and publish. Done. Works on any site — Shopify, WordPress, landing page or custom e-commerce.
A real-time dashboard shows which events fired, to which platforms and with what success rate. Catch failures before they cost you money.
Each project has its own CNAME, integrations and isolated analytics. Perfect for agencies managing multiple advertisers — without mixing data.
No server of your own. No complex code. Just copy, paste and publish.
A DNS record at your provider: your subdomain → TrackAPI. SSL provisioned automatically. No server, no infrastructure.
~2 minImport our template from the GTM Gallery, paste your Project ID and publish. Works on any site — without touching the code.
~3 minEach event gets IP, user agent and visitor data. Personal data is hashed before any send — never stored.
< 50msMeta CAPI, TikTok and GA4 receive events simultaneously, with automatic deduplication. High EMQ, low cost per conversion.
ParallelReal metrics from active projects on TrackAPI
Average Event Match Quality
High EMQ = lower cost per conversion
For the first event to arrive
From zero to active tracking, no code
Uptime over the last 90 days
Your events never stop arriving
What is Event Match Quality (EMQ)?
It's Meta's score (0–10) that measures the quality of the data sent to CAPI. The higher the EMQ, the better the optimization algorithm and the lower the cost per conversion. More data = more optimization = more ROAS.
Client-side
0.0
With TrackAPI
0.0
Who TrackAPI is for
Media Buyers
Recover lost data and improve your campaigns' ROAS.
Performance Agencies
Manage every client with isolated CNAMEs and analytics.
E-commerce
Track purchases, carts and leads without relying on the browser.
Course Creators
Optimize campaigns with complete data, not estimates.
A lost event can cost you a sale. The simplest plan costs less than what you're losing each month.
Event = 1 deduplicated conversion (unique event_id). Retries, repeated fires and container loads don't count — unlike GTM Server-Side's per-request billing.
Coming from GTM Server-Side? 1 request ≠ 1 event.
There, every script load and every hit counts as a request — a single pageview becomes 2-3 requests. Here, that's 1 event. Before comparing price, divide your request volume by ~2-3.
Try it with no commitment — validate before you pay
2,500 events/mo
1 project · 1 CNAME
For those advertising on 1 to 3 sites
50,000 events/mo
3 projects · 3 CNAMEs
For teams and higher-volume advertisers
250,000 events/mo
10 projects · 10 CNAMEs
For agencies managing multiple clients
1,000,000 events/mo
Unlimited projects and CNAMEs
800,000
Estimate based on ~2.5 requests per event — in sGTM each request includes script loads (gtm.js, gtag.js) and every hit, so a pageview becomes 2-3 requests. Here, 1 event. The real number varies with your setup.
Above 1,000,000 events?
Talk to salesAll plans include first-party CNAME, automatic deduplication and 5-minute setup. No contracts. Cancel anytime.
Straight answers so you can decide with confidence
Yes — if you're losing events, you're paying for optimization on incomplete data. Ad blockers and browser restrictions wipe out up to 40% of conversions before they reach Meta. With server-side tracking, the algorithm gets the real data and optimizes for what's actually working. The result: lower cost per conversion and higher ROAS.
No — you can install it without coding. Directly in HTML it's two lines of script (the fastest path, ~5 minutes). Through Google Tag Manager you don't touch the code, but you import our template from the Community Gallery and configure a few variables and the pixel tag — about 15-20 minutes the first time. Both paths have step-by-step guides in the dashboard.
A CNAME is a simple DNS record pointing one of your subdomains (e.g. analytics.yoursite.com) to TrackAPI. With it, events appear as first-party to the browser — the main reason for blocking disappears. The CNAME is included in every plan. Setting it up takes ~2 minutes at your DNS provider (Cloudflare, GoDaddy, etc.).
No. Each event carries a unique event_id generated by the SDK. That same ID travels through the browser pixel and TrackAPI CAPI — Meta identifies and discards the duplicate automatically. You see each conversion counted exactly once in Events Manager.
Meta CAPI (Facebook and Instagram), TikTok Events API and Google Analytics 4 (Measurement Protocol). All three receive events simultaneously from a single SDK fire. No separate setup per platform.
Yes. Personal data (email, phone) is hashed with SHA-256 before any send — it's never stored in plain text. Integration tokens are encrypted with AES-256-GCM. We comply with LGPD. You can review our privacy policy at any time.
On the Free, Starter and Pro plans, tracking pauses when you hit the monthly limit. You get email alerts at 80% and 100% — with plenty of time to upgrade. On the Agency plan, events keep flowing at $0.10 per 1,000 extra: your tracking never stops.