Skip to content

Events Log

The Events Log is the per-integration record of events a conversion source sent into AnyTrack — each entry with its payload, identifiers, and timestamps. It answers one question: did AnyTrack record this event?

The Events Log exists only on Integrations — the inbound side of the dashboard. Ad-platform Tracking Pixels have no Events Log; a customer who cannot find one under Google Ads or Meta is not missing anything from their setup. Point them at the integration that sends their conversions (their store, funnel, or network) — that is where the log lives.

What the Events Log proves — and what it doesn’t

Section titled “What the Events Log proves — and what it doesn’t”

An entry in the Events Log proves AnyTrack recorded the event. It is not a delivery receipt from an ad platform, and no AnyTrack screen shows the raw per-event API response from Meta or Google — delivery is verified in the platform’s own tools.

The Events Log is the first check whenever conversions seem missing or delayed on an ad platform: if the event was never recorded, no amount of platform processing time will make it appear. Confirm the event exists in the log, then — and only then — reason about platform-side delays, attribution windows, or conversion-action settings.

Frequently asked questions

FAQ was last reviewed on 2026-08-01

Where do I see exactly what AnyTrack sent to Google Ads or Meta?
No screen shows the raw per-event API response from an ad platform. The Events Log proves AnyTrack recorded the conversion from its source; delivery to the platform is confirmed in the platform's own tools (such as Meta Events Manager).
A conversion is delayed in Google Ads. What should I check first?
Check the Events Log (and Conversions Report) first: if the conversion is not there, AnyTrack never recorded it and Google will never receive it — the delay is not the issue. Only apply platform processing-time explanations after confirming the event exists.