Customer.io Popup Integrations: Identify People, Map Attributes and Start Journeys
Compare popup tools for Customer.io by workspace, person identifier, segment and the signal that starts a journey after signup.
A trial user gives you the same email on your pricing page and inside the product. Your team wants one person with two meaningful interactions. Before connecting a popup, find out how your Customer.io workspace identifies people and what actually starts the message you have promised.
For a first newsletter, an address in the right segment may be enough. For onboarding, the form might need to update a person already identified by your product. A third campaign may run only when it receives a named event.
Understand the workspace before adding another form
A native Customer.io signup creates or updates a profile and records a form_submit event that can start a journey. You can embed the form on a page without installing the site SDK. The workspace still needs a tracking credential and an enabled JavaScript source.
When comparing external popups, distinguish a person attribute, a segment and an event. A job title belongs on the person. A segment can select that title. If a guide download should trigger an email every time someone requests it, check the actual journey trigger rather than inferring an event from a changed profile.
What should your Customer.io popup send?
| Requirement | What to look for |
|---|---|
| Workspace identity | Check whether email can identify a person in this workspace. Test with someone who already has a product user ID. |
| Credential type | The site ID and tracking key serve a different purpose from an App API key. Supply the combination requested by the connector. |
| Attribute key | Match the spelling and expected type of the attribute already used in segment rules or message personalization. |
| Journey entry | Write down which segment change, event or other trigger is supposed to start the journey and inspect its history. |
5 popup tools with a recorded Customer.io 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; Customer.io and any bridge subscription are separate.
| Popup tool | Score / 100 | Papa pick / month |
|---|---|---|
| Poptin10,000 visitors · 1 domain | 58.03TOPRATED | $25.00Monthly price |
| ConvertFlow100,000 funnel views · 10,000 actions | 48.51TOPRATED | $299.00Monthly price |
| Poper50,000 visitors · 10 sites · Unlimited leads · 5 seats | 45.33TOPRATED | $19.00Monthly price · Promotional price |
| Popupsmart100,000 pageviews · 5 sites · 3,000 emails · 2 users | 43.55TOPRATED | $69.00Monthly price |
| WisepopsUp to 1 million pageviews | 42.91TOPRATED | $599.00Monthly price · Quote required |
Starting points for different needs
Wisepops
Its setup explicitly addresses workspaces that cannot identify people by email. A useful first check when product users and website subscribers overlap.
Poptin
Compare this route for a signup meant to feed a specific segment. Its guide asks for a segment ID and documents the supported contact fields.
Popupsmart
Useful when a form has extra inputs to match to workspace fields. The available choices depend on what is actually in the popup.
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 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.
| 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.
ConvertFlow
Connection to Customer.io
Enter the Customer.io site ID, tracking key and App API key in ConvertFlow’s integrations area. The connection loads account data for segmenting contacts and configuring submission actions. The recorded account placed this CRM route on Prime; check access before building the funnel.
| Editor capability | What it does |
|---|---|
| SMS capture | Forms expose a Phone field and separate SMS Consent control; confirmation can use an SMS subscription code. Delivery depends on the connected service. |
| Phone field | Collect phone numbers with the built-in Phone field. SMS consent is a separate form control. |
| Single choice | Dropdown and radio fields collect one answer; survey answers can use text, images, icons, letters, emoji or colours. |
| Multiple choice | Radio/Checkbox Select fields and the survey Multi-Select setting allow multiple answers. |
| Free text | Text and Paragraph fields collect short or long written responses. Number, Date and Range fields are also available. |
| Consent checkbox | Separate Email Consent, SMS Consent and Privacy Consent controls are available in forms.Email marketing consent · SMS marketing consent · Privacy terms consent |
| Hidden fields | Hidden fields can carry extra values; field settings include prefilled values and URL-parameter mapping. |
| Email capture | The editor provides an Email field, prefilling and submission actions. Contacts can pass to a connected newsletter service or CRM. |
Papa’s take
For teams that need funnel A/B testing and conditional recommendations; simple lead capture can use a lower tier. Free is for building and previewing; going live requires a paid website plan. Integrations, validation and AI also consume a separate action allowance.
Poper
Connection to Customer.io
Connect the Customer.io Site ID and API key in Poper, then match the form inputs to Customer.io attributes. Use an existing attribute key if a journey or segment already reads it. Verify the identity of a returning person before sending another offer.
| 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.
Popupsmart
Connection to Customer.io
Add Customer.io as a connection, supply the Site ID and API key and map the available elements in Match fields. The options depend on the inputs in the popup. Add the question to the design before looking for its value in the integration.
| Editor capability | What it does |
|---|---|
| Phone field | Collect a phone number with a dedicated Phone input. This field alone does not establish consent for SMS marketing. |
| Free text | Use Short Text or Long Input for written answers. The editor also provides name, address and date fields. |
| Single choice | Let visitors choose one answer through Single Choice or Dropdown. |
| Multiple choice | Let visitors select several answers with the Multiple Choice field. |
| Consent checkbox | Add the Notice and Consent element alongside form fields. |
| Hidden fields | Attach a Hidden Input to the submission without displaying another question. |
| Email capture | Collect email addresses through signup forms and pass new contacts to the connected mailing list. |
Papa’s take
The first tier with A/B testing, plus two team members.
Wisepops
Connection to Customer.io
Provide the workspace’s tracking credentials and App API key in the form’s Sync tab. Wisepops exposes an email identifier option for compatible workspaces and documents IP allowlisting for restricted keys. Check the resulting person and attributes in the intended workspace.
| Editor capability | What it does |
|---|---|
| Phone field | The form field menu includes Phone, separately from Email. |
| Free text | The question menu offers single-line Text and Multi-line text fields. |
| Single choice | Radio buttons and a Drop-down list are available in the question menu. |
| Multiple choice | The question menu includes Checkboxes for selecting multiple answers. |
| Hidden fields | Hidden field is available in the question menu for values that visitors do not enter visibly. |
| Email capture | Add an Email field to a form step. The inspected field can block addresses already collected. |
Papa’s take
For teams buying a managed onsite program, rather than just a popup editor. Final scope needs a quote.
How the connection changes the workflow
Example setups using the connections described above.
A known product user requests a demo
Submit from a controlled account that already has an application ID. Look up the original person and compare the updated attributes and segment membership. Also search by the submitted address to catch a second profile.
If a duplicate appears, inspect the workspace identifier model and the connector configuration before changing the message. A sales email can look correct even when the original product history and the new enquiry belong to different profiles.
One person requests two different guides
A marketer wants to send a PDF each time a visitor chooses a guide. A field containing the last requested title can personalize a message. Updating it twice may still leave only the latest value on the profile.
Submit two requests using one address and inspect the journey history. If delivery depends on a repeatable event, verify that the route emits it or add a separately documented event step. Use a segment-based route for journeys whose intended start is joining that audience.
Head-to-head comparisons for Customer.io users
These comparisons cover the popup tools as a whole. Use them to compare forms, targeting and costs alongside the connection details above.
Popupsmart vs Poptin
Compare field collection and campaign pricing when an existing Customer.io segment needs more than a new address.
Poptin vs Wisepops
Compare the signup experience after confirming which workspace identifier and segment each form can use.
ConvertFlow vs Poper
Compare qualifying a visitor across several steps with mapping answers from an individual popup to Customer.io attributes.
Poptin vs Poper
For readers requesting two guides, compare adding a person to a chosen segment with writing the latest interest to a profile attribute. Check which change starts the next email.
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.
- Verify the workspace and identifier using an existing product account.
- Compare a form answer with the attribute used by the target segment.
- Find the exact entry that started the journey.
- Request a second asset and inspect whether another delivery was scheduled.
Common questions
Do all these tools need the same keys?
No. Wisepops and ConvertFlow document both tracking and App API credentials; other routes describe a different combination. Use the credential types for the selected connector.
Does updating a profile generate my custom event?
A profile update establishes the person’s new attributes. For an event-triggered campaign, inspect the event stream for the specific event and its properties.
When is a native Customer.io form worth trying first?
Try it first if you need a repeatable form_submit event to deliver a guide. An embedded or hosted form can do that even on a site without the Customer.io SDK. Compare an external popup if its targeting or question flow is important, and check which signal its connector sends.