Button
Use Button for a primary or secondary call to action.
Content settings
| Setting | What it controls |
|---|---|
| Label text | The visible CTA text. |
| URL or action | Destination URL, section, checkout, or supported action. |
| Target | Same window or new tab behavior. |
| Tracking | Pixel or click tracking when configured. |
| Icon | Optional icon when supported by the template. |
Style settings
| Style area | What you can adjust |
|---|---|
| Typography | Font, size, weight, line height, and letter spacing. |
| Normal state | Text color, background, border, radius, padding, width, and height. |
| Hover state | Hover text color, background, border, and animation. |
| Layout | Alignment, spacing, and responsive width. |
Best practices
- Use clear action verbs.
- Test the destination on the published page.
- Review pixel usage if the button is tracked.
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 Button, 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 Button, 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 Button, 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 Button, keep a short checklist of the fields you changed and test the result in the same browser session.