Build an Evidence Receipt for Intent Data Measurement Vendors

November 19, 2026•11 min read

An intent data measurement receipt is a short record attached to a report. It says who produced the figures, which event definitions and dates apply, which cases were excluded, and how totals can be reconciled. Ask for the receipt when contracting and again at delivery. A buyer who spots a disagreement between CRM and media reports needs a path to investigate it.

Start with the buyer decision

Imagine a wholesaler receives a report claiming a large number of influenced accounts. The CRM manager has a smaller count because the media report includes households and the CRM uses purchasing organizations. Neither number establishes who bought. A receipt showing the unit, match scope, exposure rule and outcome source lets both teams explain why the counts differ and choose the one that fits the decision.

The receipt complements the agreement. Include named owners for measurement, incident escalation, data revisions and authorized output release. Ask whether exclusions are available as aggregate counts and under what timing. A trustworthy reporting handoff can show how a total was built without handing every row of client data to each participant.

What the current guidance changes

IAB finalized the Measurement Services Addendum v1.0 on October 28, 2026. Buyers can use the development as a prompt to review contractual ownership and measurement responsibilities before asking vendors to reconcile reports. See the IAB Measurement Services Addendum v1.0.

A fictional buyer walkthrough

A weekly media report claims 290 influenced units and the CRM lists 88 eligible accounts. The receipt should identify whether the media units were devices, households or organizations. It should also explain which match and time rules connect those metrics if the team intends to reconcile them.

Request the same sample report again after a late batch arrives. If the total changes, the revision policy should let the reviewer identify the snapshot and explanation without replacing the original record silently.

Scope statement

Name each reporting unit and the purpose for which it is used. Distinguish unique exposures, eligible matches, and verified CRM outcomes.

Build the escalation around the consequence of a failed the scope statement check check. A failed the scope statement check calls for a record of the first stage that diverged from expectation. Inspect the upstream event and the immediate downstream effect. If the upstream state cannot be verified, the failure may be a traceability problem as well as a processing problem. To close the review, write down what the decision owner is expected to do. Keep the unit beside the reported count so an account and a device cannot be conflated.

Set an owner for the exceptions before turning on broader routing.

The best evidence for the scope statement check is the one an authorized second person can check. Use an approved source rather than a copied conclusion, record the relevant version, and retain the date. This is especially important if a later report uses receipt completeness to support a change in time or spending.

Make the denominator a contractable reporting detail

A measurement service can count a matched event, a unique delivery unit, an attributed outcome or an audited sales stage. Ask which exclusions define each number. Some totals may exclude events that arrived late, duplicate rows or matches outside an allowed purpose. Some stages might be withheld for privacy reasons. A report should name those possibilities and explain how the vendor can communicate their effect safely. This gives the buyer a way to distinguish a normal scope difference from an unexpected drop in source quality.

Exclusion ledger

Have the provider distinguish late, invalid, suppressed and unavailable rows when it can report those totals safely. These states have different operational meanings. Apply the rule while the source evidence is still available. Agree on allowable aggregate outputs with privacy and measurement owners.

Treat the exclusion ledger check as a release check when the team can identify an expected state in advance. A tester should document differences between a warning, an expected missing result and a real violation. Those classes may look identical if they are collapsed into a null or zero. Retain just enough approved metadata to compare states without exposing detail that the quality check does not need. Capture the business reason, the first affected record or reporting date, and the person who approved the change.

Test the boundary of the exclusion ledger check using a case that almost meets the documented condition. Record the exact reason it falls outside. If two reviewers give different answers, inspect the underlying definition before you widen the rule. The disagreement may show an ambiguous requirement or a field that should be confirmed at intake.

Revision policy

Treat the revision policy check as a diagnostic with its own denominator. Late events or CRM merges can change a historical number. Preserve the original snapshot and mark why a revised version differs.

Put the next step in the operating notes. Require an effective date and a policy for updating executive summaries already circulated. Keep the evidence from the revision policy check with the system owner. If two sources appear to disagree, compare the units and processing times before changing any rule. A known control record can make the issue easier to reproduce and protect the production data from exploratory edits. Decide that severity before looking at the case totals so difficult failures receive consistent attention.

Turn the revision policy check into a short review record with the observed evidence, the proposed action and its owner. The next operator should be able to continue the work without being asked to infer missing details. If a check is unresolved, note which subsequent action must wait and what evidence can release it.

Escalation path

Assign owner roles for event definitions, privacy decisions, integration incidents and contested outcomes. Ask who can approve a corrected export.

Run an adverse example through the escalation path check. A failed the escalation path check calls for a record of the first stage that diverged from expectation. Inspect the upstream event and the immediate downstream effect. If the upstream state cannot be verified, the failure may be a traceability problem as well as a processing problem. The review record for the escalation path check should retain this disposition. Test the path with a sample mismatch before paying for a production reporting cycle.

Record the decision at the grain the business uses to act.

Test a disagreement before it becomes a budget dispute

Ask an authorized reviewer to pick a line item and reproduce its count from the approved evidence. If the systems use different time zones or different observation periods, align them before looking for record-level explanations. If the units differ, change the comparison question or request an allowed mapping. When the vendor revises an earlier report, confirm the correction path, affected dates and who receives the updated version. Preserve which number the team relied on for any spending decision already taken.

Audit boundaries

Ask which evidence an authorized reviewer can inspect. A report can be reproducible from approved aggregates even if raw client data stays restricted. For this case, the expected next step is clear. Document any stage that cannot be audited and limit the claims built on it.

Treat the audit boundaries check as a release check when the team can identify an expected state in advance. A tester should document differences between a warning, an expected missing result and a real violation. Those classes may look identical if they are collapsed into a null or zero. Otherwise a technically successful change may look like a surprising shift in buyer activity when the underlying business remained stable. Choose the source that verifies each one and write down who can look at it.

In the worksheet, attach the expected result of the audit boundaries check to a dated record. Ask the reviewer to point to the evidence that supports it. For a case that cannot be resolved, record what is missing and leave the substantive decision open until the right owner can respond.

Build the review worksheet

An evidence receipt can include report ID, measurement purpose, event definitions, study interval, aggregation unit, approved exclusions, late data policy and contact for reconciliation. Ask the vendor for one sample receipt that references a plausible discrepancy. The account team should be able to interpret the report without guessing how it handles missing records.

A measurement buyer can reconcile its own count of accepted opportunities against an approved aggregate. If the vendor uses view-through exposure for another metric, preserve the time window and unit beside that number. The two reports can be internally correct and still disagree because they answer different questions.

A worksheet for receipt completeness

In the fictional worksheet below, the denominator consists of report line items with a contractual reporting definition. The numerator counts cases that had a reconciled receipt and named owner. Both figures belong in the report. A reader who has only a percentage cannot tell whether a handful of outcomes drove the apparent difference.

Divide 34 by 43 and multiply by 100 for the first rate. For the second rate, use 25 divided by 43. Subtract the unrounded percentages to find that the first is 20.93 percentage points above the second. A relative comparison divides that difference by the second rate, so the first is about 36.0 percent higher on that basis.

The comparison measures whether reports can be investigated. It cannot establish the accuracy of a vendor's outcome claim unless the underlying evidence can also be verified.

Record the snapshot date beside the receipt completeness result. For this hypothetical comparison, use the same written review standard for both groups. If a reviewer changes the comparison rule, keep the original receipt completeness calculation and clearly identify the revised version.

Reconcile the count used for receipt completeness to a frozen sample or a permitted source extract. Keep intentional exclusions and unavailable observations in separate rows of the audit. If the reader cannot inspect the reason the denominator changed, hold the comparison until the data owner can explain the movement.

Put disputed figures into a reconciliation sheet

Give each number its own line, with unit, source, intended use, time range and the reviewer who can verify it. If the vendor uses a different unit, request the permitted bridge or state the limit. Record the common ground before debating which total should go in an executive report. A usable receipt makes it possible to defend why the report uses a specific measure for budget planning without treating other measures as inherently wrong.

On the fictional receipt completeness worksheet, one additional qualifying case in the first group would move its rate by 2.33 percentage points if the denominator stayed at 43. The second group changes by 2.33 points for one case on its own fixed denominator. This is a sensitivity illustration, not an uncertainty interval. A real review should show how many cases were unresolved and whether a reasonable interpretation of those cases would change the decision.

Give the person investigating receipt completeness a test identifier, the expected result, and a permitted way to see the difference between the two states. A root cause might sit in the source, the integration, the comparison rule, or the report. Record the earliest confirmed divergence and retest from there after correction.

Specify which evidence the provider can show

A vendor can offer a customer-specific model without sharing the licensed source records behind every event. Ask for enough approved provenance to evaluate its use. An evidence receipt can describe the input family, observation time and match scope without asserting that each underlying contact is exclusive to the client.

For more on the signals behind this decision, read the Cortex intent data insights.

Before the data quality reviewer closes the review, ask them to write a one-sentence conclusion about receipt completeness that includes the action and the main limitation. Then ask a colleague to explain it back. If they hear a claim about revenue, purchase readiness or causation that the measurement did not test, revise the language before it appears in a client report.

Make the diagnostic repeatable

Require a reproducible receipt for any metric used to make a spending or vendor decision. Take a vendor figure that cannot be reconciled to your CRM and ask which definition, scope or timing rule explains it. If both reports are valid at different grains, the receipt should help leadership choose the right one for the next decision.

Visit Cortex Marketing AI for an overview of how website activity and sales feedback inform buyer prioritization.

Bring a sample reconciliation, an approved test case, and the expected output. To put the decision into practice, call Cortex Marketing AI to arrange a consultation.

Back to Blog