Enhanced conversions and offline lead uploads need consent-aware handling. A denied or missing consent state should not be silently mixed into the same upload path as granted leads, and it should not send restricted user data just because the CRM stage changed.
Use this for WordPress forms, CRMs, call tracking, WooCommerce leads, or Google Ads uploads where consent mode, privacy rules, and lead qualification status all affect what can be sent.
Quick answer
Google Ads Enhanced Conversions Consent Denied Queue should be handled with a narrow evidence-first workflow: capture consent, split queues, suppress fields, then verify the result before making broader changes.
What to check first
- Capture consent state, consent timestamp, source page, form ID, and lead ID at submission time.
- Route denied, missing, granted, and region-specific consent states into separate queues.
- Suppress or transform user data fields according to the policy for that consent state.
- Keep a reason code for every row that is held, suppressed, uploaded, or retried.
- Review Data Manager API diagnostics without exposing raw personal data in tickets.
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 |
|---|
| Capture consent | Capture consent state, consent timestamp, source page, form ID, and lead ID at submission time. | Granted leads can upload through the expected conversion action. |
| Split queues | Route denied, missing, granted, and region-specific consent states into separate queues. | Denied and missing consent rows are visible but do not send restricted user data. |
| Suppress fields | Suppress or transform user data fields according to the policy for that consent state. | Retry logic cannot override a suppression reason by accident. |
| Store reason codes | Keep a reason code for every row that is held, suppressed, uploaded, or retried. | Marketing can see suppressed volume without seeing raw personal data. |
Why this usually happens
- Lead qualification can happen days after the original consent decision.
- CRM users may see only the sales stage and miss the consent state attached to the lead.
- A retry queue can accidentally upload rows that were intentionally suppressed.
- Consent-denied rows still need operational visibility so marketers understand volume and data loss.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
consent_queue_row:
lead_id: cf7-9921
consent_state: denied
crm_stage: qualified_lead
upload_status: suppressed
reason_code: ads_data_denied
user_data: omitted
reviewed_at: 2026-07-10T13:30:00Z
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.
- Capture consent
- Split queues
- Suppress fields
- Store reason codes
- Review diagnostics
What to tell the client or owner
Report upload count, suppressed count, denied count, missing-consent count, and rejected count as separate numbers.
Production verification checklist
- Granted leads can upload through the expected conversion action.
- Denied and missing consent rows are visible but do not send restricted user data.
- Retry logic cannot override a suppression reason by accident.
- Marketing can see suppressed volume without seeing 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, fix consent-aware Google Ads conversion uploads.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Helpful references