Configure ActiveCampaign as a Source in your Pipeline

Perform the following steps to configure your ActiveCampaign Source:

1. Click Pipelines in the Navigation Bar.

2. Click + Create Pipeline in the Pipelines List View.

3. On the Select Source Type page, select ActiveCampaign.

4. On the Select Destination Type page, select the type of Destination you want to use.

5. On the Select Pipeline Type page, click Edge, and then click Continue.

   

   This page appears only if the selected Destination type is supported in Edge and your Team has an existing ActiveCampaign Pipeline with the same Destination type. Otherwise, you can proceed to create an Edge Pipeline.

6. In the Configure Source screen, specify the following:

   

   • Source Name: A unique name for your Source, not exceeding 255 characters. For example, ActiveCampaign Source.

   • In the Connect to ActiveCampaign section, specify the following:

     • API Token: The API key that you copied from the Developer page of your ActiveCampaign account.

     • Account Name: The account name part of your API URL. For example, if your API URL is https://youraccountname.api-us1.com, enter youraccountname. Do not include the domain or the API path.

7. Click Test & Continue to test the connection to your ActiveCampaign Source. Once the test is successful, you can proceed to set up your Destination.

Data Replication

Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline.

For the Contacts and Deals objects, Hevo ingests new and updated records in each Pipeline run, as per the sync frequency. Changes are identified using the date on which a record was last updated. In each run, Hevo also ingests again the records updated on the day before the last saved update date, to avoid missing changes.

For all the other objects, Hevo ingests the entire data during each Pipeline run.

You can resync only the parent objects. When you resync a parent object, Hevo also resyncs its child objects.

ActiveCampaign limits API requests to 5 requests per second per account. If this limit is exceeded, a rate limit exception occurs. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.

Note: The Email Activities object uses the Append load mode, and all the other objects use the Merge load mode. You cannot change the load mode of an object. As Hevo reads all the email activities in each run and the object has no primary key, its Destination table contains the same email activities again after each run.

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.

Click to view ERD

The primary key of most objects is id. The following objects use a different primary key:

• Custom Fields: custom_field_id. Custom Field Relations: custom_field_id and relation_id.

• Custom Object Schemas: custom_object_schema_id. Its child objects use custom_object_schema_id with field_id or relationship_id.

• Account Custom Field Options and Deal Custom Field Options: the ID of the custom field and option.

• Pipeline Deal Stages: deal_group_id and deal_stage_id.

• Form Actions and Form Cfields: row_key, a key that Hevo generates from the content of each record.

• Email Activities: no primary key.

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline: