Skip to main content

​
Summary

Mailchimp appears in TruAgents as one of the supported contact-data source paths for bringing external audience data into the platform. The current app suggests this is a connected provider workflow with authentication and direct contact transfer, not a separate file-upload path.

​
Who this is for

Technical admins and operators connecting external systems to TruAgents.

​
Where it fits in the product

  • Contacts → Data Sources
  • contact import, mapping, and sync workflows

​
What this page should eventually cover

  • what kinds of Mailchimp data are expected to come into TruAgents
  • what authentication or account access is required
  • how to map imported fields into usable contact data
  • how to verify that imported contacts are ready for segmentation and campaigns

​
Practical workflow

The current Mailchimp path appears to be:
  1. create or reuse a Mailchimp integration
  2. create or reuse the associated data source
  3. authenticate with Mailchimp
  4. transfer contacts into TruAgents
  5. review the imported records before using them operationally
The default data-source setup also suggests the integration expects conventional Mailchimp-style fields such as email address and full name.

​
What to validate

  • whether the integration is authenticated
  • whether the expected audience records came across
  • whether key identity fields landed in usable contact fields
  • whether the resulting contacts are ready for segments and campaigns

​
Common mistakes

  • assuming direct transfer means no validation is needed
  • treating imported audience size as proof of import quality
  • using Mailchimp contacts in campaigns before checking a sample of real records