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 (one configured browser or Measurement Protocol route per event), and Google Enhanced Conversions for Web, which reuses your existing Google Ads connection.
On this page
Meta — Pixel and Conversions API
Configured Meta browser and server paths share event identifiers to support deduplication. Check event names and IDs in destination diagnostics, especially when other tags also send conversions.
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
New events use Measurement Protocol when a G- measurement ID and API secret are configured; otherwise a configured G-/GT- tag uses browser delivery. ConversionOS does not also send its own browser copy of an MP-owned event. The event keeps its selected route and property through retries. Browser-only delivery needs the page and tag to be available; independent merchant tags may still send duplicates. Verify GA4 reports separately from HTTP receipt. MP events do not run GA4 event-generation rules, and missing browser context can limit reporting.
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 separate setup checks and test-fire actions. Check GA4 setup validates a sample payload without adding it to reports; it does not verify the API secret or event delivery. Browser-only GA4 destinations need verification on the website and in GA4. A saved destination is configured, and a successful HTTP response is not proof that a platform processed the event. Confirm test-fire results in the destination before relying on reporting.
Dashboard test-fire exercises active server destinations only, using the same website/account credential fallback as delivery. Browser-only Google Ads, GA4 and Meta tags must be tested on your website with its consent settings; the dashboard does not execute them or create a sample purchase when no server destination is selected. Use Google Tag Assistant or Meta Test Events on the website, then verify the destination result.
Server tests send a USD 49 sample purchase and may affect destination reports. Use a designated test destination and configure a Meta test event code for Meta Test Events. Results show endpoint receipt, failure or an unconfirmed outcome for each server destination. Endpoint receipt does not establish reporting, attribution or browser delivery. Test all retains separate outcomes when one destination fails.
Destination access stays server-side
Manage destination credentials in the integration settings. A tracking key is a separate credential and does not replace the Google or Meta connection.
Frequently asked questions
Do I have to remove my existing Meta Pixel?
Follow the guide for your installation. If browser and server paths send the same conversion, align event names and identifiers and check for independent tags that might create duplicates.
What if a destination goes down?
Eligible failed deliveries are retried. Recorded events remain available under their retention policy, but failures that require new credentials or configuration need your attention.