Channel map used in the reports
Before a flagship attribution report is drafted, every paid and organic source you name is placed on this map. Rows that you do not run are struck. Rows you run without files stay in the unassigned notes rather than being filled from memory.
| Channel | What we ask you to send | How it appears in the report |
|---|---|---|
| Paid search | Campaign names, spend by week, conversion counts as your account defines them | Last-click table plus a dated spend series |
| Paid social | Flight dates, spend, and any view-through column the network provides | Main table uses clicks you can stand behind; view-through stays in an appendix |
| Display / other paid | Insertion orders or invoices, with placement names if they exist | A paid row that is not mixed into search |
| Organic search | Session or landing-page notes, branded vs non-branded if you already split them | Kept beside paid search, never absorbed into it |
| Organic social | Publishing calendar and any tagged landing pages | Dated against paid social bursts when the weeks overlap |
| Send dates, tagged click counts, and the live link format | Tagged activity only in the email row | |
| Referral | Partner list and any UTM you already use with them | Named partners; unnamed referrers stay grouped |
| Direct / untagged | The raw export; we do not ask you to relabel it in advance | Its own row, with a note when it moves with email or brand campaigns |
Why the map exists
Meetings collapse when one person says “digital” and another means paid search. The map forces a list. If a client markets a campaign whose name happens to mention Binance or a licensed character, we still treat it as a media row: dates, spend, organic aftermath. Compatibility of a label is not an endorsement, and it is not a financial product.
If you want the map applied to a quarter of your own activity, the flagship report is the engagement that does that work.
Local notes between cycles
Some clients date channel events on their own machines between monthly briefings. The Sourcepilotpath local utility is built for that record-keeping. Get it from Veve; this website does not serve an installer.