Integrations

Do you support …?

Almost every first conversation starts with that question. Here is the complete answer — sorted by direction: where we send your conversions, and where we receive orders, leads and calls from.

And if your platform isn't on the list, further down you'll find the honest reason why.

Book a 30-min demo Jump to the list
One pipeline instead of many pixels
Every destination delivered separately
Consent checked per destination
Connected

These platforms are already wired up.

Destinations on top, sources below. Hover to pause the band.

17
destination platforms we send to —
plus one generic signed webhook
13
sources we receive orders, leads,
calls and revenue from
1
pipeline for all of them —
not one tag per platform
Why this is different

One pipeline. Every destination. One consent gate.

What sets this apart isn't the length of the list, it's the architecture: every event is captured once and stored once — and only then delivered to each destination separately.

One event, many destinations

Instead of maintaining a separate tag in the browser for every platform, each event is captured once on the server. Adding a platform? The data stream stays the same — nothing changes in the visitor's browser.

Every destination on its own

Each delivery is its own job. If one platform API isn't responding, exactly that one delivery is retried — the other destinations already have the event. A reconcile job checks every 10 minutes whether every conversion truly arrived.

Consent checked per destination

Before every single delivery the consent is checked again — analytics destinations need analytics consent, advertising destinations need marketing consent. If consent is withdrawn later, the event simply stops going out.

A new platform is one adapter

When a destination is added, we add an adapter — the queue, the retries, the consent check and the monitoring are already there. No rebuild on your side, no new snippet, no re-testing across all your pages.

Platform updates are our problem, not yours. Interface versions get retired on a regular basis. A version radar continuously probes the platform interfaces and tells us when a newer version is live or the one in use is sunsetting — we follow along centrally, without anyone on your side having to touch a thing.

Your platform is on the list? Then let's connect it.

Book a 30-min demo
Runs alongside your existing tracking · compare first, then decide
Direction 1 · Outbound

Where we send your conversions.

All server-to-server, over each platform's official interface. Every destination receives the same event in the shape it expects — with click IDs, hashed identifiers and the real value.

Google Ads — including Google's Data Manager path for new accounts
Meta Conversions API — deduplicated against a running pixel
Google Analytics 4 — Measurement Protocol
Microsoft Ads — offline conversions
TikTok Ads — Events API
LinkedIn Ads — Conversions API
Pinterest Ads — Conversions API
X Ads — Conversions API
Snapchat Ads — Conversions API
Reddit Ads — Conversions API
Klaviyo — purchase and lead events for flow triggering
Brevo — Events API
CleverReach — recipient upkeep in your groups
Iterable — events and purchases
Customer.io — Track API, EU or US region
Awin — affiliate sales server-to-server
Matomo — privacy analytics, when the data has to stay in Europe
Signed webhook — Zapier, Make, n8n, HubSpot and any system of your own
The signed webhook is the universal interface. It sends the same event, HMAC-signed, to an address of your choice — so you can also reach tools that have no dedicated adapter: automation platforms, your CRM, your own backend. You decide which fields travel with it.
Direction 2 · Inbound

Where we receive orders, leads and calls from.

Before anything can be sent, it has to arrive — and it has to arrive where the truth is created: in the store system, the phone system, the booking calendar, the CRM, the accounting tool. Not in the browser.

WooCommerce — orders and refunds by webhook, plus a backfill from the store API
Shopify — web pixel, order webhook and cart bridge
Google Merchant Center — product performance and disapproved products with reasons, feeding the product ROAS (read access)
Google Keyword Planner — search volume, competition and CPC ranges, available right in the data chat
Detected on your site — Google Tag Manager and consent tools such as Borlabs, Cookiebot, Usercentrics, Complianz appear automatically in the integrations overview
Shopware 6 — via the Flow Builder
JTL — via the Wawi workflow
Stripe — for subscription and payment revenue
WordPress forms — Elementor, Contact Form 7, Gravity Forms and more, detected automatically
Telephony / Sipgate — calls with duration, source and campaign
Microsoft Bookings — appointments via Microsoft Graph
Calendly — bookings by webhook
Cal.com — bookings by webhook
CRM feedback loop — HubSpot and Pipedrive report the won deal back
Accounting — lexoffice and sevDesk report the paid invoice
Open ingest API — for everything else: your own system sends straight to us
The feedback loop is the part pixel setups simply don't have. When a lead turns into a won deal in the CRM, or the invoice gets paid, we restate the value of the original conversion — so the ad platform optimizes for paid invoices instead of form fills. More on that under Calls & leads.

Your platform is on the list? Then let us look at what data it would actually receive.

Book a 30-min demo
30 days parallel operation: €0 · Runs alongside your existing tracking · cancellable monthly
What you rely on

A list is quick to write. Delivery is the work.

Connecting a platform means little if delivery fails silently. That is why the effort here is not in the length of the list, but in what happens after.

Stored first, then sent

Every event is in your database before any destination sees it. If a platform interface goes down, the event is not lost — it is re-delivered as soon as the interface answers again.

We notice before you do

More than 20 watchdogs check operations around the clock. One of them looks specifically for conversions that still have no delivery result after twelve hours — the gap shows up the same day, not in the monthly report.

The delivery rate is in the report

What share of your conversions arrived at which platform sits in the client report and on a status page of its own. No trust required, you can see it yourself.

Servers in Germany, your data stays yours

Processing in Germany, a data processing agreement under Art. 28 GDPR, personal data hashed. And a raw data export is available at any time — leaving is built in too.

At first we did not believe the uncoverflow numbers ourselves and checked every single order against the shop. They held up. Since then we plan our budgets by these numbers instead of what the platforms claim.
Robert, Rankist Robert · RankistOne of two Shopify Plus agencies in Switzerland
2.5M+
events per month
run through this pipeline
20,000+
orders per month
are delivered through it
2,129
orders on a single day
— captured, deduplicated, delivered
What we don't connect

And why that's a good sign.

We only connect a platform when there is an official, documented server interface for it — with a specification we can verify against a real account. If that doesn't exist, we don't build on a hunch.

The reason is uncomfortably concrete: undocumented endpoints often answer “OK” even when they discard the data. An adapter like that would look green in the dashboard and deliver nothing for months — the most expensive class of failure there is, because nobody notices it. We would rather tell you upfront that a destination isn't possible than sell you a silent outage.

In practice: if your platform isn't listed here, ask us anyway. If an official interface exists, the adapter is a manageable piece of work — the pipeline around it already stands. And until then, you can usually reach the system through the signed webhook or an automation platform.

Common questions

Answered briefly.

Do we have to switch off our existing pixels?
No. uncoverflow runs alongside your existing setup — that's the recommended way to start: compare first, then decide. The purchase and the server-side report carry the same event ID, and Google and Meta deduplicate on it. A watchdog also alerts us if a native tag and our delivery would both count as primary.
How many destinations can we serve at once?
As many as you like — delivery to each destination is its own job. A slow or failing destination doesn't hold up the others, and every destination is retried independently until the event has arrived.
Our store is custom-built — does that work too?
Yes, through the open ingest API: your system sends the order to us directly with its own key, in the same shape as any other source. Everything after that — attribution, consent check, delivery to every destination — happens exactly as it would for a Shopify or WooCommerce store.
What happens when a platform changes its interface?
A version radar continuously probes the interfaces and tells us when a newer version is live or the one in use is sunsetting. We follow along centrally — for all customers at once, with no work on your side.
Read on

This goes with it.

Shops & orders →

How the purchase gets booked server-side — express checkout, refunds and attribution rescue included.

Calls & leads →

Which ad made the phone ring — and how a lead later turns into its real deal value.

Let's talk for 30 minutes.

Tell us your ad accounts, your store system and your tools — we'll tell you in the call what gets connected directly and what runs through the webhook.

Book a demo Or start with the intro gift: a free keyword analysis →
Reply within 24 hours on business days · conversations in English and German · no lock-in, cancel monthly