Seasonal Popups, Sale Overlays, and Consent: Stacking Prompts Without Breaking Either

Published 2026-10-21

Peak trading creates a prompt pileup. The consent banner appears, a sale overlay covers it, an exit intent popup fires over that, and a chat widget opens in the corner. Each team added its prompt in isolation, and together they guarantee that visitors dismiss everything unread, including the one prompt with legal consequences.

This guide covers how to sequence competing prompts during campaigns: why consent must stand alone, how to hold and release marketing overlays fairly, what never to do with dismissal behaviour, and how to plan the prompt calendar before the sale rather than during it.

Consent gets the first, clear moment

The consent choice should be the first interactive layer a new visitor meets, and it should be fully visible and usable, not partially covered by a promotional overlay with a higher stacking order. This is partly legal, since a choice made while the banner was obscured is hard to defend, and partly practical, because visitors who clear the banner properly give you a stored state that ends the question for the rest of the visit. Audit stacking order and focus behaviour as part of campaign setup, not after complaints arrive.

Queue the marketing prompts

Once consent is resolved, release marketing overlays in a deliberate order with delays between them: the campaign offer first if it is time limited, secondary prompts like newsletter signup later or on relevant pages only. A simple prompt queue in code, where each overlay registers and waits its turn, prevents the pileup permanently rather than relying on every team remembering every other teams campaign dates. Cap the total: a visitor who has dismissed two prompts in a session should be left alone to shop.

Dismissal must mean what it says

The fastest way to destroy trust in both systems is dismissal tricks: a close button that opens the offer in a new tab, a no thanks link that counts as consent, or a banner that returns on every page until accepted. Keep each prompts dismissal independent and final for its stated period. In particular, never wire a marketing overlay interaction into consent state. Clicking away a sale popup is not a privacy choice, and treating it as one corrupts the receipt.

Plan the stack before the sale

Prompt conflicts are a calendar problem disguised as a design problem. Before peak periods, list every layer that can appear, who owns it, its dates, and its priority, and test the full stack on the staging version of the highest traffic templates. Include the unglamorous cases: returning visitors with stored consent, mobile viewports where layers cover more of the screen, and accessibility focus order. Fifteen minutes of sequencing work before the campaign protects both conversion and the consent record the campaign traffic generates.

Related reading

These earlier guides cover connected questions in more depth: Consent Banners on Slow Networks: Choices That Load Before Trackers, Even on 3G, Geo Targeted Consent: Showing the Right Banner in the Right Region, and Consent and Lead Capture Popups: Discounts, Exit Intent, and the Trackers Inside.

Frequently asked questions