Event logs
Every event PixelFlow sends, in real time, with the full payload
Free trial. No card, no tag manager.
Watch events arrive as they happen
Click a button on your site and see the event appear in the log a moment later. Each row shows the timestamp, the event name, where it came from and whether Meta accepted it.
Live events
Purchase
{…}
12:04:11
Lead
{…}
12:03:58
PageView
{…}
12:03:41
See what data was added
Open any event to see the full "payload" - ie. exactly what user data was tracked and sent along with the event
Delivery status
Every event shows whether it was processed, deduplicated or rejected, with Meta’s response when there is one.
Filter and export
Filter by event, source, pixel or time, then export the rows you need for a client or a support ticket.
yoursite.com · one script
Browser pixel
fbq() in the page
Conversions API
PixelFlow server
Meta · 1 Purchase, same event_id
Understand why your Event Match Quality is low
Match quality depends on the identifiers sent with each event. The log shows which ones were present on every event, so you can see at a glance whether email, phone, click ID or browser ID were missing and fix the setup.
Browser and server events side by side
Every conversion shows up twice, once from the browser pixel and once from the Conversions API, with the shared event ID that lets Meta count it once. If one side is missing you will see it here first.
Lead
Processed
Browser
Lead
Processed
Browser
Lead
Deduplicated
Server
Purchase
Processed
Browser
Purchase
Processed
Browser
Purchase
Deduplicated
Server
Purchase · blocking rules
3 active
Block if already fired this session
Block without a Facebook click ID
Block repeats within 30 minutes
Block if same referrer
See what was stopped, and why
Events blocked by a blocking rule or filtered as bot traffic are logged with the reason, so a missing conversion is never a mystery.
Every payload, exactly as it was sent
Open any event in the log and you see the full payload PixelFlow tracked and sent to Meta: the event name, event ID, time and page URL, the customer identifiers Meta matches on, the custom data such as value, currency and content IDs, and the UTM parameters the visitor arrived with.
Browser and server payloads sit side by side, so you can check the same event ID went out on both, see what Meta accepted, and copy the JSON when support or a developer asks what was tracked.
Event data
event_name, event_id, event_time, action_source and the page URL it fired on.
Customer data
Email, phone, IP, user agent, fbp and fbc. Personal fields are hashed the way Meta requires.
Custom data
value, currency, content_ids and any parameters you added to the event.
Attribution
utm_source, medium, campaign, term, content and utm_id captured on the visit.
Payloads are kept for 30 days, then deleted.
FAQ
Everything you need to know about the event log.
How long are events kept in the log?
Events are retained in your account so you can look back at past days and weeks. Older events roll off according to your plan’s retention.
Does the log show Stripe and Calendly events?
Yes. Server-side integration events appear in the same log, marked with their source.
Can I see the exact data sent to Meta?
Yes. Each event opens into the full JSON payload PixelFlow sent, including the hashed identifiers.
What does Deduplicated mean?
The browser pixel and the server event carried the same event ID, so Meta kept one and discarded the other. That is the intended outcome, not an error.
Can I use the log to test a new setup?
Yes. Trigger the event on your site and watch it arrive. For Meta’s side, use the Test Events tool in Events Manager alongside it.
Is there a limit on logged events?
No. PixelFlow does not cap events on any plan.
Smarter, server-side tracking
Start sending accurate conversions today - no tag manager, no code, no developer required.
Compatible with
