ConversionOS destinations

ConversionOS sends conversions to three destinations: Meta (Pixel plus Conversions API, dual-fired with a shared event ID so Meta de-duplicates), Google Analytics 4 (gtag plus Measurement Protocol), and Google Enhanced Conversions for Web, which reuses your existing Google Ads connection.

Meta — Pixel and Conversions API

ConversionOS dual-fires the browser Pixel and the server-side Conversions API for every conversion, both carrying the same event ID. Meta uses that ID to de-duplicate, so you get the reliability of server-side delivery without inflated counts. This is Meta's own recommended configuration.

Verify with Meta Test Events

Meta's Test Events tool is supported directly, so you can watch events arrive and confirm de-duplication is working before you rely on the data.

Google Analytics 4

Conversions are sent through both gtag and the Measurement Protocol, so events that a browser would have dropped still reach GA4.

Google Enhanced Conversions for Web

This destination reuses the Google Ads connection you already made for fraud protection — there is no separate authentication step. If Google Ads is connected, enabling it is a toggle.

Testing a destination

Each destination has its own connection test and test fire, so you can prove one works without waiting for a real conversion or disturbing the others.

Credentials never reach the browser

OAuth and CAPI tokens are encrypted at rest and used only server-side. Nothing sensitive is exposed to your visitors.

Frequently asked questions

Do I have to remove my existing Meta Pixel?

No. ConversionOS works alongside your existing setup, and the shared event ID is what prevents double counting.

What if a destination goes down?

Deliveries retry automatically with exponential backoff, and the raw conversion is stored in AdProtektor regardless — so an outage at a destination never costs you the underlying record.