Data Manager API Consent Missing Rejected Rows Dashboard
If Data Manager API rows are rejected because consent is missing, the fix is not only an upload retry. The WordPress form, cookie banner, CRM field, and upload mapper need to agree on consent state before conversion data is sent.
Use this for teams that collect WordPress leads, import offline conversions, and need to explain why some rows are not eligible for Google Ads uploads.
Quick answer
Data Manager API Consent Missing Rejected Rows Dashboard should be handled with a narrow evidence-first workflow: capture consent, store source fields, classify rejection, then verify the result before making broader changes.
What to check first
- Capture consent state at form submit time, not only at upload time.
- Store the consent source, timestamp, policy version, and form ID with the lead record.
- Show upload status by consent state so rejected rows are visible to marketing and compliance.
- Separate missing consent from denied consent. Those rows should not be treated the same.
- Review whether the cookie banner, form plugin, and CRM mapping use the same field names.
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 at form submit time, not only at upload time. | Accepted, denied, and missing-consent test leads appear in separate dashboard states. |
| Store source fields | Store the consent source, timestamp, policy version, and form ID with the lead record. | Upload logic suppresses rows that should not be sent. |
| Classify rejection | Show upload status by consent state so rejected rows are visible to marketing and compliance. | Missing-consent rows point back to a specific page, form, or field mapping. |
| Dashboard causes | Separate missing consent from denied consent. Those rows should not be treated the same. | Marketing can explain the conversion gap without opening raw logs. |
Why this usually happens
- Consent mode often lives in the browser while offline conversions are uploaded days later from the CRM.
- A hidden form field can be missing on one landing page even when the banner works elsewhere.
- Denied consent should suppress or alter uploads, while missing consent usually means instrumentation is broken.
- Marketing teams may only see lower conversion counts unless rejected rows are surfaced.
Field notes
- Keep consent fields out of free-text notes. Use predictable enum values.
- Run one accepted test lead, one denied test lead, and one missing-consent test lead before release.
- Dashboard rejected rows by cause: missing consent, denied consent, invalid identifier, timestamp, duplicate.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
dashboard_columns:
lead_id: GF-20260701-2044
form_id: quote_form
consent_state: missing
consent_source: not_recorded
upload_status: rejected
rejection_reason: consent_missing
owner: web_tracking
action: fix_form_hidden_field
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
- Store source fields
- Classify rejection
- Dashboard causes
- Retest uploads
What to tell the client or owner
Tell stakeholders the dashboard separates tracking defects from privacy choices. Missing consent is a fix task. Denied consent is a user choice to respect.
Production verification checklist
- Accepted, denied, and missing-consent test leads appear in separate dashboard states.
- Upload logic suppresses rows that should not be sent.
- Missing-consent rows point back to a specific page, form, or field mapping.
- Marketing can explain the conversion gap without opening raw logs.
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 WordPress consent and conversion uploads.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
- Data Manager API consent denied handling for WordPress leads
- Google Ads Data Manager consent mapping for WordPress forms