Google has been moving offline conversion imports and enhanced conversions for leads uploads toward Data Manager API paths. WordPress lead pipelines that still rely on older Google Ads API upload paths need a token and access audit before failures show up in reporting.
Use this for agencies, CRM integrations, WordPress form pipelines, server-side tracking jobs, and teams that upload offline conversions or enhanced conversions for leads to Google Ads.
Quick answer
Google Ads Offline Conversion Import Token Allowlist Audit should be handled with a narrow evidence-first workflow: inventory uploaders, map tokens, run test upload, then verify the result before making broader changes.
What to check first
- List every job, plugin, CRM connector, server script, and vendor that uploads offline conversions to Google Ads.
- Record the developer token, OAuth client, manager account, conversion action, and API path used by each uploader.
- Check whether any uploader depends on a legacy path that may require allowlist access.
- Run a test upload with a safe test conversion and record accepted, partial failure, or blocked responses.
- Prepare a Data Manager API migration path with consent, field mapping, retry, and dedupe behavior documented.
Diagnostic table
Use this table to keep the work practical. It connects the symptom to evidence and a verification step.
| Action | Evidence to collect | How to verify |
|---|
| Inventory uploaders | List every job, plugin, CRM connector, server script, and vendor that uploads offline conversions to Google Ads. | Every uploader has an owner, token, API path, and conversion action documented. |
| Map tokens | Record the developer token, OAuth client, manager account, conversion action, and API path used by each uploader. | Blocked or partially failed uploads are visible in a daily report. |
| Run test upload | Check whether any uploader depends on a legacy path that may require allowlist access. | The migration path includes consent, normalization, retries, and dedupe. |
| Log blockers | Run a test upload with a safe test conversion and record accepted, partial failure, or blocked responses. | Marketing knows which conversion actions are safe, delayed, or at risk. |
Why this usually happens
- Lead upload jobs are often hidden in CRM middleware, WordPress plugins, or small server scripts.
- A token can be valid for one API path while a specific upload method is blocked.
- Reporting lag can make upload access failures look like attribution delay.
- Migration plans fail when they ignore consent and field normalization.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
upload_audit_row:
uploader: wordpress-crm-sync
developer_token: redacted
api_path: legacy_offline_import
conversion_action: qualified_lead
last_success: 2026-07-06
migration_owner: analytics
Safe fix order
Do the work in a sequence that makes each result easy to prove. Stop if a step produces new evidence that changes the incident scope.
- Inventory uploaders
- Map tokens
- Run test upload
- Log blockers
- Plan Data Manager path
What to tell the client or owner
Do not wait for a weekly reporting surprise. Tell the ad owner which upload path is still working and which needs migration.
Production verification checklist
- Every uploader has an owner, token, API path, and conversion action documented.
- Blocked or partially failed uploads are visible in a daily report.
- The migration path includes consent, normalization, retries, and dedupe.
- Marketing knows which conversion actions are safe, delayed, or at risk.
Mistakes to avoid
- Do not judge the fix by one browser or the homepage only.
- Do not delete evidence before recording usernames, file paths, timestamps, and response headers.
- Do not add a cache, security, or tracking plugin while the original problem is still unclear.
- Do not leave test users, temporary debug logs, or broad API keys active after verification.
When HandL WP should help
Bring in help when this affects leads, checkout, search visibility, malware risk, paid media reporting, or a client production site. HandL WP can trace the issue through WordPress, hosting, cache, tracking, and Search Console, then verify the workflow after the technical fix.
If this is active on a production site, audit Google Ads lead conversion uploads.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Helpful references