Match Quality Center and Identity Store
Designed to show which parameters each event actually carried, and to give guest checkouts a durable identifier.
updated
Coming to PixelCapi Pro Outline — facts still to be confirmedNot shipped yet. Match Quality Center is in development. This page describes what it is designed to do, in future tense, and will be rewritten as reference documentation when it ships. Release notes go out on the changelog.
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.
What it is designed to do
Show, per event type, which identifying parameters were present and which were missing — because a score on its own tells you there is a problem and a parameter list tells you where it is.
The Identity Store is designed to hold a durable identifier for buyers who are not logged in, so a guest checkout is not an anonymous event.
What already helps today
Correct per-platform normalisation and hashing, which is the thing that most often holds a score down without producing any error. See Match quality dropped.
Outline still to fill
TODO(owner: verify) — the screen, the parameter coverage view, how scores read from the platform are combined with the plugin’s own coverage data, and what the recommendations say. Also: how the Identity Store stamps its identifier onto an order at checkout so webhook-time sends can use it.
Was this page helpful?