Note: Integrations must be set up by a Toolkit admin. To connect any of the integrations below, contact support and let us know which integration you'd like added to your account.

Connecting and Managing Integrations

Popup integrates with popular email marketing and CRM platforms so subscriber data flows directly into your existing tools.

Connecting an Integration

1. In your Popup dashboard, go to the Integrations tab.
2. Find the service you want to connect (e.g. Mailchimp, ActiveCampaign, Drip).
3. Click Connect and follow the authorization steps for that service (API key, OAuth, etc.).
4. Once connected, the integration appears with a green status indicator.

Disconnecting an Integration

1. Go to the Integrations tab.
2. Find the connected service.
3. Click the settings icon or Disconnect button.
4. Confirm the disconnection. Existing subscribers already sent to that service are not affected.

Default Settings

When you connect an integration, Popup applies default settings for how new subscribers are added:

• Default List/Group -- Choose which list or group new subscribers are added to. This applies to all widgets unless overridden at the widget level.
• Double Opt-In -- Some integrations support toggling double opt-in on or off from the default settings.
• Tags -- Set default tags that are automatically applied to every new subscriber.

You can override these defaults on a per-widget basis in the widget editor's submit action settings.

Custom Field Mapping

Custom field mapping lets you send additional form data (phone number, company name, etc.) to your connected integration.

Site-Wide Mapping

1. Go to Integrations and click the settings icon next to your connected service.
2. In the Field Mapping section, map Popup form fields to your integration's custom fields.
3. These mappings apply to all widgets by default.

Widget-Specific Mapping

If you need different field mappings for different widgets, use unique field names in each widget's form fields. When you assign a unique field name in the widget editor, Popup treats it as a separate mapping that does not inherit the site-wide default.

Tip: Use descriptive, unique field names (e.g. phone_homepage, phone_exit_popup) to keep widget-specific mappings clean and avoid conflicts with site-wide mappings.

Need more help?

If you've worked through this and still need a hand, contact support -- we'll dig in with you.