Notification
Use Notification to show a short on-page message or social-proof notice.
Content settings
| Setting | What it controls |
|---|---|
| Notification text | Message shown to the visitor. |
| Template or type | Notification layout or preset when available. |
| Timing | Delay, duration, repeat, or display timing when supported. |
| Position | Where the notification appears. |
Style settings
| Style area | What you can adjust |
|---|---|
| Container | Background, border, radius, shadow, padding, and spacing. |
| Text | Typography and color. |
| Icon | Icon color, size, or placement when available. |
| Animation | Motion effects when available. |
Best practices
- Keep notifications short.
- Avoid covering forms, CTAs, or checkout buttons.
- Test mobile safe areas and z-index behavior.
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 Notification, 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 Notification, 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 Notification, 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 Notification, keep a short checklist of the fields you changed and test the result in the same browser session.