Poptin vs Personizely.
A welcome email or a different return visit?

Eye-catching (+0.64) · Entrance animation (+0.64)

A separate mobile version can change text, images, buttons and field order.

Radio buttons or a single-select dropdown.

Collected through the Message field.

Consent checkbox (+0.16) · Email marketing consent (+0.16)

Consent checkbox (+0.16) · Email marketing consent (+0.16) · SMS marketing consent (+0.32) · Privacy terms consent (+0.32)

Any input field can be set to hidden.

Multi-step (+0.32) · Popup steps (+0.32)

Logic (+0.32) · Action logic (+0.32)

Validation (+0.16) · Field validation (+0.32) · Email format (+0.32) · Phone format (+0.32) · Email typo check (+0.32) · Business email filter (+0.32)

Validation (+0.16) · Email verification (+0.32)

Set per popup or inherited from the account default.

Follow-up (+0.32) · After signup (+0.32) · Reward email (+0.32) · Email automation (+0.32) · Email sequences (+0.32) · Delays and branches (+0.32) · Lifecycle triggers (+0.32)

Separate play, winning and losing screens.

Spin the wheel (+0.13) · Prize weights (+0.13) · Losing slices (+0.13)

Spin the wheel (+0.13) · Prize weights (+0.13) · Losing slices (+0.13)

Audience targeting (+0.45) · Referrer targeting (+0.45) · Cart targeting (+0.45) · Profile targeting (+0.45) · Customer tags (+0.45) · Login status (+0.45) · Order history (+0.45)

Behavior triggers (+0.23) · Time delay (+0.23) · Exit intent (+0.23) · Scroll trigger (+0.23) · Inactivity trigger (+0.23)

Behavior triggers (+0.23) · Time delay (+0.23) · Exit intent (+0.23) · Scroll trigger (+0.23) · Inactivity trigger (+0.23) · Hover trigger (+0.45) · Page-load trigger (+0.45)

Separate repeat rules for new, returning and converted visitors.

An A/B variant is created from a finished campaign and grouped in one test.

A/B testing (+0.35) · Popup tests (+0.35)

A/B testing (+0.35) · Popup tests (+0.35)

Campaigns, segments and journeys; Growth Free covers 250 contacts and 500 emails.

One domain on Free and Basic, four on Pro, unlimited on Agency and Growth.

Workspaces (+0.28) · Several sites (+0.28) · Client portfolio (+0.56)

Workspaces (+0.28) · Several sites (+0.28)

Roles (+0.28) · Billing access controls (+0.56)

Contacts, email campaigns and popup analytics; keys are tied to one account.

HTTP API (+0.19) · Operate campaigns (+0.19) · Read performance (+0.19) · Scoped credentials (+0.19)

HTTP API (+0.19) · Operate campaigns (+0.19) · Read performance (+0.19) · Scoped credentials (+0.19)

MCP server (+0.38) · Operate campaigns (+0.38) · Read performance (+0.38) · Scoped credentials (+0.38)

Team notifications (+0.64) · Email (+0.64) · Slack (+0.64)

SmartrMail: Copy the API key from SmartrMail’s integration settings and the list ID from the subscriber list URL. Enter both under Email and Integrations on the poptin and approve. The guide confirms lead delivery to the list but gives no complete extra-field map. Kit: Authorize Kit or enter an API key, then select a form to receive name, email and phone. The Kit form’s confirmation-email settings determine whether subscribers must confirm before joining. Brevo: Connect with a v3 API key and list ID to send name, email and phone. Names split into first and last name; the SMS attribute requires a phone number with its country prefix. ActiveCampaign, ActiveTrail, Benchmark, Drip, E-goi, Ecomail, Elastic Email, Emma, Gist, MailerLite, Mailgun, Omnisend, Sendloop: Send new popup contacts to the connected email platform for follow-up. The integration selector is included in Growth Free; custom-field transfer depends on the selected connector. CM Commerce: Enter the CM Commerce API key and the target list ID in the poptin’s integration settings. The guide lists name, email, phone and message and sends a test lead after setup. Choose the CM Commerce integration when configuring this route. Customer.io: Use the workspace Site ID, API key and segment ID in the Customer.io integration for the poptin. Its guide lists name, email, phone and message and sends a test lead on successful setup. Check the person in the intended workspace and segment. Dotdigital: Enter the Dotdigital API user email, password, regional endpoint and address book ID under the popup’s Email and Integrations settings. After publishing, Poptin sends a test lead to that book. Its guide lists name, email, phone and message as supported fields. EmailOctopus: In EmailOctopus, copy the list ID and the field tag for first name. Enter both with the API key in Poptin. Poptin documents name, email, phone and message; check the actual destination field before using any of them in a template. iContact: Enter the app credentials, account ID, folder ID and list ID for the intended iContact account in Poptin. The list ID can be copied from the list URL. The documented fields are name, email and phone. Mailjet: Copy the Mailjet API key, secret and contact list ID into the poptin’s integration settings and approve the connection. This directs new email signups to the chosen list. Validate any optional answers on the contact before building a segment around them. Moosend: Choose Moosend in the popup’s Email and Integrations settings and enter the API key and list ID. The guide confirms list delivery, but its field note names a different provider. Verify optional fields using a real submission before depending on them. SendFox: Generate a SendFox personal access token, copy the list ID and enter both in the poptin’s integration settings. Save the popup and look for its API test lead in that list. Poptin specifies name and email for this connector. Sendlane: On the individual popup, enter the Sendlane list ID, API key, hash key and subdomain described in Poptin’s setup guide. This route sends signups to that list. Check which credentials your account exposes before following this older setup in a new account. SendPulse: Open Email and Integrations on the poptin, choose SendPulse and supply the account’s API credentials. SendPulse documents choosing the email list that receives new form responses. Verify extra answers in that address book before treating them as campaign variables. AWeber: Authenticate AWeber in the poptin’s Email and Integrations settings, choose the list, approve and save the changes. Poptin’s connector guide names Email and Message as the supported fields. Check a different connector if several structured answers must reach AWeber separately. Campaign Monitor: Copy the API key and the list API ID into the popup’s Email and Integrations settings. Poptin documents sending name, email address, phone and message. The list ID identifies the destination, so a copied client campaign needs its own settings checked. Constant Contact: In the popup editor, open Email and Integrations, add Constant Contact and select the email list for new subscribers. Poptin documents signup delivery there. Its walkthrough does not enumerate optional fields, so inspect a contact before relying on a phone number or a preference. GetResponse: In Email and Integrations, enter the GetResponse API key and the target list’s token. Save the popup and look for Poptin’s test lead in that list. Poptin specifies name and email and explicitly excludes the phone field for this connector. SendGrid: Enter a SendGrid API key and the list ID from Marketing → Contacts in the poptin’s integration settings. Poptin sends a test lead to the selected list and documents name, email and phone. Verify a real form submission separately from the setup test. Klaviyo: Choose a Klaviyo list to receive name, email, phone and custom properties. SMS needs consent and confirmation; invalid phone numbers can prevent list membership. Mailchimp: Connect Mailchimp, select tags and groups, and enable updates for returning contacts if needed. Message and consent values use text merge fields named MESSAGE and CONSENT.

Kit, Brevo, Omnisend, MailerLite, ActiveCampaign, Sender, Ometria, Zoho Marketing Automation: Use a form automation to send widget subscribers to the connected email platform. Ontraport: Personizely lists Ontraport for subscribers acquired through its list-building widgets. Connect the destination and inspect the receiving contact after a form submission. Its public listing does not establish a campaign-enrolment action or a mapping for a particular custom field. CM Commerce: Personizely lists CM Commerce separately as a destination for email subscribers from its popups. Check the actual subscriber list in the commerce account. The vendor listing confirms list growth; supported custom fields and the authentication steps are unspecified. CleverReach: Authorize CleverReach under Settings → Integrations and add the list action to the widget’s subscription form. For recognizing a subscriber who clicks back to the site, Personizely also documents adding a subscriber identifier to mailing links. Check the form action and returning-visitor setup separately. Dotdigital: Connect Dotdigital in Personizely and map the contact fields used by the widget. For recognition on a later visit, Personizely documents adding the Dotdigital contact ID parameter to links in outbound email. A new signup and a click back from a mailing are separate exchanges. Moosend: Connect Moosend in Personizely, then assign the list to the widget’s subscription form. Personizely also documents identifying a returning subscriber from an email link. Sending a new address to a list and recognizing the same reader later require separate setup. SendPulse: Use the SendPulse API ID and secret in Personizely’s integration settings. Edit the widget form and choose the destination list for the subscription action. Authorizing the account and assigning that action to a form are separate steps. SmartrMail: Connect a SmartrMail API token and select the destination list in the widget’s subscription action. Personizely recommends a manually created list for popup signups, separate from the customer list populated by the ecommerce integration. Mailjet: Enter the API key and secret for the correct Mailjet account in Personizely. Assign the selected list to the widget form. Personizely notes that the list label it shows can come from the first part of the email associated with the list. Sendlane: Connect a Sendlane API token, map Personizely custom fields and assign an action to the widget form. The available actions include adding a contact to a list and unsubscribing from a list. Inspect the action on a copied form before publishing it. iContact: Personizely lists iContact as a destination for its list-building widgets. Assign the receiving integration to the signup form and verify the address on the intended iContact list. The provider’s listing does not spell out a mapping for additional fields. GetResponse: Authorize GetResponse from Personizely’s integration settings, then add the GetResponse list action to the subscription form in the widget. That action determines where the new email address lands. The guide confirms list delivery but leaves autoresponder cycle-day handling open. AWeber: Connect the AWeber account in Settings → Integrations, authorize access, then select the AWeber action and list on the widget’s subscription form. The documented outcome is a subscriber on that list. Verify tags separately if the first message depends on one. SendGrid: Connect SendGrid using an API key in Personizely settings, then configure the SendGrid action on the widget’s subscription form and choose the list. This sends signup addresses to Marketing Contacts. Check any additional profile attributes on the receiving contact. Constant Contact: Authorize Constant Contact in Settings → Integrations, then edit the subscription form in the widget and select its action and destination list. Authorization alone does not assign the list. The guide demonstrates adding new contacts and leaves extra field mapping unspecified. Campaign Monitor: Authorize Campaign Monitor in the account integration settings, then select the list in the widget’s subscription form action. New subscribers are added to that list. Confirm the selected client and list for each widget when an agency manages several accounts. Mailchimp: Add a Mailchimp form automation, select a list and map fields explicitly. Choose Add to list for single opt-in or Add with confirmation for double opt-in. Unmapped values are not sent. Klaviyo: Form automation sends standard fields and custom properties. Subscribe to list records consent; Add to list does not. Confirmation follows list settings, and SMS needs form consent.

Postscript, Attentive, Yotpo: Route contacts and supported SMS subscriber information.

Agile CRM, Fireberry, Freshsales, LeadSquared, Nutshell, Salesflare: Route new contacts to sales tools. Keap: Authenticate Keap in the poptin’s integration settings and publish the changes. Poptin lists name, email and phone and sends an API test lead to the contact database. A contact arriving in Keap is the starting point for checking any sales or messaging automation. Pipedrive: Authorize Pipedrive from the popup and save the integration. Name, email and phone are supported; deal name and deal stage are optional settings. Poptin sends a test contact after setup. Inspect the pipeline as well if you enabled deal creation. Zoho CRM: Sign in to Zoho CRM from the popup’s integration settings and authorize access. Poptin documents name, email and phone and sends a test entry to Zoho CRM Leads. Look there first when checking a new enquiry. Salesforce: Authenticate Salesforce under the poptin’s Email and Integrations settings and map the form fields. Poptin requires a mapping for Company. Make sure the form actually collects a usable value before choosing this route for a business enquiry. HubSpot: The CRM route sends name, email and phone, with optional contact updates. HubSpot Forms also sends Message to a chosen form. Both require an email field and account authorization.

Postscript, Attentive, Yotpo: Route contacts and supported SMS subscriber information. HubSpot: Use the form’s Add/update contact automation, map properties and add a list action if needed. Unmapped fields are not sent; editor previews do not run automations.

Crisp, Drift, Intercom, Slack: These messaging services appeared in the authenticated integration selector. Delivery was not tested.

Google Analytics, Segment, Clarity, Mixpanel, Heap, PostHog, Zuko, Klar: Send events or tag sessions with widget and campaign activity; the available flow depends on the connector.

Shopify, Wix, Shoplazza, Webflow, Square, PreProduct: Platform connections support installation, store workflows or contact sync; these are not identical integrations.

Bouncer, reCAPTCHA v3, Clearbit, Albacross, Hyperise: Validate submissions or enrich visitor data for personalization.

Make, Zapier: Use intermediary workflows for additional destinations.

Zapier, Webhooks, SureTriggers: Forward lead data and trigger other workflows.

REST API, Webhooks: Read popup analytics, pause or resume existing popups, and manage contacts through the API. Webhooks forward form submissions to your endpoint. MCP is not yet available.

Install the app and enable its theme embed.

Install through the native Shopify app.

Install the native Poptin app from the Shopify App Store.

Install Personizely: A/B Testing from the Shopify App Store.

No Built for Shopify badge, as confirmed by the site owner.

No Built for Shopify badge, as confirmed by the site owner.

Promote Shopify products with cross-sell widgets.

Product pickers read Shopify collections and variants.

Generate unique codes from an existing Shopify discount.

Use customer tags, login status and order history. Order-history access requires an upgrade.

Use logged-in customer identity and Shopify order history in audience conditions.

Synchronize contacts with Shopify.

Use a cart trigger or a follow-up automation after a Shopify purchase.

The Shopify web pixel records add-to-cart and checkout-start events for triggers and goals.

Target by cart item count, value and products, login status, customer tags and order history. Order-history targeting requires an upgrade.

Target the visitor’s Shopify Market in widgets.

Automatically apply a visible coupon to the Shopify cart when auto-apply is enabled.

Add a product to the cart with a popup button.

Add a Shopify product to the cart through a widget automation.

Covers 1,000 visitors and one website, so no paid plan is needed.

Essential covers 1,000 visitors within its 10,000-visitor allowance.

Basic covers 10,000 visitors on one website. Viewing more pages does not increase the visitor count.

Essential covers 10,000 visitors; pages per visitor do not change the visitor allowance.

Basic stops at 10,000 visitors. Pro covers the required 50,000.

The recorded plans do not establish the traffic allowance and monthly price for this workload.

Basic allows only one website. Pro includes four, so it fits both sites even though their traffic is modest.

Essential covers two sites and 10,000 total visitors, without cross-domain deduplication.

Removing branding requires paid access; Growth is cheaper than Basic and covers 5,000 visitors.

A monthly plan explicitly including branding removal at this traffic level is not established.

Free supports promotional popups, links to an offer and fixed coupon codes. This traffic fits its free allowance.

The monthly plan entitlement for an offer link or fixed coupon at this traffic level is not established.

A/B testing is included in Free. This scenario stays within its 1,000-visitor limit.

Premium includes widget A/B testing and covers 1,000 visitors. Essential URL/theme testing is not popup A/B testing.

Free includes surveys and forms with text answers, choice fields and contact details. It covers basic data and feedback collection; a dedicated scored or branching quiz is not established.

The monthly plan entitlement for both text answers and single-choice questions is not established at this workload.

Free stops at 250 active contacts and 500 emails; Growth includes automations and unlimited emails.

A single-product monthly plan covering automated welcome emails, 500 active contacts and 1,000 sends is not established.

Includes popups, newsletters, audience segments and automated email sequences. Free is limited to 250 contacts and 500 emails; Growth covers 500 contacts, unlimited emails and 5,000 visitors.

A single-product monthly plan covering newsletters, segments and automated sequences for 500 contacts and 5,000 emails is not established.