Cookie
Use Cookie to show a cookie notice or simple consent-style message.
Content settings
| Setting | What it controls |
|---|---|
| Cookie text | Notice text shown to visitors. |
| Button text | Confirmation or accept button label. |
| Link text | Privacy, terms, or policy link text when available. |
| Link URL | Destination for privacy or cookie policy. |
| Position | Where the notice appears on the page. |
Style settings
| Style area | What you can adjust |
|---|---|
| Button | Text color, background, border, radius, padding, and hover state. |
| Container | Background, text color, border, radius, shadow, width, and spacing. |
| Responsive placement | Position and size on mobile. |
Best practices
- Confirm legal requirements for your traffic regions.
- Keep text short and understandable.
- Test overlap with sticky CTAs or chat buttons.
FAQ
When should I use this page?
Use this page when you need a quick reference for this Atomicat feature and want to understand what it changes before editing or publishing. It is especially useful while reviewing a page, funnel, quiz, lead flow, product setup, video configuration, or account setting. For Cookie, keep a short checklist of the fields you changed and test the result in the same browser session.
Do I need to configure this before publishing?
Configure it before publishing whenever the feature affects visitor behavior, tracking, SEO, forms, embeds, checkout, or access. If the feature only changes internal organization, review it before launch so your team can manage the campaign consistently. For Cookie, keep a short checklist of the fields you changed and test the result in the same browser session.
Can this affect live pages?
Yes, some settings can affect live pages after saving or publishing. Always preview the page, test the main action, and confirm desktop and mobile behavior before sending paid traffic or sharing the URL. For Cookie, keep a short checklist of the fields you changed and test the result in the same browser session.
What should I check if something looks wrong?
Check the page status, project access, saved revisions, browser cache, connected domain, and any related integrations. If the feature depends on a plan, permission, or enabled module, confirm that your workspace has access. For Cookie, keep a short checklist of the fields you changed and test the result in the same browser session.