Pre-Launch Account Access and Tracking Audit (Onboarding)
A checklist with 7 steps: Collect admin-level access to every ad account the client owns before any campaign work begins.
By InnovaAI ResearchPublished
What are the steps?
Pre-Launch Account Access and Tracking Audit (Onboarding)
- 01
Collect admin-level access to every ad account the client owns before any campaign work begins
Request Business Manager or MCC admin rights, not analyst seats. Analyst-level access blocks pixel edits, audience uploads, and billing changes, which stalls launch by days.
- 02
Verify conversion tracking fires on the actual thank-you or checkout URL, not a staging page
Run a test conversion and confirm the event lands in the platform's events manager with the correct value parameter. A pixel that fires on the wrong page produces clean-looking reports and wrong optimization signals.
- 03
Map the client's product catalog or offer list to the campaign structure you intend to build
For ecommerce accounts, confirm the feed is connected and approved. For lead gen, confirm the form endpoint and CRM handoff. Catalog mismatches surface as disapproved ads 24 to 48 hours after launch.
- 04
Document the client's brand and legal constraints in a one-page creative brief
Capture prohibited claims, required disclaimers, approved color and logo usage, and any regulated-industry language. Automation tools such as Nanos or Ryze will generate copy that ignores these unless you feed them the constraints.
- 05
Set the account's baseline metrics snapshot before spend starts
Record current CPA, ROAS, and conversion volume from the trailing 30 days. Without a baseline, the first monthly report cannot separate your work from seasonality.
- 06
Confirm billing method, currency, and spend cap with the client in writing
A declined card on day three of a retainer burns the launch window and forces a re-approval cycle. Get the cap in writing so no single platform can overspend the monthly budget.
- 07
Assign named owners for creative approval, budget changes, and escalation
One client-side approver and one agency-side owner per function. Shared inboxes and group chats are where approval requests go to die.