PopupBuilder.io
Poptin / Product guide

Poptin Integrations 2026

Visit Poptin

Use Poptin's integration directory to find a route, then verify the data contract. These guides and checks cover direct email and CRM connectors, Shopify and BigCommerce installation, Zapier or Make automation, field mapping, consent and failed-delivery handling.

Vendor documentation · checked 2026-09-06

Integration options and setup checks

Choose the connection for your workflow, then verify what reaches the destination. These are source-based findings; the checks below are our evaluation guidance, not hands-on test results.

Mailchimp

Poptin's help article documents OAuth or API-key connection, Audience Groups and Tags, plus Name, Email, Phone and Message fields.

Availability:
The article was updated 15 November 2024. It says CONSENT can use a text merge tag and warns that OAuth connections across domains can replace a previous connection.
Before you rely on it:
Use a fresh address, keep only email required in the Audience test, and inspect fields, tags, group and consent after delivery.
Read vendor documentation ↗

Kit

The current guide sends each new lead to a selected Kit form and documents Name, Email and Phone as the three synced fields.

Availability:
OAuth and API-key routes are documented. Kit double opt-in is enabled by default on the selected form.
Before you rely on it:
Verify the form, three fields and confirmation state; add a fourth-field requirement to the test because the guide does not document one.
Read vendor documentation ↗

Salesforce

The guide maps name, email, phone and message, requires a value for Salesforce Company and creates an API test lead after approval.

Availability:
The article was updated 15 November 2024 and says Salesforce API access depends on edition; Professional may require separately purchased API access.
Before you rely on it:
Map Company, enable the Description field when using Message, confirm API access and inspect the created test lead.
Read vendor documentation ↗

Other native email and CRM destinations

The current directory lists Klaviyo, Omnisend, ActiveCampaign, HubSpot, Pipedrive, Zoho CRM, Keap and other destinations.

Availability:
Directory listing establishes a connection route, not every field, update action or plan condition.
Before you rely on it:
Confirm whether the workflow creates or updates a record, then inspect required properties, ownership, consent and duplicates.
Read vendor documentation ↗

Website platforms

The directory lists WordPress, Shopify, Wix, Webflow, Squarespace, Woo and BigCommerce. The BigCommerce marketplace lists single-click and multi-storefront compatibility.

Availability:
Platform installation and commerce data are separate. A visible popup does not prove that a cart, order or customer condition is populated.
Before you rely on it:
Verify script installation first, then exercise the exact commerce rule with a test cart or customer state.
Read vendor documentation ↗

Zapier, Make and webhooks

Zapier's current directory exposes a Poptin New Lead instant trigger. Poptin separately documents Make and generic webhook routes.

Availability:
The observed Zapier surface establishes a Poptin trigger; the destination action, fields, task usage and separate automation cost depend on the workflow.
Before you rely on it:
Test one successful and one deliberately incomplete payload, then configure an owner and alert for failed delivery.
Read vendor documentation ↗

Built-in email versus an external destination

The product now offers its own email workflows as well as external marketing connectors.

Availability:
Check the selected Emails & Poptins allowance if sending inside Poptin.
Before you rely on it:
Choose one intended follow-up path and test it. Running both paths without coordination can send duplicate messages.
Read vendor documentation ↗

Suggested setup checks

Follow one Poptin lead from display to delivery

Use your actual campaign and destination to separate installation, capture, transport and follow-up checks.

  1. Write the data contract

    List the destination, record action, required fields, consent state, tags, owner and expected follow-up.

  2. Verify campaign eligibility

    Confirm the script loads and the intended page, audience and commerce conditions show the campaign.

  3. Submit a unique test lead

    Use a fresh address, complete every field and inspect the destination record instead of relying on the onsite success message.

  4. Test duplicates and failure

    Resubmit an existing contact and deliberately break one mapping so you can see how updates and errors are handled.

  5. Assign monitoring

    Record who owns credentials, failed-delivery alerts, destination changes and a periodic end-to-end test.

Browse Poptin guides

4 of 4 guides available

Questions before you decide

Frequently asked questions

Which email tools are listed in Poptin’s integration directory?

The directory lists Klaviyo, Mailchimp, Kit, Omnisend and ActiveCampaign among its email destinations. Treat that as connector availability, then verify authentication, destination list and the fields required by your campaign. The directory alone does not establish all plan or field restrictions.

Can Poptin connect through Make or Zapier?

Yes. Poptin lists both services, and Zapier currently exposes an instant New Lead trigger for a Poptin conversion. Confirm the destination action, available fields, task usage and separate automation cost, then test both successful and failed delivery.

Does installing Poptin on a platform enable every commerce rule?

No. Poptin lists website platforms and BigCommerce lists its app as single-click and multi-storefront compatible, while Poptin documents commerce conditions separately. Verify script display first, then exercise the exact cart, order or customer rule with a test state.

What should I test before sending Poptin leads to a CRM?

Check whether the workflow creates a contact, updates an existing record or assigns an owner, then inspect a fresh test record. Verify required fields, consent, duplicate behavior and failure alerts. A CRM logo in the directory does not specify every supported action.

Which fields does Poptin send to Mailchimp?

The Poptin guide documents Name, Email, Phone and Message. It also describes Groups and Tags, plus a text merge tag for the consent checkbox. The guide warns that a Mailchimp OAuth connection on another domain can replace a previous connection, so test the intended domain and Audience with a fresh address.

Which fields does Poptin send to Kit?

The current Poptin guide documents Name, Email and Phone sent to the selected Kit form. It also notes that Kit double opt-in is enabled by default on the form. Test the confirmation state and treat any additional field as an unverified requirement.

What does the Poptin Salesforce integration require?

Poptin’s guide requires a value mapped to Salesforce Company and documents name, email, phone and message fields. It says API access depends on the Salesforce edition and that the Description field may need to be enabled. Confirm those conditions and inspect the API test lead after approval.