ePrivacy and GPDR Cookie Consent by Cookie Consent Skip to main content

Loader ActiveCampaign

ActiveCampaign, known for its strong email marketing capabilities, offers a user-friendly interface for creating and executing targeted campaigns with precise audience segmentation. One notable use case involves using the loader feature to effortlessly import and send a batch of emails into ActiveCampaign, streamlining the process of engaging with a wide audience.

Business value in CDP

When utilizing the ActiveCampaign loader within a CDP, you can enhance its business value by enriching customer profiles with additional data. This can include their purchase history, providing insights into previous transactions and product preferences. Furthermore, incorporating behavioral data allows for more targeted segmentation based on website activity and engagement with previous email campaigns. Demographic information such as age, gender, and location can also be integrated to personalize further and tailor email campaigns, resulting in more effective customer engagement and higher conversion rates.

Steps for setting up ActiveCampaign Loader

Follow this step-by-step guide to configure the component:

  1. The first step is to set up the loader within Meiro Integration by following the instructions given in this article.
  2. Set up the loader as a destination in CDP. Read here. 
  3. Continue with exporting your segmented customer profiles. Refer to this article.

Setting up the loader in MI

For setting ActiveCampaign as a destination within Meiro Integration, use the ActiveCampaign loader component.

Data In/Data Out

 

 

 

 

 

 

Data In 

Loader requires contacts.csv file in directory /data/in/tables/contacts.csv.

 

The CSV file /data/in/tables/contacts.csv must have a header consisting of the required field email and the optional fields first_name, last_name, and phone.

 


For example:

 

email,phone
foo@bar.com,
jane@doe.com,123456789
Data Out

After each successful export, the loader returns information about the processed audience.
The output includes the Audience ID of the audience that was created or updated in the connected platform.

 

This information can be used for automation or integration purposes, allowing the Audience ID to be automatically populated in CDP and removing the need for manual updates.

 

Example Output:

 

{
  "audience_name": "Summer Campaign 2025",
  "audience_id": "1234567890",
  "status": "success"
}

  • If the Audience ID is provided in the configuration, the loader updates the existing audience with that ID.

  • If the Audience ID is not provided, a new audience is created using the Audience Name, and the corresponding Audience ID is returned in the output.

Learn more: about folder structure in configuration here.

Parameters

URL 

(required)

  Base URL that is specific to your account.

Credentials

API KEY 

(required)

 Private API key.
Contact list
Contact list ID The ID of the contact list where contacts from the export.ndjson file will be imported.
Contact list name  Name of new contact list.
User group ID The ID of the user group. It will be associated with the contact list and enable to see the contact list in the UI.
User group name Name of a new user group.
Behavior
  • Set contact_list.id to upload contacts to the existing contact list.
  • To create a new contact list, set contact_list.name and at least one of contact_list.user_group_id or contact_list.user_group_name.
  • Use contact_list.user_group_id to use the existing user group or contact_list.user_group_name to create a new user group.
No Comments
Back to top