# Events Log

> The per-integration log of events a conversion source sent into AnyTrack — proof an event was recorded, not a delivery receipt from an ad platform.

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

## Direction: the Events Log is inbound only

The Events Log exists **only on Integrations** — the inbound side of the dashboard. Ad-platform [Tracking Pixels](/glossary/tracking-pixel) 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

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 diagnostic gate

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.
