Severity: HighOwner: CMP adminTime to fix: 15-45 min
Reject button only in second layer
Expose Reject on the first layer instead of forcing users into extra clicks or preference screens to refuse optional processing.
Covers: reject_in_second_layer, reject_not_first_layer
Why this matters
A reject option buried in a second layer weakens free choice and often fails the equal-friction standard expected for valid consent interfaces.
How to verify manually
- Open the first-layer banner on desktop and mobile.
- Check whether the user can refuse optional processing without opening extra settings.
- Compare the effort required for Accept versus Reject flows.
Typical root causes
- The CMP template is configured to show Reject only in preferences.
- Custom styling or banner copy removed the first-layer reject action.
- The design prioritizes opt-in conversion over equal user choice.
GTM fix
- Update the CMP template or container settings to expose Reject in the first layer.
- Confirm Reject sends the same denied state regardless of whether preferences are opened.
- Retest both desktop and mobile banner layouts.
WordPress fix
- Enable the decline or reject action in plugin settings for the initial banner view.
- Adjust banner layout so the first-layer action remains visible on small screens.
- Remove CSS that hides or collapses the reject control.
Generic fix
- Place Reject next to Accept in the first-layer banner.
- Do not require a second interaction just to refuse optional processing.
- Keep the first-layer wording neutral and not nudging toward acceptance.
How to confirm the fix worked
- Confirm Reject is present in the first layer on desktop and mobile.
- Confirm rejecting from the first layer prevents optional tags from firing.
- Run a fresh scan and verify the issue is no longer flagged.
Next step
Re-scan after deployment to confirm that the runtime behavior changed, not just the banner copy.