A difference between two dashboards is a question. It becomes an investigable obligation only when the scope, definition, timing and source coverage support that conclusion.
Two totals can be correct about different things
An advertising platform may report an attributed conversion. A tracker may report a received postback. An operator backend may report a qualified first-time deposit. Finance may report a payment for the previous settlement period. These numbers can differ without any single system being broken.
Start by naming the event that each total represents. Does a conversion mean a registration, a successful deposit, a qualified acquisition or a partner confirmation? Which source owns that definition? A percentage difference is not useful until both sides describe a comparable population.
Establish the relationship before the ratio
A comparison needs a tenant, an operator, a partner relationship, a currency and a declared period. A campaign name alone cannot provide those boundaries. Similar names, timestamps or amounts can suggest where to investigate, but they do not establish that two observations refer to the same subject.
In Spend Sentinel R2, exact correlation uses the configured relationship and observed subject identity. Partner confirmation also requires an explicit reference to its originating acquisition event. If that link is absent, the event stays unlinked. Assigning it to the most plausible campaign would make the report look more complete while weakening the evidence.
Separate business time from observation time
Occurrence time describes when a source says an event happened. Receipt time describes when the event became available to the comparison. An economic period describes where a revenue or payment amount belongs. These are different questions.
A late callback can be absent in an earlier snapshot and present in a later one. A late payment can belong to an earlier commercial period. Replaying the earlier investigation should not silently import information that arrived afterwards. Preserve the observation cutoff alongside the result, including its timezone.
Absence needs coverage
A query returning no matching callback does not prove the partner never received it. The export might be partial, the endpoint might lag or the observation deadline might still be open. A count of zero is a measured value; a missing dataset is unavailable evidence.
The configured deadline and a source completeness declaration determine when a missing observation becomes investigable. R2 keeps the comparison pending when the necessary coverage is absent. A source declaration itself is not independent attestation: retain who or what supplied it and the evidence reference behind it.
A practical review sequence
This order helps avoid a familiar failure: attaching money to a discrepancy before establishing what the discrepancy means. The synthetic callback-gap investigation demonstrates that sequence using a versioned agreement and downloadable evidence. It is product proof, not a claim about customer results.
- Name the two event definitions and the source responsible for each.
- Fix the relationship, currency and economic period.
- Inspect exact identities and explicit parent references.
- Choose a timezone-aware observation cutoff.
- Check whether source coverage reaches the relevant deadline.
- Only then apply the approved commercial rule and document what remains unknown.
Inspect the implementation
These notes describe the R2 model and its current boundaries. They do not certify a provider connection.
Spend Sentinel event and comparison contract ↗Inspect the generated callback-gap evidence ↗