This map is part of the advertising delivery reconciliation hub. The worked exception follows one case through its decisions; this page shows the plumbing underneath: which system holds which record and how they connect.
System, record, linking key and owner
| System | Record it holds | Linking key | Usual owner |
|---|---|---|---|
| Order management system | Signed insertion order, placement list, run dates, rate | Order ID and line reference | Sales operations |
| Ad server | Line items, targeting, delivery reports, remedy lines | Line item ID, carrying the order ID; placement or ad unit ID | Ad operations |
| Verification and third-party reports | Independent counts and the removals they justify | Campaign or line name, date range and time zone | Ad operations |
| Finance adjustment log | Corrected totals, each removal with a reason, the settled figure | Line item ID or order ID plus reason code | Billing or revenue accounting |
| Billing system | Invoice lines, credit memos | Invoice line referencing order ID | Finance |
| Account managers' mailboxes | Agency acceptance of a makegood or credit | Order number in the subject or body, if anyone typed it | Commercial team |
Read the table as a chain from top to bottom. The strong keys (order ID, line item ID) are system-generated. The weak ones (names, email subjects) depend on habit.
One fully joined case
Illustrative and fictional. A 340-person business-to-business trade media company runs a sponsorship campaign for an industrial equipment maker. Here is the chain as it would look if every key held:
| Hop | From | To | Key that joins them | Status |
|---|---|---|---|---|
| 1 | Insertion order IO-2219 | Ad server order | Order number pushed by integration | Joined |
| 2 | Ad server order | Line item for newsletter placements | Order ID on the line item | Joined |
| 3 | Line item | Placement list in the signed order | Ad unit ID, unchanged since signing | Joined |
| 4 | Line item delivery | Verification report | Same date range, time zone and line name recorded in the discrepancy log | Joined |
| 5 | Delivery | Adjustment log row | Line item ID plus reason "off-contract placement" | Joined |
| 6 | Shortfall | Makegood line item | Original line ID in the makegood's notes field | Weak: typed by hand |
| 7 | Makegood | Agency acceptance email | IO-2219 in the email subject | Weak: depends on habit |
| 8 | Order | Invoice line | Order ID on the invoice | Joined |
Six strong joins and two weak ones. That is a realistic, useful result: the weak hops are exactly where SourceX's review would test coverage, and where the company's administrators should check how many years follow the same pattern.
Each hop, and where it breaks
Follow IO-2219 through the systems again, this time asking what would have broken the chain at each hop.
Hop 1, insertion order to ad server order. At the trade media company an integration pushes the IO number into the ad server, so the join holds. Many sales teams instead retype it into a free-text name. Inside the ad server itself the link is solid: in Google Ad Manager's API every line item has a required orderId field naming its parent order. The fragile part is the step before, between the sales system's numbering and the ad server's.
Hops 2 and 3, line item to the newsletter placements that were sold. The ad server records where the sponsorship actually ran; the signed order records where it was allowed to run. The ad unit ID ties the two together, which works only while the unit keeps its ID. If the newsletter section was renamed or split after signing, someone needs a mapping from old unit to new.
Hop 4, delivery to the equipment maker's own counts. The two never agree to the impression. Google's help on investigating discrepancies asks for the same date range, time zone and line items on both sides, and for discrepancy tolerances agreed with the buyer upfront. A discrepancy log that wrote those settings down is what lets someone redo the comparison.
Hop 5, delivery to the adjustment row. The finance row keys the removal to the line item ID and the reason "off-contract placement". Ask also which count the row started from: Google's Open Bidding help prefers Billed impressions for reconciliation because the billing ping fires before invalid-traffic and discrepancy deductions.
Hop 6, shortfall to the makegood line. Here the trade media company is weak: the original line ID sits in a notes field someone typed. A formal Ad Manager makegood would hold it as data, since the makegood proposal line item stores the original line item's ID and a reason such as underdelivery, but formal makegoods exist for Programmatic Guaranteed deals, keep the original CPM and quantity limits, and need the buyer's acceptance. Direct-sold sponsorships rarely use them.
Hops 7 and 8, acceptance and invoice. The invoice line carries the order ID, so finance closes cleanly. The agency's acceptance is found only because an account manager habitually put IO-2219 in the subject line. Without that email the makegood reads as unexplained free inventory.
Coverage questions for the ad operations director
Ask about keys and years, never contents:
- For how many years of closed campaigns do order IDs appear on ad server line items?
- Were placements renamed during that period, and was a mapping kept?
- Does the adjustment log key each removal to a line item and a reason?
- How were makegoods booked, and do they reference the original line?
- Which mailboxes hold agency acceptances, and what happens to them when staff leave?
- Can the current ad server still export closed line items with their IDs intact? Export capability varies by system and contract, so the company confirms this with its administrators.
How diligence teams test revenue adjustments, which uses the same joins, is covered in MCP for quality of earnings and MCP for general ledger reconciliation. The wider data category is described on the reconciliation exceptions data page.
What the map tells a partner about fit
Records: closed campaigns where at least the order-to-line-item and line-item-to-invoice joins hold. Ownership: the publisher's own operating records, subject to rights review of advertiser terms. Authority: a named executive, usually not the ad operations director. The company baseline: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Unknown until SourceX reviews it: buyer interest, the rights result, de-identification and any offer. To hand the answers to a decision-maker, use the referral brief template.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If the director confirms that most hops join for several years of closed campaigns, register as a partner, check the company against who qualifies and read the program terms before introducing the executive who can approve.