Ambil kembali pelacakan Anda. Miliki data Anda.
Tagging sisi server menyeluruh untuk Meta, TikTok, LINE, Google, dan LinkedIn — di-deploy di cloud Anda sendiri. Tahan terhadap deprecation cookie, mengutamakan privasi, siap audit.
Dipercaya di 11 pasar Asia-Pasifik
Pasar Asia-Pasifik tercakup
Garis pertahanan
Platform iklan didukung
Data tetap di GCP Anda
Cara data mengalir
Browser menangkap sinyal. Edge Anda mengorkestrasi. Platform iklan hanya menerima yang dibutuhkan — sudah di-hash, dideduplikasi, dirutekan.
Tiga belas garis pertahanan
Dari pengambilan sinyal hingga retensi data — setiap tahap diperkuat, dapat diobservasi, dan di bawah kendali Anda.
Pengambilan sinyal first-party
Tangkap fbp / fbc / ttclid / line_uuid / gclid melalui subdomain Anda sendiri — tahan secara desain, tahan terhadap ad-blocker dan ITP.
Jembatan identitas
Pemetaan anonymous_id ↔ member_id dengan rolling lookup 30 hari. Identitas terjaga tanpa putus saat login.
Perbaikan langsung
fbp / fbc hilang saat conversion? Kami isi ulang dari riwayat sebelum event meninggalkan edge.
Deduplikasi Event-ID
FB Events Manager menampilkan 'Deduplicated'. Pixel browser + CAPI server tidak pernah double-count.
Routing Pixel
Forward penuh, pembagian rasio, peralihan berdasarkan event, peralihan berdasarkan waktu — pola apa pun, platform apa pun.
Kedaulatan data
Firestore + BigQuery di proyek GCP Anda. Akses query langsung. Tanpa vendor lock-in.
PII saat tersimpan = SHA-256
Email dan nomor telepon di-hash sebelum disimpan. Plaintext tidak pernah masuk BigQuery.
Desain modular
Jeda worker, ambil manual dari DB, kirim CAPI manual — setiap mata rantai dapat diganti.
Rute terverifikasi
Rute Cloud Scheduler melalui verifikasi OIDC + audience. Tidak ada pemicu tidak sengaja.
Tingkat pencocokan ditingkatkan CRM
Unggah member_id / email / phone. Kami hash dan lampirkan otomatis — kualitas pencocokan naik.
Otomasi audience
Pemindaian kondisi memicu replay CAPI otomatis untuk conversion yang terlewat.
Retensi yang Anda kendalikan
Default 730 hari dengan auto-purge di BigQuery + Firestore. Sesuaikan per regulasi.
Observabilitas bawaan
Metrik sukses / gagal permanen per event, mode Worker bypass, taksonomi error_kind terstruktur.
Dipercaya di Asia-Pasifik
Logo bersifat ilustratif sambil menunggu izin publikasi pelanggan.
Pertanyaan yang sering diajukan
Dua belas pertanyaan yang paling sering ditanyakan pembeli. Tidak ada 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 pelacakan Anda seperti yang belum pernah Anda lihat
Walkthrough dua puluh menit. Data CRM tidak meninggalkan perimeter Anda.