Zero-configuration same-origin tracking
Your ads are losing conversions your analytics never sees.
Ad blockers and browser privacy limits drop a large share of browser-side conversion events before they ever reach Meta, Google or LinkedIn. ZeroConfig collects them from your own domain and forwards them server-side, so your campaigns optimise on what actually happened. Setup takes three steps and no developer.
See it set up end to end
Prefer to click around instead? Open the sandbox and load your own site — no sign-in.
Three steps, about ten minutes
No container to publish, no server to run, no data layer to design.
- 1
Sign in to your platforms
Connect Cloudflare, Meta, Google Ads and LinkedIn through each platform's own OAuth screen. You approve the access; we never see a password.
- 2
Choose what counts
Load your site and click the buttons that matter — a quote request, a booking, a checkout. No tag manager, no code, no developer ticket.
- 3
Map events to conversions
Point each event at the conversion action it should count as in every platform. A purchase and a form fill stop sharing one goal.
What we hold, and what we never touch
You are about to connect your ad accounts to something. Here is exactly what that means.
OAuth, not credentials
Every connection goes through the platform's own sign-in screen. ZeroConfig never receives, asks for, or stores a password to any of your ad accounts.
Tokens only, scoped and revocable
What we keep is the access token each platform hands back, with the narrowest scopes that work — reading your ad accounts and writing conversions. Disconnect inside ZeroConfig and we delete our copy; remove ZeroConfig in the platform's own settings and the token itself stops working.
No visitor personal data stored
Emails and phone numbers are hashed in transit and forwarded to the ad platform. Nothing identifying is written to our database — the event log records what happened and where it went, not who did it.
Your data stays on your domain
Collection runs from your own domain through a worker in your own Cloudflare account. There is no shared vendor subdomain and no CNAME cloaking.
The full detail is in the privacy policy, including every scope we request from each platform.
Start with the part that needs no trust
Load your own site in the sandbox and click the buttons you would track. Nothing is saved, and no account is required — or spend fifteen minutes with us instead.