Tuntut semula penjejakan anda. Miliki data anda.
Tagging sisi pelayan hujung-ke-hujung untuk Meta, TikTok, LINE, Google dan LinkedIn — dilancarkan dalam awan anda sendiri. Tahan terhadap deprecation kuki, mengutamakan privasi, sedia untuk audit.
Dipercayai di 11 pasaran Asia-Pasifik
Pasaran Asia-Pasifik dilindungi
Garis pertahanan
Platform iklan disokong
Data kekal dalam GCP anda
Bagaimana data mengalir
Pelayar menangkap isyarat. Edge anda mengawal. Platform iklan hanya menerima yang diperlukan — sudah di-hash, di-deduplikasi, dihala.
Tiga belas garis pertahanan
Daripada penangkapan isyarat hingga penyimpanan data — setiap peringkat diperkukuh, boleh diperhatikan, dan di bawah kawalan anda.
Penangkapan isyarat first-party
Tangkap fbp / fbc / ttclid / line_uuid / gclid melalui subdomain anda sendiri — tahan dari reka bentuk, kebal terhadap ad-blocker dan ITP.
Jambatan identiti
Pemetaan anonymous_id ↔ member_id dengan rolling lookup 30 hari. Identiti kekal lancar selepas log masuk.
Pembaikan segera
Hilang fbp / fbc semasa conversion? Kami isi semula daripada sejarah sebelum event meninggalkan edge.
Deduplikasi Event-ID
FB Events Manager memaparkan 'Deduplicated'. Pixel pelayar + CAPI pelayan tidak pernah double-count.
Penghalaan Pixel
Forward penuh, pembahagian nisbah, peralihan berasaskan event, peralihan berasaskan masa — sebarang corak, sebarang platform.
Kedaulatan data
Firestore + BigQuery dalam projek GCP anda. Akses query terus. Tiada vendor lock-in.
PII semasa simpan = SHA-256
E-mel dan nombor telefon di-hash sebelum disimpan. Plaintext tidak pernah masuk BigQuery.
Reka bentuk modular
Jeda worker, ambil manual daripada DB, hantar CAPI manual — setiap mata rantai boleh diganti.
Laluan disahkan
Laluan Cloud Scheduler melalui pengesahan OIDC + audience. Tiada pencetus tidak sengaja.
Kadar padanan dipertingkatkan CRM
Muat naik member_id / email / phone. Kami hash dan lampirkan secara automatik — kualiti padanan meningkat.
Automasi audience
Imbasan keadaan mencetuskan replay CAPI automatik untuk conversion yang terlepas.
Penyimpanan yang anda kawal
Lalai 730 hari dengan auto-purge merentas BigQuery + Firestore. Sesuaikan setiap rejim regulasi.
Pemerhatian terbina dalam
Metrik kejayaan / kegagalan kekal per event, mod Worker bypass, taksonomi error_kind berstruktur.
Dipercayai di Asia-Pasifik
Logo bersifat ilustrasi sementara menunggu kebenaran penerbitan pelanggan.
Soalan lazim
Dua belas soalan paling kerap ditanya pembeli. Tiada milik anda? Hubungi kami.
-
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.
Lihat penjejakan anda seperti yang anda belum pernah lihat
Walkthrough dua puluh minit. Data CRM tidak meninggalkan perimeter anda.