Source Coverage and Freshness Check (QA)
A checklist with 6 steps: Map every data source the client contract names against what the platform actually ingests.
By InnovaAI ResearchPublished
What are the steps?
Source Coverage and Freshness Check (QA)
- 01
Map every data source the client contract names against what the platform actually ingests
List contracted channels (paid search, paid social, organic, email, CRM) beside the connector list. A 30-connector platform such as DashThis or a 200-source platform such as Klipfolio only helps where the specific source is live, not where the catalog is long.
- 02
Record the refresh interval per source and flag anything slower than the client's review cadence
Daily pulls are fine for a monthly retainer; a weekly client meeting fed by a 7-day-lagged ad connector produces decisions on stale spend.
- 03
Reconcile platform totals against the native interface for three high-spend accounts
Pull the same date range in Google Ads or Meta directly and compare. Note variance above 2% in the QA log with the likely cause (attribution window, currency, timezone).
- 04
Label every metric that consent banners, ad blockers, or AI referrals distort as directional
Session and conversion counts under GA4 undercount by design; present them as trend indicators rather than absolute totals so the client does not read a drop as agency underperformance.
- 05
Confirm white-label and access controls before the first client login
Check custom domain, logo, and permission tiers so a client cannot see another account's dashboard or an internal cost view.
- 06
Freeze the dashboard layout for the reporting period and log any mid-period change
Swapping a metric mid-month breaks comparison and invites the question of why the number moved.