The Event log, deliveries and the data-flow record

Open Event log from the sidebar. It shows every event Kalman received and exactly what it sent to Meta. No names, emails or intake answers are stored there.

Inbound events

The Inbound events tab lists events from your tag and webhooks, newest first, 50 per page. Use Newer and Older to page through them. Each row shows:

• Time, Event and Source
• Value, Product and Campaign
• Visitor: the start of Kalman's random visitor id
• Meta: the delivery status, or "not mapped" if that event isn't sent to Meta

Use the Event name list to show one type of event, such as Purchase.

To check a new setup, do the step on your site, then open the log for the last few minutes. The Check it worked link on the install page opens it for the last 10 minutes. You can also add ?minutes=10 (any value from 1 to 1440) to the Event log address. A Last 10 minutes · show all chip shows the filter is on. Click it to clear the filter.

Consent signals don't appear in the log, because they aren't events.

Deliveries to Meta

The Deliveries to Meta tab shows the latest 50 deliveries, with Created, Kalman event, Sent as, Status, Attempts and HTTP for each. The statuses are:

• pending: waiting to be sent, for example while sending is paused
• sent: delivered
• failed: the platform refused it or couldn't be reached
• skipped: held back on purpose, for example because the visitor said no, the event is older than Meta's 7-day window, or a privacy check stopped it
• shadowed: stored instead of sent while the destination is in shadow mode

Click What we sent to see the exact body Kalman sent and Meta's response. Bodies are kept for 90 days. After that, the details window says the body was pruned.

Download a data-flow record

The data-flow record is a file you can keep as evidence of what Kalman did.

1. Open Integrations → Meta. Other connected ad channels have the same button.
2. Click Download data-flow record.

Only owners and admins can download it. By default it covers the last 30 days, as a CSV file. To choose the period, add from and to dates to the download link, for example ?from=2026-01-01&to=2026-03-31. The period can be at most 400 days. Add &format=json to get JSON instead.

The record contains:

• the fields the destination is allowed to send
• your event mappings and how values are set, with any clinical acknowledgements
• your consent mode and consent source
• delivery counts by event and status
• skip counts by reason
• the history of changes to the destination and your privacy settings

Each download is noted in the workspace's audit history.

What Kalman never sends

Kalman builds each delivery from a fixed allowlist: hashed identifiers, event name, time, value and currency. Names, intake answers, and condition, medication or product names never go to an ad platform. The data-flow record itself contains no hashes and no identifiers.