SendPulse Popup Integrations: Address Books, Variables and Email Confirmation
Compare four ways to send popup leads into a SendPulse email address book. Check variable mapping, form-level routing and subscriber confirmation.
A SendPulse account can power an email newsletter and a chatbot for the same store. A visitor entering an email in a popup has completed one of those journeys. Plan the destination as an email address book first; a later invitation to join a chatbot is a separate interaction.
Write the first email before picking the popup. If it says “Here are this week’s events in Bristol,” both the address and the city have to arrive. If it is the same bulletin for everyone, list delivery may be all the editor needs.
What should appear in the address book?
SendPulse’s own popup builder supports email capture and a confirmation option. Use the native form as a reference for the promised success message and the state of a new subscriber. Third-party tools bring different display controls and their own field mapping.
A subscriber’s city can go into a variable. A store code known in advance can be sent as a fixed value. Putting a whole city into another address book is useful when it truly has a separate mailing schedule; otherwise, a variable can keep one audience easier to manage.
What should your SendPulse popup send?
| Requirement | What to look for |
|---|---|
| Address book | Open the exact mailing list selected in the popup. A new contact in another part of SendPulse cannot establish delivery to this audience. |
| Variable | Match the visitor’s answer to the variable used in the template, including its expected type and spelling. |
| Confirmation | Check what a subscriber sees between submitting the form and confirming their email. Measure the confirmed audience separately. |
4 popup tools with a recorded SendPulse connection
Sorted by Popup Papa’s absolute capability score out of 100. This measures the overall toolkit, not the depth of this one integration. Prices are the directory’s Papa pick plans, not guaranteed minimum connector prices. Check the connector tier and capacity before buying; SendPulse and any bridge subscription are separate.
| Popup tool | Score / 100 | Papa pick / month |
|---|---|---|
| Poptin10,000 visitors · 1 domain | 58.03TOPRATED | $25.00Monthly price |
| Personizely10,000 visitors · 10 sites | 49.95TOPRATED | $59.00Monthly price |
| Poper50,000 visitors · 10 sites · Unlimited leads · 5 seats | 45.33TOPRATED | $19.00Monthly price · Promotional price |
| Claspo50,000 pageviews · 1 site | 42.39TOPRATED | $39.00Monthly price |
Starting points for different needs
Poptin
A practical route for straightforward list delivery. SendPulse documents connecting the API credentials and choosing the list in Poptin.
Claspo
Try it for localized forms that need a customer-entered value and a fixed campaign identifier on the same record.
Personizely
Useful for a team reusing one connected account across several widgets. The subscription action on each widget selects its list.
How each connection works
Connection details and plan conditions are shown below. The field tables describe the popup editor; supported transfer depends on the connector.
Poptin
Connection to 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.
| Editor capability | What it does |
|---|---|
| Single choice | The inspected field offers Radio and Single-select display modes, with editable option labels and values. This confirms one selected answer; it does not establish a scored quiz or rating scale. |
| Email double opt-in | Choose a double opt-in setting for the popup or inherit the account setting. |
| Phone field | Collect a phone number in a dedicated contact field. |
| Free text | Collect a written response with the Message field. |
| Consent checkbox | Add an Email Consent checkbox alongside the signup fields. |
| Hidden fields | Set an input field to Hidden instead of displaying it to visitors. |
| Email capture | Collect email addresses through signup forms and pass new contacts to the connected mailing list. |
Papa’s take
Unbranded popup campaigns with a practical visitor allowance. Email bundles are separate.
Personizely
Connection to 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.
| Editor capability | What it does |
|---|---|
| Phone field | The form editor offers a Phone field. This alone does not establish SMS subscription or delivery. |
| Free text | Custom fields include text and textarea for free-text answers. |
| Single choice | Custom fields include select and radio controls for one answer. |
| Multiple choice | A multiple-choice custom field type is available. |
| Consent checkbox | Separate email marketing, SMS marketing and privacy consent fields are available.Email marketing consent · SMS marketing consent · Privacy terms consent |
| Email capture | Collect email addresses through signup forms and pass new contacts to the connected mailing list. |
Papa’s take
Adds widget A/B testing and personalization; Essential has a different testing scope.
Poper
Connection to SendPulse
Connect the SendPulse account from the popup editor with its API credentials. Choose the list and map the popup fields to the subscriber attributes needed for follow-up. A separate field for the offer source lets several popups share an address book.
| Editor capability | What it does |
|---|---|
| Phone field | Popup and standalone form editors offer a Phone field. This establishes number collection, not SMS consent or message delivery. |
| Free text | Standalone forms and surveys offer Short Text and Long Text fields for written answers. |
| Single choice | Dropdown and Radio controls are available in the popup, form and survey editors. |
| Multiple choice | The form and survey logic library offers a Checkbox Group for multiple choices. |
| Consent checkbox | The standalone form and survey libraries include a Terms control; popup forms offer a Checkbox element. Consent wording needs configuring for the intended use. |
| Hidden fields | The popup integration step offers hidden inputs. Forms and surveys also expose Hidden fields and a dedicated settings section. |
| Email capture | The AI-generated popup contains an email field. The Plinko editor also has an email gate before play. |
Papa’s take
Pro adds tests, games and integrations. The inspected monthly price is a promotion; confirm the traffic definition and ongoing rate before paying.
Claspo
Connection to 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.
| Editor capability | What it does |
|---|---|
| Phone field | The editor provides a Phone field. This establishes phone collection, not SMS marketing consent or delivery. |
| Free text | Text input and Text area collect short and long written answers; Calendar and Date fields are also available. |
| Single choice | Dropdown and Radio components collect a single selected answer. |
| Consent checkbox | The component library includes Checkbox and Data processing and terms of use controls. |
| Hidden fields | Attach hidden fields to the widget submission through the editor’s hidden-field settings. |
| Email capture | The editor provides an Email field and a separate signup page in the inspected game template. |
Papa’s take
Removes branding and leaves room for a growing store. Shopify pricing is used here. Team invitations are documented for the web app, but its help center excludes Shopify accounts.
How the connection changes the workflow
Example setups using the connections described above.
One mailing, several local editions
Ask readers to choose their local edition. Map the answer to the address-book variable used by the campaign. Give the signup a separate source value if the team also wants to know which website collected it.
Submit two neighbouring cities. Preview the actual edition for both addresses and for a subscriber with no city. That third case is what your team will see when someone joins through a simpler form.
Keep email signup separate from a messenger offer
Promise the newsletter on the email form. If the thank-you screen also offers a messaging channel, measure clicks and completed messenger subscriptions separately from contacts added to the address book.
Check a visitor who leaves immediately after submitting the email. They should still receive the intended confirmation or newsletter follow-up. Avoid treating a missing chatbot subscription as a failed email transfer.
Head-to-head comparisons for SendPulse users
These comparisons cover the popup tools as a whole. Use them to compare forms, targeting and costs alongside the connection details above.
Poptin vs Personizely
Compare selecting a SendPulse list in Poptin with reusing an authorized Personizely account across several widget actions.
Personizely vs Claspo
Compare routing each widget to its list with passing a fixed campaign value alongside the visitor’s own answer.
Poper vs Claspo
For a local edition, compare mapping each reader’s city in Poper with adding a fixed source in Claspo alongside the entered address and preference.
Check the whole journey before launch
Use a small test campaign with addresses you control. Check the receiving record and the follow-up, not only the popup’s success message.
- Confirm which address book the published popup targets.
- Inspect the city or other variable on an actual contact.
- Check the pending and confirmed journeys under the intended settings.
- Compare email subscribers and messaging-channel subscribers separately.
Common questions
Which credentials does the Poptin route use?
SendPulse’s own instructions specify an API key and secret in the popup integration, followed by email list selection.
Can I add the same source to every signup?
Claspo documents static fields. Supply the offer name once in the integration and map the reader’s own answers separately.
Will an email signup subscribe someone to a chatbot?
The routes here deliver email contacts. A messaging subscription needs the corresponding channel interaction and its own verification.