Data Manager diagnostics distinguish denied consent, no consent, and unknown consent. Treating them as one retryable error can resend records that should remain suppressed or hide missing source evidence.
Use this for WordPress lead and offline conversion pipelines that send consent-aware events through the Data Manager API.
Quick answer
Data Manager API Denied Consent Error Queue should be handled with a narrow evidence-first workflow: persist error context, classify reason, check consent layers, then verify the result before making broader changes.
What to check first
- Store request ID, internal batch ID, lead ID, consent reason, source form, and capture time.
- Map denied, no consent, and unknown consent to separate non-retry or review actions.
- Verify request-level, event-level, and account-level consent sources.
- Correct only missing or malformed evidence when the original user choice supports it.
- Reconcile suppressed, corrected, retried, and accepted counts without raw personal data.
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 |
|---|
| Persist error context | Store request ID, internal batch ID, lead ID, consent reason, source form, and capture time. | Denied consent rows remain suppressed. |
| Classify reason | Map denied, no consent, and unknown consent to separate non-retry or review actions. | Unknown and missing consent rows stay on hold until evidence exists. |
| Check consent layers | Verify request-level, event-level, and account-level consent sources. | Only eligible corrected rows enter a retry batch. |
| Correct evidence only | Correct only missing or malformed evidence when the original user choice supports it. | Batch counts reconcile to request-status diagnostics. |
Why this usually happens
- Request-level consent can be overridden by an event.
- Account settings can affect the overall consent result.
- A CRM can drop the original consent timestamp or source page.
- Blind retries cannot turn denied consent into granted consent.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
consent_error:
request_id: req-c91
lead_id: lead-312
reason: PROCESSING_ERROR_REASON_NO_CONSENT
source_form: gf-18
captured_at: null
action: hold_for_evidence
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.
- Persist error context
- Classify reason
- Check consent layers
- Correct evidence only
- Reconcile counts
What to tell the client or owner
Report request ID, reason counts, source forms, suppression count, review count, eligible retries, and final accepted count.
Production verification checklist
- Denied consent rows remain suppressed.
- Unknown and missing consent rows stay on hold until evidence exists.
- Only eligible corrected rows enter a retry batch.
- Batch counts reconcile to request-status diagnostics.
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 consent handling in WordPress conversion uploads.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Helpful references