Redirect
Use Redirect when one button-style element needs multiple destination links.
Content settings
| Setting | What it controls |
|---|---|
| Link rows | Add, remove, reorder, and edit destinations. |
| URL | Destination for each redirect link. |
| Target | Same window or new tab behavior when available. |
| Tracking | Click tracking or pixel events when configured. |
Style settings
| Style area | What you can adjust |
|---|---|
| Typography | Font, size, weight, and line height. |
| Button style | Text color, background, border, radius, padding, width, and hover state. |
| Layout | Alignment, spacing, and responsive behavior. |
Best practices
- Use Redirect only when multiple destinations belong together.
- Use separate Button elements when each action needs equal visual weight.
- Replace placeholder URLs before publishing.
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 Redirect, 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 Redirect, 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 Redirect, 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 Redirect, keep a short checklist of the fields you changed and test the result in the same browser session.