Events not showing up in Meta Events Manager
The connection looks configured, the setup finished without an error, and Events Manager shows nothing. Work through these in order. The first two account for most cases.
Is a source connected in the same project?
Section titled “Is a source connected in the same project?”A destination on its own sends nothing. Events reach Meta through a source, so a connected Meta destination with no source feeding it is doing exactly what it was asked to do. Open the project and check a source instance exists and is sending.
Is the tag published?
Section titled “Is the tag published?”On a web or e-commerce source, the tag has to be live on the site. In a tag manager that means the container has been published, not just saved. A saved-but-unpublished container is the most common version of this.
Are you looking at the right dataset?
Section titled “Are you looking at the right dataset?”Events are written to the dataset chosen during authentication. If your business has several, confirm the one open in Events Manager is the one the connection is writing to, and that it is the dataset registered against the right property. A website dataset and an app dataset are not interchangeable.
Is the time window hiding them?
Section titled “Is the time window hiding them?”Events Manager defaults to a recent window and applies whatever filters were last used. Widen the date range and clear the filters before concluding nothing arrived. Server events can also take a few minutes to appear, so a check made seconds after a test is too early.
Are they arriving and being deduplicated?
Section titled “Are they arriving and being deduplicated?”If the delivery method shows Browser and server, your server events are arriving and being deduplicated against the browser events correctly. That is the intended behavior rather than a fault, and the total you see is the deduplicated one.
Send a test event
Section titled “Send a test event”Use the test event code in Events Manager and send one event through. A test event that appears proves the path works and moves the question to what your real events are carrying. A test event that does not appear points back at the credentials or the dataset.
If delivery stopped rather than never started
Section titled “If delivery stopped rather than never started”Where events were arriving and then stopped, the access token has probably expired or been revoked. Tokens are also tied to the person who created them, so a colleague losing access or leaving has the same effect. Generate a new token in Events Manager and re-validate the connection.
Still stuck
Section titled “Still stuck”Contact support with the project, the destination, the dataset ID and roughly when events were last seen. Where the source is a file, include the file name so the specific delivery can be traced.