Skip to main content

For admins

Integrations

Integrations connect Better Email to your ESP. They make it possible to export finished campaigns with the correct merge tags, segmentation logic, and platform-specific code for the target system.

If you want your own system to call Better Email directly, use the Better Email API. API docs are separate from ESP integration guides.

Guides by ESP​

Salesforce Marketing CloudPerformance dataKlaviyoPerformance dataBrazePerformance dataHubSpotPerformance dataIterablePerformance dataBloomreach EngagementPerformance dataAgillicPerformance dataMailchimpPerformance dataDynamics 365 Customer Insights - JourneysPerformance dataOracle EloquaPerformance dataAdobe Campaign ClassicAdobe Campaign v8Adobe Journey OptimizerActiveCampaignCustomer.ioSendGridSailthruSAS CI 360Custom HTML export

If the ESP you use isn't listed, contact us. We can help you choose the right workflow or tell you whether a dedicated integration is available. Access to integrations is managed with groups and access control.

Other integrations​

These bring content in rather than send Campaigns out. Cloudinary and Bynder let editors pick images from your image library in any image field, and SFMC Content Builder does the same in Campaigns on a Salesforce Marketing Cloud Destination. Betty's connectors let her build Campaigns from Figma, Miro, monday.com and Trello, and your team can ask her for one in Slack. You can also use Better Email from your own AI client.

CloudinaryImagesBynderImagesSFMC Content BuilderImagesFigmaBetty connectorMiroBetty connectormonday.comBetty connectorTrelloBetty connectorSlackBetty connectorYour AI clientMCP

What integrations are used for​

Integrations affect more than export. They can also shape:

  • merge tag output
  • segmentation rules
  • recipient field syncing
  • feed and personalization workflows

That means integration setup is foundational, not just a final-step task.

Who can manage integrations​

note

Only users with the Admin role can create, edit, and authenticate integrations.

Editors and designers only see the integrations they have access to.

Adding an integration​

The high-level flow is:

  1. Go to Integrations.
  2. Create a new integration and choose the correct type.
  3. Enable it.
  4. Complete any required credentials or authentication steps.
  5. Save and confirm the connection is active.

Integration picker showing the ESPs and custom export options available in Better Email

Some integrations use API keys. Others use OAuth and will redirect you to the ESP for approval.

Some plans include a set number of integrations, counted by Destination. Better Email refuses a new integration or Destination past that number. The message tells you to ask the agency that manages your Organization to upgrade the plan, or to contact Better Email if no agency does.

Integration access and visibility​

note

Enterprise-only feature: Integration access restrictions and group-based access control are available on Enterprise plans.

If integration access controls are enabled in your workspace, admins can limit an integration to specific users or groups.

This matters because integration visibility affects more than the integration list itself. Users only see integrations they have access to when:

  • exporting campaigns
  • choosing an integration for segments
  • choosing an integration for recipient fields
  • syncing recipient fields from an integration

If a user does not have access to an integration, they also will not see segments or recipient fields tied to that integration.

Exporting a campaign​

Once an integration is active, users can export campaigns directly from Better Email.

During export, Better Email renders the email with:

  • the current content and settings
  • merge tags
  • segmentation logic
  • integration-specific output rules

If the integration supports updates, repeated exports can update the same asset in the ESP instead of creating duplicates.

Best practices​

  • Keep integration names clear so marketers know which one to export to.
  • Use access controls if different teams work in different ESPs or business units.
  • Verify recipient fields and segments after connecting a new integration.
  • Test exports early when setting up a new workflow, not right before a launch.