Data Manager API

Data Manager API GMP Offline Conversion Deduplication

HandL WP Engineering·Jul 3, 2026

When WordPress forms, CRMs, and offline upload jobs all report the same lead or sale, Google Marketing Platform conversion reporting can become inflated unless there is a clear deduplication key. Data Manager API implementations should define lead ID, event timestamp, Floodlight activity, consent state, and source priority before the first batch.

Use this for teams sending offline conversions from WordPress lead forms into Campaign Manager 360, Search Ads 360, Display and Video 360, or other Google Marketing Platform reporting paths.

Quick answer

Data Manager API GMP Offline Conversion Deduplication should be handled with a narrow evidence-first workflow: choose stable id, map activities, set source priority, then verify the result before making broader changes.

What to check first

Choose one stable lead or transaction ID that follows the record from WordPress to CRM to upload.
Map each conversion activity to the CRM outcome that should trigger it.
Define source priority when WordPress and CRM can both create a conversion row.
Check timestamp windows, timezone handling, consent state, and hashed user data rules.
Build diagnostics for duplicate keys, rejected rows, accepted rows, and suppressed rows.

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 stable ID	Choose one stable lead or transaction ID that follows the record from WordPress to CRM to upload.	One real lead creates one intended offline conversion row.
Map activities	Map each conversion activity to the CRM outcome that should trigger it.	Suppressed duplicates are visible with source and reason.
Set source priority	Define source priority when WordPress and CRM can both create a conversion row.	Accepted rows can be traced back to WordPress and CRM records.
Normalize timestamps	Check timestamp windows, timezone handling, consent state, and hashed user data rules.	Marketing can reconcile GMP counts against CRM accepted outcomes.

Why this usually happens

A form submit and a CRM qualification can look like two events even when they refer to one lead.
Upload jobs may run after CRM edits and produce rows with slightly different timestamps.
Floodlight activity names do not automatically explain source priority.
Deduplication cannot be fixed later without source IDs and upload logs.

Field notes

Start with one activity and one CRM outcome before scaling the feed.
Keep a test lead with a fake but stable ID through every system.
Dashboard suppressed duplicates so marketing trusts the lower count.

Useful command or data shape

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

dedupe_key:
  source_lead_id: gf-209842
  crm_id: crm-88421
  activity: qualified_lead
  event_time: 2026-07-03T15:22:00Z
  source_priority: crm_over_form
  consent_state: granted
  action: suppress_duplicate_form_row

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 stable ID
Map activities
Set source priority
Normalize timestamps
Dashboard diagnostics

What to tell the client or owner

Give marketing the dedupe key, source priority rule, accepted-row logic, and duplicate suppression dashboard columns.

Production verification checklist

One real lead creates one intended offline conversion row.
Suppressed duplicates are visible with source and reason.
Accepted rows can be traced back to WordPress and CRM records.
Marketing can reconcile GMP counts against CRM accepted outcomes.

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, deduplicate offline conversions.

Related HandL WP guides

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

Helpful references

Data Manager API Google Ads Attribution