Reclaim your tracking. Own your data.
End-to-end server-side tagging for Meta, TikTok, LINE, Google, and LinkedIn — deployed inside your own cloud. Cookie-resilient, privacy-first, audit-ready.
Trusted across 11 Asia-Pacific markets
Asia-Pacific markets covered
Lines of defence
Ad platforms supported
Data stays in your GCP
How the data flows
Browser captures the signals. Your edge orchestrates them. Ad platforms get only what they need — hashed, deduplicated, routed.
Thirteen lines of defence
From signal capture to data retention — every stage is hardened, observable, and yours to govern.
First-party signal capture
Capture fbp / fbc / ttclid / line_uuid / gclid via your own subdomain — resilient by design, ad-blocker and ITP-tolerant.
Identity bridge
anonymous_id ↔ member_id mapping with 30-day rolling lookup. Identity persists seamlessly through login.
Repair on the fly
Missing fbp / fbc on a conversion? We backfill from history before the event leaves your edge.
Event-ID dedup
FB Events Manager shows ‘Deduplicated’. Browser pixel + server CAPI never double-count.
Pixel routing
Full-fanout, ratio split, event-based switching, time-based switching — any pattern, any platform.
Data sovereignty
Firestore + BigQuery in your GCP project. Direct query access. No vendor lock-in.
PII at rest = SHA-256
Email and phone are hashed before storage. Plaintext never lands in BigQuery.
Modular by design
Pause the worker, fetch from DB manually, fire CAPI by hand — every link is replaceable.
Verified routes
Cloud Scheduler routes go through OIDC + audience verification. No accidental triggers.
CRM-augmented match rates
Upload member_id / email / phone. We hash and attach automatically — match quality up.
Audience automation
Condition-scan triggers automatic CAPI replays for missed conversions.
Retention you control
730-day default with auto-purge across BigQuery + Firestore. Tune per regulatory regime.
Observability built-in
Per-event success / permanent-failure metrics, Worker bypass mode, structured error_kind taxonomy.
Trusted across Asia-Pacific
Logos shown are illustrative pending customer publication permission.
Frequently asked questions
Twelve questions buyers ask most. Missing yours? Reach out.
-
What is server-side Google Tag Manager and why does it matter?
Server-side GTM (sGTM) moves your tag execution from the browser to your own server. It survives ad-blockers and browser tracking-prevention features (Safari ITP, Firefox ETP). For TopAdsROI, sGTM also means your ad measurement data lives in your GCP project — never on a vendor’s server. -
How is TopAdsROI different from Stape, Addingwell, or gtmserver.com?
Those are great hosted solutions, but they store your data on their infrastructure. TopAdsROI deploys into your own GCP, with Firestore and BigQuery in your project — you have direct query access, your retention policy, your region. We also pre-model 11 Asia-Pacific regulatory regimes; the others ship a generic platform. -
Where is customer data stored?
Inside your own Google Cloud Platform project, in the region you choose: Sydney (australia-southeast1), Tokyo (asia-northeast1), or Singapore (asia-southeast1). Email and phone are SHA-256 hashed before they hit Firestore or BigQuery — plaintext PII never persists. -
Which ad platforms do you support?
Meta Conversions API (CAPI), TikTok Events API, LINE Conversion API, Google Ads, and LinkedIn Insight Tag CAPI on day one. We add new platforms quarterly based on customer demand. -
Do you support LINE Conversion API?
Yes — and natively. LINE is a primary channel in Japan, Taiwan, and Thailand, so we built first-class LINE CAPI integration alongside Meta and TikTok. -
How do you comply with the Australian Privacy Act 2024 reform?
Our policy template aligns with the Australian Privacy Principles (APP), automated-decision disclosure (Schedule 1, Part 15), and the NDB (notifiable data breach) scheme. Your DPO inherits a working template instead of starting from a blank page. -
How do you comply with Japan APPI?
We honour third-party-provision consent and the external-transmission rules introduced in 2022. Cross-border transfer disclosures are pre-drafted in Japanese. -
How long does deployment take?
Typical pilot deployment is 5–10 business days from kickoff to first event flowing through your edge. Full multi-platform rollout (Meta + TikTok + LINE + Google + LinkedIn) usually completes within 30 days. -
What is the SLA?
We target 99.9% availability of our edge and orchestration layer. Workers-bypass mode lets ops manually replay events from your data store if any link in the chain degrades. Detailed SLAs are in your order form. -
How is pricing determined?
Pricing is calibrated to four variables: monthly event volume, number of active markets, ad platforms in scope, and data residency choice. Three commercial models — pay-as-you-go, subscription, or perpetual buyout. Talk to us for a tailored quote. -
Can we self-host on our own GCP?
Yes — that’s the default deployment model. We deploy into your GCP project so the data never leaves your perimeter. We retain operational responsibility under a Data Processing Addendum. -
What happens if we cancel?
You keep your GCP project and the data in it. We export configuration to a customer-specified bucket and disconnect within 60 days. No vendor lock-in.
See your tracking like you’ve never seen it before
Twenty-minute walkthrough. No CRM data leaves your perimeter.