Enhanced conversion lead pipelines often store a consent state but omit the timestamp, source page, banner version, form version, or policy context. Those missing fields make suppression, troubleshooting, and compliance evidence harder.
Use this for WordPress forms that send hashed user data, click IDs, and offline conversion events to Google Ads or the Data Manager API.
Quick answer
Enhanced Conversions Missing Consent Timestamp Audit should be handled with a narrow evidence-first workflow: map fields, find missing context, normalize timestamps, then verify the result before making broader changes.
What to check first
- Inventory consent state, timestamp, source URL, form ID, banner version, policy version, lead ID, and click ID.
- Identify rows where consent is granted or denied but capture time or source context is missing.
- Confirm server and browser clocks use a consistent timezone and immutable event timestamp.
- Suppress rows whose consent cannot be determined instead of guessing from later CRM activity.
- Test one granted and one denied submission through storage, CRM, and upload queue.
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 | Inventory consent state, timestamp, source URL, form ID, banner version, policy version, lead ID, and click ID. | Every upload-eligible lead has consent state, timestamp, and source context. |
| Find missing context | Identify rows where consent is granted or denied but capture time or source context is missing. | Denied and unknown consent rows remain out of the upload queue. |
| Normalize timestamps | Confirm server and browser clocks use a consistent timezone and immutable event timestamp. | The original capture timestamp survives CRM and batch processing. |
| Suppress unknowns | Suppress rows whose consent cannot be determined instead of guessing from later CRM activity. | Audit logs use internal IDs and do not expose raw personal data. |
Why this usually happens
- Hidden form fields may capture state but not the exact consent event time.
- CRM imports can overwrite or drop source metadata.
- Server-side uploads may use processing time instead of the original lead timestamp.
- A later consent change should not silently rewrite the historical capture record.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
consent_audit_row:
lead_id: lead-20491
ad_user_data: GRANTED
captured_at: 2026-07-11T12:44:18Z
source_url: /request-help
form_id: gf-18
policy_version: 2026-06
upload_status: eligible
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
- Find missing context
- Normalize timestamps
- Suppress unknowns
- Test both states
What to tell the client or owner
Report the missing-field count, affected forms, suppression count, timestamp standard, policy owner, and the two end-to-end test IDs.
Production verification checklist
- Every upload-eligible lead has consent state, timestamp, and source context.
- Denied and unknown consent rows remain out of the upload queue.
- The original capture timestamp survives CRM and batch processing.
- Audit logs use internal IDs and do not expose raw personal 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, audit enhanced conversion consent handling.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Helpful references