Paid Account Access and Pixel Verification (Onboarding)

Paid Account Access and Pixel Verification (Onboarding)

1. 01

   Collect admin-level access to every ad account, business manager, and pixel before kickoff

   Request partner access rather than shared logins so the client retains ownership and your team can be removed cleanly at offboarding. Confirm the person granting access has authority to do so in writing.

2. 02

   Map each pixel, conversion event, and catalog to the specific campaign objective it serves

   A single client often runs three or four pixels across legacy builds. Tag every event with the objective it supports so reporting does not double-count conversions later.

3. 03

   Verify event firing with a live test purchase or form submission on both mobile and desktop

   Platform diagnostics frequently show green while a checkout event fires only on desktop. Run one real transaction end to end and screenshot the event manager result.

4. 04

   Confirm domain verification, Aggregated Event Measurement priority, and any consent-mode settings

   Unverified domains cap event tracking to eight conversions and break retargeting pools. Document the current priority order before you change anything.

5. 05

   Inventory existing audiences, saved reports, and any third-party measurement tags

   Note which audiences were built from first-party lists versus pixel behavior, since list-based audiences decay fast and often inflate early performance reads.

6. 06

   Record the baseline 30-day spend, CPM, and conversion volume per platform in a shared sheet

   This baseline becomes the only honest comparison point for your first 60 days. Without it, every later performance claim is unfalsifiable.

7. 07

   Log every access grant, pixel ID, and event name in the client's account record

   Agencies lose accounts at handoff because nobody can reconstruct which pixel belonged to which campaign. One page, updated at onboarding, prevents that.