Personizely vs Claspo.
Remember the visitor or coordinate the offers?

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

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

Consent checkbox (+0.16) · Privacy terms consent (+0.16)

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

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

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

Logic (+0.16) · Step logic (+0.32)

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

Validation (+0.16) · Email typo check (+0.32)

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

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)

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

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

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

Workspaces (+0.56) · Several sites (+0.56)

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

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

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.

Kit: Use Claspo’s webhook integration to send submissions to a Kit form or sequence. The destination ID and request body specify where the subscriber goes and which fields are included. ActiveCampaign, MailBluster, MailerLite, MailWizz, Mautic, Newsletter2Go, Omnisend, Brevo, Zoho Campaigns, Acumbamail, VBOUT, Act-On, Userlist: Send widget submissions to an email platform through its documented integration route. Field mapping can include form answers and submission context where the receiving connector supports those values. beehiiv: Connect a beehiiv API key in the widget integration and select the publication. Map the required subscriber data and use static fields for information shared by everyone submitting that widget. Create the receiving fields in the correct publication first. CleverReach: Connect CleverReach at the widget’s integration step and choose the receiving group. Map the required email field and any additional supported inputs; fixed values can identify the particular signup offer. Inspect both recipient activation and field values in CleverReach. Dotdigital: Connect the widget to Dotdigital, choose the address book and map the contact inputs. System values such as site language and fixed campaign labels can go into separate Dotdigital fields. An address book membership alone does not preserve a visitor’s answer. Iterable: Connect the widget to Iterable, choose the subscriber list and map email plus any supported contact fields. Fixed field values can identify the campaign or language. Check the type of each receiving field when extending an existing Iterable profile. SendPulse: Choose SendPulse in the widget’s integrations, authorize with the account credentials and select the mailing list. Map each input to a SendPulse field and add static values if needed. A fixed language value is useful for a form published on only one language version of a site. SendFox: Claspo documents a webhook setup for SendFox. Configure the contacts endpoint and authorize the request with the SendFox token; map the required email and supported optional parameters in the request. If the signup belongs to one list, verify that membership after submitting. Constant Contact: Authorize Constant Contact on the widget’s Integrations step and select a list. Email is required. Map contact inputs such as name or phone, optionally add browser or language data, and use a static value when every signup should carry the same offer name. GetResponse: Connect the API key, choose the mailing list and map the required email address. Claspo can also transfer widget answers, system fields and fixed values. Its guide points to the list’s API subscription settings for signups that require a confirmation message. SendGrid: Create a restricted SendGrid key with Marketing access as specified in Claspo’s guide, then choose the list in the widget. Map email and any other supported form fields; static values can label the source. This lets a team identify the popup offer on the marketing contact. Klaviyo: Select a list and map each widget’s fields, including custom properties. Email and SMS subscription requests run separately and follow the list’s opt-in settings. Mailchimp: Authorize Mailchimp, choose an audience and map fields; email is required. Select existing groups, add fixed values and enable opt-in confirmation as needed. A Test button checks the setup.

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

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.

SalesDrive, FluentCRM: Route form submissions into your CRM. Pipedrive: Connect the Pipedrive API token, include Name in the widget and map the supported inputs. You can also create a deal linked to the contact and use a selected component as the deal title. Claspo’s guide excludes transfer to custom Pipedrive fields. Zoho CRM: Authorize Claspo, choose the Zoho CRM module in the widget integration and map the inputs. The guide names Leads and Contacts and requires last_name. It also supports mapping system values and supplying a fixed field such as the enquiry source. Salesforce: Authorize Salesforce from the widget’s integrations and configure the destination and mapped fields. Claspo requires last name in its setup. Map a real surname field for a sales enquiry, then check that the remaining contact and campaign values reach the expected CRM fields. HubSpot: Select a static list and map widget, system or fixed values to contact fields. Email is required; contacts use single opt-in. Active lists are not supported.

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.

Google Analytics, Meta Pixel, Shopify: Track campaign events and lead events; Shopify documentation covers customer field mapping and metafields.

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

Google Analytics, Meta Pixel, Shopify: Track campaign events and lead events; Shopify documentation covers customer field mapping and metafields.

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

Google Sheets: A dedicated setup guide covers spreadsheet delivery.

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

Zapier, Make, Pabbly, Activepieces, Boost.space, Webhooks: The inspected Webhook setup supports HTTPS POST, authentication, custom headers and a JSON body with submission and prize fields. Zapier also appears in the connection menu.

Install through the native Shopify app.

A native Shopify app is available.

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

A native app is available in 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.

Add the Shopify Products component to a widget.

Product pickers read Shopify collections and variants.

Generate unique codes from an existing Shopify discount.

Map customer fields and metafields through the Shopify integration.

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

Synchronize contacts with Shopify.

Map form fields to Shopify customer fields.

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

Target the visitor’s Shopify Market in widgets.

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

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

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

Free covers 2,000 pageviews on one Shopify site.

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

60,000 pageviews exceed the 50K tier; use 100K.

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

The 100K tier covers 100,000 pageviews on one site.

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

Pro 100 covers three websites and 100,000 combined pageviews. The $52 monthly equivalent requires annual billing.

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

The first paid Shopify tier removes branding and covers 2,000 pageviews.

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

A promotional popup with an offer link fits the free plan on one site at 2,000 pageviews.

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

All popup features, including A/B testing, are included on the free Shopify tier; 2,000 pageviews fit.

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

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

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

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

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

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