Email and SMS integrations
Email and SMS integrations send the people who sign up through your Personizely widgets straight to your email marketing, SMS or CRM platform, such as Klaviyo, Mailchimp, Omnisend, Brevo, HubSpot, Attentive, Postscript or Yotpo. You attach an action like "Add to list" or "Add subscriber with keyword" to a form, and every submission creates or updates the contact in your platform with the details the visitor entered and the ones Personizely already knows.
Available on: all platforms. 29 email, SMS and CRM platforms are supported; see the catalogue.
How it works
- Connect the platform in Settings → Integrations, by OAuth or API key. Personizely loads your lists, tags, keywords and fields from it.
- Add an automation to the widget element that collects the contact, usually a Form element: in its Interaction tab, under Automation, click Add action, choose the platform in Action in, pick the Action type (for example Subscribe to list) and its list.
- A visitor submits the form. The values are validated and saved to the visitor's Contacts and form submissions in Personizely.
- The automation runs on Personizely's servers a moment later and sends the contact to your platform. Several automations on the same element run one after another, in the order listed.
- Your platform takes over: welcome flows, confirmation emails and SMS compliance messages are sent by your platform, under its settings.
Because automations run server-side, they work regardless of ad-blockers and don't slow the widget down. The visitor sees the success step or redirect straight away.
What's sent
Each automation sends the visitor's whole profile, not only the fields in that form:
- Contact details from this or earlier submissions: email, phone, first and last name, company, address, birthdate.
- Consent fields the visitor answered, such as Email marketing consent.
- Tracking fields Personizely recorded, such as UTM source and campaign, referrer and first visited page, and location (country, region, city, zip), where the platform has a place for them.
- Your Custom fields, such as a quiz answer.
How those land in your platform depends on the platform:
Model | Platforms | What happens |
|---|---|---|
You map fields in the Mappings dialog | Mailchimp, Brevo, HubSpot, ActiveCampaign, Constant Contact, ConvertKit, MailerLite and most other email platforms | Each platform field gets the Personizely field you choose. Unmapped fields aren't sent |
Automatic | Klaviyo, Omnisend, Attentive, Postscript, Yotpo, Ometria, CM Commerce | Standard details go to the platform's standard properties; every other field with a value becomes a custom property named after the Personizely field |
Details are on each platform's page and in Field mapping.
What each action needs
Platform type | Needs on the profile |
|---|---|
Email-only platforms (Mailchimp, AWeber, ConvertKit, …) | An email address |
Klaviyo, Omnisend, Brevo, HubSpot, Attentive, Yotpo | An email address or a phone number |
Postscript | A phone number |
If the profile doesn't have it, that automation is skipped and the others still run. Phone numbers are stored and sent in international format, such as +14155550123. Use the Form element's phone field, which formats numbers for you.
Lists, tags and other destinations
The available actions differ per platform. The most common:
Action | What it does | Platforms (examples) |
|---|---|---|
Add or update contact | Creates the contact, or updates it if it exists | Brevo, HubSpot, Omnisend, Yotpo, ActiveCampaign, MailerLite |
Add to list | Adds the contact to a list or audience | Klaviyo, Mailchimp, Brevo, HubSpot, Yotpo, most others |
Subscribe to list | Adds the contact with email (and SMS) marketing consent | Klaviyo |
Remove from list / Unsubscribe | Removes the contact, or marks them unsubscribed | Klaviyo, Mailchimp, Brevo, HubSpot, most others |
Tags | Adds tags as part of another action, or as their own action | Mailchimp, Omnisend, Postscript, ActiveCampaign, ConvertKit |
Keyword or sign-up source | Subscribes a phone number to an SMS program | Postscript, Attentive |
Trigger event | Sends a custom event you can use to start a flow | Yotpo |
Lists, tags and keywords are loaded when you connect. Click Refresh on the integration after creating new ones in your platform.
On platforms where Add to list only works for an existing contact (the action's help text says "You might need an Add or update contact action before this one"), add Add or update contact first, above it.
Consent and double opt-in
Personizely sends what the visitor submitted. Whether that counts as marketing consent depends on the action you pick:
Platform | Single opt-in (subscribed immediately) | Double opt-in (confirmation first) |
|---|---|---|
Klaviyo | Add to list adds to the list without recording consent; Subscribe to list records consent immediately when the list is single opt-in | Subscribe to list follows the list's double opt-in setting |
Mailchimp | Add to list | Add with confirmation to list: Mailchimp emails a confirmation link |
Brevo | Add or update contact, Add to list | Add or update contact with confirmation: Brevo sends your double opt-in template |
SendPulse | Add to list | Add to list with confirmation |
CleverReach | Add to list | Add to list with inactive status |
Omnisend | Add or update contact subscribes email, and SMS when the visitor gave SMS consent on the form | Not available |
Yotpo | Add to list subscribes only the channels the visitor consented to in the form | Not available |
Postscript, Attentive | Your keyword or sign-up source decides the compliance flow | Set in Postscript or Attentive |
Two rules hold everywhere:
- Your form is the consent capture. Add a checkbox for Email marketing consent, SMS marketing consent or Marketing consent - Email and SMS, with the wording your region requires, when the action you chose subscribes people immediately. Yotpo, the Shopify Add customer action, Klaviyo Subscribe to list and Omnisend read these fields to decide what to subscribe; other platforms receive them as data.
- SMS needs explicit consent. Klaviyo Subscribe to list and Omnisend subscribe a phone number to SMS marketing only when the visitor gives SMS consent on the form. Add an SMS marketing consent or Marketing consent - Email and SMS checkbox to forms that collect a phone number.
Targeting with platform data
Some platforms also send data back to Personizely, so you can target visitors by their status in your email tool:
- List, tag and form filters for Mailchimp, Brevo, ActiveCampaign, ConvertKit, Campaign Monitor, GetResponse, AWeber, iContact, MailerLite, SendPulse and Ometria. See Email list and tag filters.
- Profile sync: mapped fields updated in Mailchimp, Brevo or HubSpot update the visitor's fields in Personizely, which you can target with the Visitor fields filter filter.
- Identification from email links for platforms that put a subscriber ID in links. See Identifying visitors.
A common use: hide your signup popup from people who are already subscribed, with a target such as "Mailchimp List: Visitor is not subscribed to Newsletter".
Behavior details and limitations
- The latest value wins. Each automation sends the profile as it is at that moment. A visitor who submits a second form with a new first name updates the contact's name in your platform.
- Existing contacts are updated, not duplicated. Platforms match the contact on email (or phone), so a returning subscriber who signs up again is updated in place.
- Submissions before you added the automation aren't sent. Export them from Contacts and form submissions and import them into your platform.
- Deleting a contact in Personizely doesn't delete it in your platform, and the other way round, except for HubSpot, where a deletion clears the visitor's personal data in Personizely.
- Disconnecting stops the automations. They stay on your widgets, greyed out, and run again once you reconnect.
- Widget A/B test control groups see no widget, so no automations run for them.
Examples
- Klaviyo welcome series: Form with Email and a consent checkbox → Subscribe to list "Newsletter". Klaviyo's welcome flow, triggered by the list, sends the discount code.
- SMS and email in two steps: step 1 collects email with Mailchimp Add to list; step 2 collects a phone number with SMS consent and Postscript Add subscriber with keyword.
- B2B lead to CRM: Form with name, email, company and a "Team size" custom field → HubSpot Add or update contact with "Team size" mapped to a HubSpot property, then Add to list "Website leads".
Troubleshooting
- Nothing arrives in the platform → test on the live site (previews don't run automations), check the integration is connected and that the form collects the email or phone the action needs.
- Contacts arrive without names or custom fields → map the fields in Mappings, or for automatic platforms check the custom property names in the contact's profile.
- Contacts arrive but don't get emails → check the action: Add to list on Klaviyo doesn't record consent, and double opt-in actions wait for the visitor to confirm.
- A new list isn't in the dropdown → click Refresh on the integration.