Poptin vs Claspo.
A first newsletter or a longer signup form?

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.32)

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

Any input field can be set to hidden.

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

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

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

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

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.26) · Losing slices (+0.26)

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)

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.56) · Several sites (+0.56) · Client portfolio (+0.56)

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

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

HTTP API (+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: 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.

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.

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.

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

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

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

Google Sheets: A dedicated setup guide covers spreadsheet delivery.

Make, Zapier: Use intermediary workflows for additional destinations.

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.

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.

A native Shopify app is available.

Install the native Poptin app 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.

Add the Shopify Products component to a widget.

Map customer fields and metafields through the Shopify integration.

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

Map form fields to Shopify customer fields.

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

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

Add a product to the cart with a popup button.

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

Free covers 2,000 pageviews on one Shopify site.

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

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

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

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

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

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

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

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

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

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

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

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

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.