Widget automations
Automations are extra actions that run when the visitor interacts with a widget element: track a conversion, send the lead to your email platform, call a webhook, add a product to the cart, open another widget, run your own JavaScript and more. They run alongside the element's action, which decides what happens on the widget itself, such as closing it or going to the next step.
Available on: all platforms. Platform and integration automations need that platform or integration.
How it works
- You add automations to an element in its Interaction tab, under Automation. Click Add action, choose Action in (Personizely, or one of your enabled integrations) and the Action type, and fill in its options.
- When the element's event happens, every automation on it runs.
- Some automations run in the visitor's browser straight away. Others run on Personizely's servers once the event has been recorded.
Which elements support automations
Element | Event that runs the automations |
|---|---|
Click | |
Click (the Automation section appears once the image has an action) | |
Successful submit | |
Answer submitted | |
Reaches zero while the widget is displayed | |
Product button click | |
The cart crosses the goal while the widget is displayed | |
The wheel lands on a segment (automations are set per segment) |
Headline, Text, Coupon, HTML, Video, Map, Social, Divider, Spacer and Container don't support automations.
Track widget conversion is added automatically to new Button, Survey, Products and Form elements. Removing it shows a warning: "If you remove this action you will not be able to track conversions and revenue of this element in this widget."
Catalog
Personizely
Automation | What it does | Runs |
|---|---|---|
Counts a conversion for the widget, used for conversion rate and goal attribution | Browser and server | |
Counts a completion, a second success metric | Browser and server | |
Opens another widget | Browser | |
Emails the visitor's details to your team | Server | |
Runs your code on the page | Browser | |
Posts the visitor's profile to your URL as JSON | Server | |
Sets a field on the visitor's profile | Browser, saved on the server | |
Runs a content personalization with the Manual trigger | Browser |
Run campaign is listed when your plan includes campaigns or during a trial.
Shopify
Automation | What it does | Runs |
|---|---|---|
Add customer | Creates or updates a Shopify customer, with tags | Server |
Apply discount | Applies a discount code, or a newly generated unique code, to the cart | Browser |
Add a product to the cart | Adds a product variant to the cart | Browser |
Set cart attribute | Sets a cart attribute that's saved on the order | Browser |
Change user consent | Grants tracking consent in Shopify's customer privacy settings | Browser |
Wix
Automation | What it does | Runs |
|---|---|---|
Add contact | Adds the visitor to your Wix contacts | Server |
Add label to contact | Adds a Wix contact label | Server |
Subscribe | Subscribes the visitor in Wix | Server |
Checkout | Takes the visitor to Wix checkout | Browser |
Email, SMS and CRM integrations
Each connected integration adds its own automations, such as adding the visitor to a Klaviyo list, tagging a contact or subscribing to SMS. They run on Personizely's servers. See Integrations.
Behavior details and limitations
- Browser automations run immediately, before the event has reached Personizely. Server automations run after the event has been recorded, a moment later.
- Server automations need a recorded event. They run for clicks, submits, timer and cart-progress completions, and wheel spins. A click is recorded whenever the element has at least one automation.
- Order. Integration automations (for example adding a contact to Klaviyo, then sending a webhook) run one after another in the order listed. Browser automations such as Show widget or Execute JavaScript run straight away and don't wait for integration automations to finish.
- Failures don't block the visitor. If an integration rejects a request, for example because its credentials expired, the widget keeps working and the other automations still run.
- Disabled integrations. Automations of a disabled integration are greyed out ("This integration is disabled") and don't run.
- Control group. Visitors in a widget A/B test's control group see nothing, so no automations run for them.
- Preview. A preview records no events, so server automations (alerts, webhooks, integrations, conversion counting) don't run. Browser automations such as Show widget, Execute JavaScript code or Add a product to the cart do run.
- Element actions are separate. Opening a URL, closing the widget and going to a step are actions, not automations.
Examples
- Newsletter signup: Form with Track widget conversion, Klaviyo "Add to list" and Send alert to your marketing inbox.
- Upsell button: Button with Add a product to the cart, Track widget conversion and Close widget as its action.
- Quiz to personalization: Survey with Change field value and Run campaign, showing a homepage tailored to the answer.