Skip to content

Browse the documentation

Dedup Doctor

The browser copy and the server copy of every event, side by side, compared by their actual event IDs.

updated

Outline — facts still to be confirmed

This article is a structured outline. Its headings and scope are settled; the specific values, screens and steps are marked TODO(owner: verify) until they have been checked against the plugin itself. Blueprint §7 is explicit that no article may state plugin behaviour that has not been verified.

Dedup Doctor lists both copies of each event and compares the actual event IDs, with the platform’s own trace ID beside each server send. A worked example of a healthy funnel is in Verify your first event.

What a row shows

  • Event name.
  • Event ID, on each side.
  • Send status.
  • The platform trace ID returned for the server send.

Reading the result

Matched means both halves reached the platform carrying one ID. A missing half tells you which side failed. Mismatched IDs mean deduplication is not happening at all — see Duplicate events.

Dedup Doctor also carries in-product copy explaining Meta’s Processed and Deduplicated labels, because that distinction is where most of the confusion lives.

Outline still to fill

TODO(owner: verify) — filters and time ranges available; how far back history is kept; what the screen shows for platforms other than Meta; whether rows can be exported.

Was this page helpful?