Settings
Page settings control page-level behavior in the Atomicat Page Builder.
Use Settings to configure SEO metadata, tracking pixels, custom code, delay behavior, feature toggles, page speed options, and revisions when your account has access.
Settings tabs​
The settings popup includes several tabs. Availability can vary by page type, account access, or feature availability.
| Setting tab | Purpose |
|---|---|
| Optimizer | Page optimization options, including ad-campaign destination and platform optimization settings when available. |
| SEO | Page title, description, Open Graph metadata, keywords, canonical links, favicon, social image, and related metadata. |
| Delay | Page delay behavior, including delay timing and video synchronization when supported. |
| Pixel | Tracking pixel configuration and related usage information. |
| Code | Custom code areas for scripts and tags. |
| Features | Page-level feature toggles such as developer tools, search engine behavior, parameter passing, back redirect, privacy terms, and scroll behavior when configured. |
| Page Speed | Performance-related page settings. This tab is not shown for quiz routes. |
| Revisions | Page revision history when backup access is available. |
When to use Settings​
Use Settings after the main page content is ready.
Configure settings when you need to:
- Add SEO metadata before publishing.
- Add tracking scripts or pixels.
- Add custom integration code.
- Control delay behavior for page content.
- Enable or disable page-level features.
- Review previous revisions.
- Improve page performance.
Choose the right settings guide​
Each settings page focuses on a specific page-level responsibility:
| Goal | Start here |
|---|---|
| Make the page clearer for Google and social previews | Optimizer and SEO fields |
| Generate title and description ideas with AI | AI SEO generation |
| Control delayed content or video-based reveal timing | Page delay |
| Add browser pixels and campaign tracking | Pixels and tracking |
| Send server-side conversion events | Server events |
| Configure Utmify tracking | Utmify pixels |
| Use Atomicat tracking reports | AtomicTracker |
| Add custom scripts or tags | Custom code |
| Enable or disable page behavior | Page features |
| Review performance-related options | Page Speed insights |
| Restore an earlier page state | Page revisions |
Custom code safety​
Atomicat validates custom code before saving. Malformed <script>, <style>, or <noscript> tags can block saving.
Review custom code carefully and only add scripts from trusted sources.
Recommended settings workflow​
- Finish the page structure and main content.
- Add SEO title, description, social image, and keywords.
- Configure pixels or tracking integrations.
- Add custom code only if required.
- Review page features and page speed options.
- Save the page.
- Publish or test the page.
Related docs​
- Pixels and tracking
- How to add pixels to a page
- Page delay
- How to apply video delay
- Optimizer and SEO fields
- AI SEO generation
- Page delay
- Pixels and tracking
- Server events (Conversions API)
- Utmify pixels
- AtomicTracker
- Custom code
- Page features
- Page Speed insights
- Page revisions
FAQ​
Should I configure Settings before or after building the page?
Build the main page content first, then configure Settings before publishing. SEO metadata, tracking, custom code, delay behavior, features, and page speed options should be reviewed once the final visitor path is clear.
Which Settings tab affects Google search results?
The SEO tab controls the page title, description, canonical URL, keywords, favicon, Open Graph image, and related metadata that can influence search snippets and sharing previews.
Where should I add tracking scripts?
Use Pixel, Server Events, Utmify, AtomicTracker, or Custom Code depending on the tracking method. Avoid pasting the same pixel in multiple places unless the campaign requires it.
Why do I not see every Settings tab?
Some tabs depend on the page type, plan, enabled modules, workspace permissions, or feature rollout. For example, Page Speed is not shown for quiz routes, and Revisions depend on backup access.