Google Ads

Data Manager API Google Marketing Platform Offline Conversion Map

HandL WP Engineering·Jul 2, 2026

The Data Manager API supports sending offline conversion events for Google Marketing Platform products, but WordPress lead teams still need a clean source-to-upload map. Lead ID, click IDs, user data, Floodlight activity, consent state, CRM status, and diagnostics have to travel together.

Use this for WordPress lead generation sites, agencies, or ecommerce teams sending qualified leads or offline revenue to Campaign Manager 360, Search Ads 360, Display and Video 360, or related Google measurement products.

Quick answer

Data Manager API Google Marketing Platform Offline Conversion Map should be handled with a narrow evidence-first workflow: choose conversion event, map fields, preserve lead id, then verify the result before making broader changes.

What to check first

Choose the source event that represents a qualified offline conversion, not every raw form submit.
Map WordPress form fields, CRM fields, consent fields, click IDs, and Floodlight fields in one table.
Preserve a stable lead ID from form entry to CRM to upload row.
Normalize user data only when policy and consent allow it.
Log accepted rows, rejected rows, partial failures, and upload timestamps for marketing review.

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
Choose conversion event	Choose the source event that represents a qualified offline conversion, not every raw form submit.	Every upload row can be traced back to a WordPress form entry and CRM record.
Map fields	Map WordPress form fields, CRM fields, consent fields, click IDs, and Floodlight fields in one table.	Only qualified events are uploaded to the chosen activity.
Preserve lead ID	Preserve a stable lead ID from form entry to CRM to upload row.	Consent handling is documented before hashing or sending user data.
Apply consent rules	Normalize user data only when policy and consent allow it.	Rejected rows are visible with enough detail to fix the source data.

Why this usually happens

Offline conversion uploads often fail because the CRM stage and original form entry do not share an ID.
Google Marketing Platform fields are different from a simple Google Ads lead import.
Consent and user-data handling need to be decided before a developer writes the upload code.
Marketing teams need rejected-row diagnostics, not only a background job that says complete.

Field notes

Start with one conversion action and one CRM stage before adding every lifecycle event.
Keep a sample row with fake data so field owners can approve the map.
Use partial failure handling so one bad lead does not hide all accepted leads.

Useful command or data shape

Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.

offline_conversion_map:
  source: gravity_forms_entry
  lead_id: entry_id
  crm_stage: sales_qualified
  product: campaign_manager_360
  activity: consultation_booked
  consent_state: granted
  diagnostics: accepted_rows, rejected_rows, partial_failures

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.

Choose conversion event
Map fields
Preserve lead ID
Apply consent rules
Expose diagnostics

What to tell the client or owner

Give marketing a one-page field map with source field, transformed field, destination field, consent rule, and diagnostic owner.

Production verification checklist

Every upload row can be traced back to a WordPress form entry and CRM record.
Only qualified events are uploaded to the chosen activity.
Consent handling is documented before hashing or sending user data.
Rejected rows are visible with enough detail to fix the source data.

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 offline conversions from WordPress.

Related HandL WP guides

Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.

Helpful references

Google Ads Data Manager API Conversion Tracking