Google's Data Manager API field mapping docs show that teams moving from older Google Ads API upload paths need to remap jobs, operations, destinations, user data, and custom variables. For WordPress lead sites, the practical risk is losing the lead ID, consent state, or conversion action between the form and the upload.
Use this when WordPress forms, CRM stages, or offline lead uploads are being moved to the Data Manager API or audited after poor Google Ads matching.
Quick answer
Google Ads Data Manager API Field Mapping for WordPress Leads should be handled with a narrow evidence-first workflow: map fields, keep lead id, store consent, then verify the result before making broader changes.
What to check first
- Map every WordPress form field to a CRM field and a Data Manager API field before writing upload code.
- Keep one stable lead ID across the WordPress entry, CRM record, and upload event.
- Store consent state, source URL, click IDs, and user-provided data with clear retention rules.
- Separate raw lead, qualified lead, booked call, and closed-won conversion actions.
- Log accepted rows, rejected rows, API errors, destination references, and retry status.
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 |
|---|
| Map fields | Map every WordPress form field to a CRM field and a Data Manager API field before writing upload code. | A test lead can be traced from WordPress to CRM to the upload event. |
| Keep lead ID | Keep one stable lead ID across the WordPress entry, CRM record, and upload event. | The same lead ID appears in the form entry, CRM row, and upload logs. |
| Store consent | Store consent state, source URL, click IDs, and user-provided data with clear retention rules. | Rejected events show the field that failed instead of disappearing silently. |
| Separate actions | Separate raw lead, qualified lead, booked call, and closed-won conversion actions. | The Google Ads conversion action matches the CRM stage being uploaded. |
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
field_map:
wordpress_entry_id: lead_id
gclid: ad_click_id
consent_state: consent.ad_user_data
email_hash: user_data.email_address
phone_hash: user_data.phone_number
crm_stage: conversion_action
value: conversion_value
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.
- Map fields
- Keep lead ID
- Store consent
- Separate actions
- Log diagnostics
Production verification checklist
- A test lead can be traced from WordPress to CRM to the upload event.
- The same lead ID appears in the form entry, CRM row, and upload logs.
- Rejected events show the field that failed instead of disappearing silently.
- The Google Ads conversion action matches the CRM stage being uploaded.
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, map WordPress lead fields for Google Ads.
Helpful references
Operate the upload after field mapping
After the payload fields are mapped, use the Data Manager API service account access guide to verify authentication and destination permissions. Then retain every request ID and follow the Data Manager API partial success runbook for downstream diagnostics and safe retries.
Operate consent, duplicates, and encrypted uploads
After mapping fields, classify downstream outcomes with the Data Manager consent error queue and the duplicate identifier audit. Encrypted pipelines should also verify the AWS KMS wrapped-key permission path.
Validate destination and event-name ownership
When mapped events are rejected, use the multiple Google Analytics destinations error fix to make destination references unambiguous, then apply the Data Manager invalid event-name audit to reserved and dynamically generated names.
Keep every destination reference unique
For requests that route events to more than one account or product, use the Data Manager API duplicate destination reference fix to normalize request-level references, update event routing, validate a small batch, and protect transaction ID deduplication.
Handle event-time rejects outside the normal retry queue
When an upload returns EVENT_TIME_INVALID, use the Data Manager API event-time window and retry policy to preserve the original timestamp, check UTC conversion and clock drift, and move permanent rejects out of the active queue.