Introducing Gateway: connecting Conversions APIs takes a tag. Orchestrating them takes a platform.

Most Conversions API setups assume that once a conversion is sent, the job is done. Gateway does not. It sends each conversion only to the platform Hub credited, with the identifiers and consent Radar matched, then reads back what the platform answered. Meta, Google Ads, TikTok, X, Microsoft Ads, Reddit, OpenAI and FinanceAds are supported, and we are a registered tech provider at Meta and TikTok. We built it for teams tired of every ad platform claiming the same sale, and bidding on it.

Everything around the send

The part we spent the most time on is everything that happens around the send. Before each batch, Gateway checks the ad account's standing and the conversion's lookback window, and holds back what would be rejected. After it, every platform response is stored next to its conversion, so a mismatch takes one row to find. Failures are typed by cause: a sale no channel earned returns an attribution error code, and anything that fails for a temporary reason is resent automatically for up to 72 hours. Because dispatch is server-side, advertising consent can even be collected later, at checkout or sign-up, and the conversion waits until it is given.

What is available today

Gateway is available today alongside Radar and Hub. The initial release supports eight destinations, cross-platform deduplication, deferred advertising consent and per-conversion response history, with no field mapping to configure for any of them. You can get started at oneviewhub.com.