Server-side event APIs

Server-to-server conversion APIs (Meta CAPI, TikTok Events API) deliver attribution even without cookies.

What we check

Detects server-to-server conversion APIs: Meta CAPI, TikTok Events API, LinkedIn CAPI, Enhanced Conversions.

Why it matters

Server-to-server conversion APIs (Meta CAPI, TikTok Events API) deliver attribution even without cookies.

Common causes

Paid campaigns run, but conversion measurement hangs entirely on the browser pixel.
CAPI was activated in the ad account but sends without a consistent event_id, conversions count twice or get discarded.
Enhanced Conversions are on in the Google Ads account, but the hashed fields never come out of the tag.
The site runs no paid campaigns, then the finding is expected and not an error.

The fix

If you run paid performance: enable Meta CAPI or Enhanced Conversions alongside the pixel/tag.

Matching template

GA4 and Google Ads Consent Mapping

Documents which data flows from GA4 to Google Ads and which signal governs each flow.

Get the worksheet →

Check it yourself first

The Tracking Check tests this point along with all the others, in seconds.

Start the Tracking Check →

Asked often

What does a failing "Server-side event APIs" check mean?

Server-to-server conversion APIs (Meta CAPI, TikTok Events API) deliver attribution even without cookies. If you run paid performance: enable Meta CAPI or Enhanced Conversions alongside the pixel/tag.

How do you fix a failing "Server-side event APIs" check?

If you run paid performance: enable Meta CAPI or Enhanced Conversions alongside the pixel/tag.

The fix, delivered

Wired up in days, not sprints.

Findings from the Tracking Check go into a ranked sequence with effort estimates in the Audit Sprint, every module with an acceptance criterion.

To the service Request an Audit Sprint