Redirect
Use Redirect when a click should send visitors to another destination, especially when the page needs multiple possible redirect URLs or query-parameter handling.
How It Works In Atomicatβ
In Atomicat 3.0 redirect behavior is tied to button click handling and a published redirect script. When a button has a links array, the script finds the component, chooses one random URL on click, merges missing query parameters from the source anchor, optionally applies pass-through parameters, and navigates the browser to the final URL.
When To Use Itβ
- Split click traffic between several destination URLs for a simple redirect test.
- Send visitors to different checkout or offer pages while keeping one visible CTA.
- Preserve tracking parameters such as UTMs when redirecting.
- Document a dedicated redirect CTA separately from normal Button behavior.
Configure The Elementβ
- Add or select the redirect-style button.
- Enter each destination URL in the redirect links list.
- Keep links absolute and valid; avoid JavaScript URLs.
- Confirm whether query parameters should pass to the destination.
- Style the visible button like any other CTA.
Testing Notesβ
- Click the redirect button several times to confirm different links can be selected.
- Check the final URL includes required query parameters.
- Test on the published page because script execution matters.
Limitations And Tipsβ
- Random redirect behavior can make debugging harder; keep a record of every destination.
- Redirect should not be used to hide misleading destinations.
- If only one destination is needed, a normal Button link is simpler.
Related Docsβ
FAQβ
How does random redirect work?
The publish script selects one URL from the button's links array at click time.
Are URL parameters preserved?
The script merges missing query parameters from the anchor URL and can apply pass-through params when enabled.
Should I use Redirect for one link?
Usually no. Use a normal Button link unless you need redirect-specific behavior.