An agency reporting stack needs source accounts, a reporting layer and a record of the report delivered to the client. Those layers answer different questions. The source platform owns its underlying observations; the reporting layer interprets them; a delivered snapshot records what the client received.
This guide maps components and ownership. It does not install tracking on a client site, interpret privacy law or calculate an agency software budget.
Minimum reporting components
| Layer | Record owner | Interface to inspect |
|---|---|---|
| Source account | Client or authorized platform owner | Account identity and approved access |
| Connection | Agency reporting administrator | Credentials, source selection and refresh responsibility |
| Report | Report owner | Metric definitions, filters and date range |
| Delivered snapshot | Client-service owner | Version and delivery context |
Preserve the client and source-account identifiers. A report labeled with the right client name can still point to the wrong property or advertising account.
Marketing-reporting and general BI routes
Swydo documents managing client data sources, including reusing connections across reports and replacing a source. It is a candidate reporting layer for supported marketing sources. Ask which reports change when a source is replaced and who authorizes that change.
Power BI documents data refresh and its relationship to reports and models. It is a candidate general reporting layer where the agency needs a broader model. Confirm the proposed connector and operating owner; this guide does not implement a warehouse or refresh pipeline.
Neither source establishes that two products interpret a metric identically. The report owner must define the period, filters and meaning. We have not measured connector reliability or reporting accuracy.
Evaluate a source-account replacement
Use fictional clients and synthetic reports. Replace one connection and ask the report owner to identify every affected report. Then compare the current report with a previously delivered snapshot. The snapshot should remain understandable even if the live source changes.
Include an expired connection authorization. Show who receives the exception and what the client-facing report displays before recovery. An old value presented without freshness context can be mistaken for a current result.
Finally, change a report filter. Ask which client-service participant approves the revised definition and whether the next delivered version carries that context.
Keep technical implementation separate
A reporting stack may require engineering, but the operating brief should first specify source authority, metric ownership and delivery records. Add specialist data components only for a named requirement that the existing reporting route cannot meet.
The agency operating map covers commercial and delivery systems. Systems-of-record ownership explains why a report is not another editable operational authority. Browse the Agency Operations hub for related component choices.