A PPC tracking handoff should document what counts as a conversion, where the event is collected, how it reaches the ad platform, whether it influences bidding, how duplicates are prevented, and who owns the implementation.
Campaign optimization depends on measurement. If the incoming media team inherits unclear or duplicated conversion actions, automated bidding and reporting can optimize against the wrong signal.
AxiomLift’s white label PPC management page covers the delivery service. Use this checklist before an account transfer, redesign, tracking rebuild, or new partner onboarding.
1. Create a conversion dictionary
List every conversion event in plain business language.
For each event, record:
- event name
- business meaning
- URL/form/action involved
- platform source
- Google Ads conversion action name
- primary or secondary status
- counting rule where relevant
- value method if used
- owner
- current test status
Examples might include completed purchases, qualified lead forms, booked appointments, or phone-call events—but use only events meaningful to the client’s business.
2. Verify primary versus secondary conversion actions
Google Ads distinguishes conversion actions used as primary goals from secondary actions used mainly for observation. Primary conversion settings can affect the “Conversions” column and automated bidding depending on goal configuration.
The handoff should explicitly mark which signals the account is intended to optimize toward.
Ask:
- Is this a real business outcome or a micro action?
- Should Smart Bidding optimize toward it?
- Is the action duplicated elsewhere?
- Did its purpose change over time?
Do not let an old “thank-you page view” remain primary simply because nobody reviewed the settings.
3. Map every data path
A conversion may reach Google Ads through different routes.
Examples:
- Google tag directly on the site
- Google Tag Manager
- GA4 import
- ecommerce integration
- CRM/offline conversion import
- call tracking
- third-party booking platform
Draw the path for each important event.
For example:
Form submit → data layer → GTM → Google Ads conversion action
or
Purchase → GA4 ecommerce event → imported Google Ads conversion
This helps identify duplicates and ownership gaps.
4. Check for duplicate measurement
Google’s setup guidance warns about duplicate tagging/reporting when the same conversion is configured through multiple paths.
Common situations to review:
- direct Google Ads tag plus GA4 import for the same event
- hard-coded tag plus GTM tag
- multiple GTM containers
- thank-you page view plus form event both treated as the same lead
- CRM import plus browser conversion without deduplication strategy
Do not delete anything immediately. First confirm which path is intended, which is reliable, and how historical reporting will be affected.
5. Test the actual user journey
Do not validate tracking only by seeing that a tag exists.
Run the real path:
- arrive on the landing page
- complete the intended action
- verify the website success state
- inspect tag/debug output
- confirm the analytics/ad-platform event path
- verify no duplicate firing
- record the test date and result
Repeat for desktop/mobile or different forms when implementation differs.
6. Document consent and privacy dependencies
Tracking behavior may vary based on consent settings, region, browser, or privacy implementation.
Record:
- consent platform in use
- who owns its configuration
- whether tags depend on consent state
- known modeling or data limitations
- legal/compliance owner
The media team should not change consent settings as an “optimization” task without the appropriate owner.
7. Review GA4 imports carefully
If Google Ads imports events from GA4, document:
- GA4 property
- event name
- key event status where relevant
- import mapping
- filtering conditions
- whether the same action is measured directly in Google Ads
Do not assume matching event names mean the data is identical.
8. Document offline conversion and CRM flows
For lead-generation accounts, the valuable outcome may occur after the web form.
If offline imports are used, record:
- CRM/platform owner
- identifier captured
- lead-stage definition
- import schedule
- value mapping if used
- deduplication method
- failure monitoring
- privacy/security requirements
An incoming PPC partner should understand which stages are trustworthy before using them for optimization.
9. Preserve a pre-handoff baseline
Before changing tracking, export or record:
- current conversion action list
- primary/secondary status
- goal configuration
- recent conversion volumes
- known discrepancies
- tag/container versions where possible
When the new setup goes live, annotate the date. Otherwise reporting may show a sudden change that looks like campaign performance when it is actually measurement.
10. Assign owners
Every tracking component should have an owner:
| Component | Owner to define |
|---|---|
| Business conversion definition | Client/agency strategy |
| Google Ads goal setup | PPC owner |
| GTM implementation | Analytics/dev owner |
| Website form event | Development owner |
| GA4 configuration | Analytics owner |
| CRM/offline import | CRM/data owner |
| Consent configuration | Legal/privacy + technical owner |
The PPC manager should not be expected to silently own every system in this chain.
Once tracking ownership is documented, use the white label PPC reporting guide to make sure changes in measurement are explained clearly instead of being mistaken for changes in campaign performance.
Handoff checklist
- Conversion dictionary complete.
- Primary/secondary actions reviewed.
- Data path documented for priority events.
- Duplicate paths checked.
- Real user journeys tested.
- Consent dependencies documented.
- GA4 imports reconciled.
- Offline/CRM flows documented if used.
- Baseline saved before changes.
- Implementation owners named.
- Tracking-change date will be noted in reporting.
Use this together with the broader PPC account takeover checklist so measurement, ownership, campaigns, budgets, and creative are transferred as one system.