Skip to content
OverviewServer-side trackingConversion APIAnalytics and reportingAI AttributionAudience SyncMCP serverIntegrations
Feature · Conversion API

Every conversion delivered, and proof that it was

Convultra speaks to each ad platform's conversion API directly, server to server. Every event gets a destination, a status and the platform's own response, so a broken connection is visible the same day rather than at month end.

Start free trial Read the setup guide
Per event Delivery status and platform response
90 days Google Ads click window preserved
Retries Automatic, with manual retry in the log
0 Conversions counted twice
How it works

From your server to theirs

01
Record The conversion arrives from the browser, the plugin or your backend, with value, currency and an order ID.
02
Match The stored click ID and hashed customer data are attached, so the platform can credit the right ad.
03
Deliver Sent to Google Ads over its conversion upload API with enhanced conversions, and to OpenAI Ads over its conversions API. Meta CAPI, Microsoft Ads and TikTok Events API are coming soon.
04
Confirm The platform's response is logged against the event: delivered, pending, failed, and the reason in plain English.
delivery logexample row 
event      purchase · ORD-12345 · $149.00
platform   Google Ads
status     delivered
attempt    1 of 3 · 2026-09-14 09:14:22 UTC
response   accepted, enhanced conversion matched
backendserver-side install 
POST https://tracking.convultra.com/v1/track

event      purchase
value      149.00 USD
order id   ORD-12345
email      alex@example.com · hashed before it reaches a platform
In the product

What you see once it is running

Conversion delivery summary in Convultra: sent, delivered, failed and pending counts with the delivery rate, failures by platform with value at risk, and a failures over time chart with the tooltip open for one day, showing 7 failed and 44 delivered.
Delivery summary · what arrived, what failed, and what it was worth
Conversion delivery attempts list in Convultra showing each conversion, its value, the platform destination, attempt count, the platform response and a Delivered, Retrying, Failed or Pending state.
Attempts · per-event status with the platform response
What the log shows

Questions the delivery log answers

Did it arrive? Delivered, pending or failed, per event and per platform, with timestamps and attempt counts.
Why did it fail? A plain-English reason, not the platform's raw error. Click not recognized, outside the window, connection expired.
Can I retry? Failed deliveries can be retried from the log or the API while the platform window is still open.
How much is at risk? The revenue behind failed deliveries, deduplicated by conversion, so you know what a broken connection is costing.
Was it deduplicated? Shared event IDs mean the platform collapses the browser and server pair rather than counting both.
Which platforms are next?Coming soon Meta, Microsoft Ads and TikTok forwarding are coming soon on the same log and the same mapping.
Specifics

For whoever asks the technical questions

Google Ads Conversion upload API with enhanced conversions, live
OpenAI Ads Conversions API on the oppref click ID, live
Meta Conversions API, coming soon
Microsoft Ads Conversion upload with msclkid, coming soon. Spend sync live
TikTok Events API, coming soon
Deduplication Shared event ID, four configurable windows
Retry Automatic, then manual from the log or API
Windows Google Ads 90 days, OpenAI Ads 7 days. Microsoft Ads 90 days and Meta 7 days once forwarding ships
Access Delivery log in the dashboard, REST API and MCP (beta)

Before you install

Is this the same as Meta CAPI or Google's conversion upload?

It uses those APIs. Convultra is the product on top: it stores the click ID, hashes the customer data, attaches a shared event ID, sends the event, and logs the response. You connect an account instead of building the integration.

What happens when a delivery fails?

It is retried automatically. If it still fails, the log shows the reason in plain English and you can retry it manually while the platform's window is open. The revenue at risk is totaled so you can see what a broken connection costs.

Will my conversions be counted twice?

No. Convultra attaches a shared event ID to the server event, and the same ID travels with your existing pixel event, so the platform collapses the pair.

Can I read the log programmatically?

Yes. The REST API and the MCP server (both in beta) expose the delivery log, a delivery summary and a retry operation.

Next

Pairs with

Server-side tracking The first-party collection that feeds the log. Analytics and reporting Revenue, spend and ROAS on the same numbers the log delivers. AI Attribution Assistant traffic named, with conversions attached.

Stop guessing whether it got there.

Start free trial Read the docs