Every paid media team has reporting. Very few have a reporting stack.
The difference shows up on Monday morning. Reporting is a pile of platform exports and a dashboard someone built two years ago. A stack is a system with layers, where each layer feeds the next, and the top layer is a short report a decision maker actually reads.
Here are the five layers, in order, plus where AI fits.
Layer 1: Raw platform data
Google, Meta, and TikTok each keep score their own way.
Each platform defines a conversion differently. Each uses its own attribution window, its own view of when a conversion happened, and its own idea of what counts as engagement. Meta may credit a purchase to an ad someone saw a week ago. Google may credit the same purchase to a search click.
This is not a flaw you can fix. It is the nature of the raw layer. The mistake is treating any single platform's numbers as the truth instead of as one witness's testimony.
What good looks like at this layer:
- Conversion events are defined once, in writing, and mapped to what each platform calls them.
- Attribution settings are documented, not left on defaults nobody remembers choosing.
- Exports are scheduled, not pulled by hand when someone asks.
If a person spends part of every Monday downloading CSVs, the stack is broken at layer one.
Layer 2: Blending
Blending pulls platform data into one place so you can see spend and results side by side.
The tool matters less than people think. A connector into a spreadsheet, a reporting tool with native data sources, or a proper warehouse can all work. Small accounts do not need a warehouse. Large multi-platform accounts eventually do.
What breaks blending is never the pipe. It is the definitions.
"Conversions" from Google and "results" from Meta are not the same thing, and adding them together produces a number that means nothing. Before you blend, write a metric dictionary: what each metric means, which platform field feeds it, and which numbers are never allowed to be summed across platforms.
One more quiet failure: dates. Platforms report in different time zones, and a blend that ignores this will show small daily mismatches forever. Pick one time zone for reporting and convert everything to it.
Layer 3: The naming dependency
This is the layer nobody budgets for, and it decides whether the rest of the stack works.
Blended data is only useful when you can slice it. Brand versus non-brand. Prospecting versus retargeting. Product line, region, offer. The platforms do not give you those slices. Your campaign names do.
When names are consistent, a report can split performance by any dimension carried in the name, automatically. When names are improvised, someone has to maintain a manual mapping table, and the mapping table is always out of date.
A workable convention has a few traits:
- Every campaign name carries the same fields in the same order, separated by the same character.
- The allowed values for each field come from a fixed list, not free text.
- The convention is written down where the people launching campaigns will see it.
Naming conventions feel like housekeeping. They are actually the join keys of your entire reporting system. This is a large part of why we treat account structure as a build project, not a cleanup chore. Our approach lives on the paid ads systems page.
Layer 4: Visualization
Now, and only now, dashboards.
Most dashboards fail because they were built before the layers underneath were solid. They visualize inconsistent data with improvised names, so every chart carries an asterisk and every review meeting starts with an argument about whose number is right.
The other failure is scope. A dashboard with forty charts answers no question. Build views around the questions people actually ask:
- Are we pacing to budget this month?
- Which campaigns earned more budget, and which should lose it?
- What did the last change we made actually do?
Three focused pages beat one sprawling one. And a dashboard is still not a report. It is a place to look things up. Nobody opens it unprompted, and the numbers do not explain themselves.
Layer 5: The narrative summary
The top of the stack is a short written summary. What changed, why it changed, what we are doing about it, and what we need from you. A few paragraphs. Weekly.
This is the only layer most stakeholders will ever touch. It is also the layer most teams skip, because by the time someone has fought through exports, blending, and a broken dashboard, there is no time left to write.
That ordering is backwards. The narrative is the product. Everything below it exists so this page can be written quickly and trusted completely. A weekly documented cadence like this is the backbone of how we manage paid media.
Where AI fits
AI belongs in one specific slot: drafting the narrative from the blended data.
Given clean, blended, well-named data, a model can produce a solid first draft of the weekly summary. What moved, by how much, against which targets. A senior marketer then edits it, adds judgment, and owns the result. The draft takes minutes, and the summary ships every week instead of whenever someone finds time.
Notice the dependency. AI drafting works because layers one through three are clean. Point a model at raw exports with improvised campaign names and it will summarize noise, confidently. The value is in the stack, not the model.
This is the pattern behind our reporting builds: reporting that writes itself, reviewed by a human who signs their name to it. More on that at analytics and reporting.
Build order matters
If you are starting from a pile of exports, resist the urge to buy a dashboard tool first. Build in this order:
- Document conversion definitions and attribution settings for each platform.
- Fix campaign naming, and backfill a mapping for historical campaigns.
- Blend into one source with a written metric dictionary.
- Build a small number of views around real questions.
- Ship the weekly narrative, drafted by AI, edited by a person.
Each step makes the next one cheaper. Skipping a step makes every later step more expensive.
Find out where your stack breaks
We have built and run this stack across $100M+ in managed spend, and the failure point is almost never where teams expect. It is usually layer two or three, quietly poisoning everything above it.
Our paid media audit traces the whole chain, from platform settings to the report your leadership reads, and hands you a dollar-weighted plan you keep whether or not we do the work. If the account is fine and the reporting is the problem, we will say exactly that.