Age Verification: verification modes, copy, and modal layout

Configure an age gate that satisfies policy requirements without destroying page UX: buttons, birthday checks, imagery, and deny behavior.

Quick start

  1. Open the editor: /get-widget/age-verification
  2. Choose the verification mode: buttons or date of birth.
  3. Add headline, description, button copy, and legal text.
  4. Configure image usage and image position.
  5. Tune overlay, modal styling, and denial behavior.
  6. Click Save & Get Code to publish and embed.

Verification mode: 2 buttons vs birthday input

Use the mode setting based on how strict the gate needs to be:

  • 2-button confirmation: the lowest-friction option and the best default for many marketing sites
  • Birthday verification: stronger friction, but more appropriate when policy requires an actual date check

If you switch to birthday mode, make sure the validation message and denied-state copy are customized for the language and tone of the site.

Copy configuration

Age Verification has more copy settings than a typical modal because legal clarity matters.

You can configure:

  • headline
  • subtitle / description
  • confirm button label
  • deny button label
  • legal text
  • invalid date warning
  • access denied warning

If you localize the site, customize these warnings directly instead of leaving generic English copy in place.

Image layout and background treatment

The widget supports several image placements:

  • left
  • right
  • top
  • bottom
  • centered composition

In addition, you can control:

  • whether the image is enabled at all
  • overlay color and opacity
  • blur amount
  • background color behind the modal
  • overall widget height for tighter or taller compositions

Use strong imagery carefully. If the image competes with the verification CTA, reduce the overlay contrast problem before changing typography.

Buttons, denial behavior, and branding

The confirmation and denial actions should be visually distinct. Configure:

  • primary and secondary button text
  • fill / border colors
  • radius and shape
  • button order where supported
  • optional redirect or deny-state outcome

For most sites, the confirm action should be visually primary and the deny action secondary but still obvious enough to remain compliant.

Need help? Send the right details (so we can answer fast)

Support is fastest when we can reproduce the issue.

Please include:

  • The page URL where the widget is embedded (or the editor URL)
  • The platform/builder (WordPress, Webflow, Shopify, Squarespace, etc.)
  • What you expected to happen vs what you see
  • A screenshot of where the snippet is pasted (or a short screen recording)

If your issue involves a social connection (Instagram/Threads/TikTok), also include:

  • Which login path you used (Instagram vs Meta vs TikTok)
  • A screenshot of the provider error screen (if any)
  • Whether the account is Personal vs Business/Creator

Contact us here: /support.