Export ActiveCampaign Contacts with Custom Fields - Skyvia

ActiveCampaign: Exporting Contact Custom Field Values

Overview

You can export ActiveCampaign contacts with a specific custom field value to a CSV file using the Advanced Task Editor Mode in a Skyvia Export integration.

Steps

  1. Create a new Export integration.
  2. Open it and switch to Advanced Task Editor Mode.
  3. Add an Execute Command action.
  4. Use the following query, replacing your field id with the actual custom field ID value from your ActiveCampaign connection:
SELECT Email, CreatedDate, Value
FROM (SELECT ContactId, Value
      FROM ContactCustomFieldValues
      WHERE FieldId = your field id) AS cfv
JOIN
     (SELECT Id, Email, CreatedDate
      FROM Contacts) AS ct
ON cfv.ContactId = ct.Id
GROUP BY Value

Note: Value contains the custom field value. Email serves as the unique contact identifier.

Result

The exported CSV will include:

  • Contact email
  • Contact created date
  • Value of the custom field

    • Related Articles

    • Resolving ActiveCampaign Backup Errors (403 Forbidden)

      Overview Sometimes, when running an ActiveCampaign backup, users may encounter the following error: The remote server returned an error: (403) Forbidden This happens when the ActiveCampaign API receives too many requests in a short period, especially ...

    • Brevo Attributes Field: Mapping Rules and Override Behavior

      Overview When working with Brevo contacts, the fields Attributes_FirstName, Attributes_LastName, and Attributes_Phone are provided as standalone fields for convenience, as they are universal to all users. However, for adding or updating custom ...

    • Working with Mailchimp Custom Merge Fields

      Overview In some scenarios, you may encounter difficulties accessing custom Mailchimp fields in Skyvia. This article explains how to configure the Merge Fields Behavior setting to make custom (merge) fields available in your integration. Steps to ...

    • Replication: Schema Validation Failed (Absent Columns / Redundant Columns)

      Overview If you encounter the following errors in an integration, it means the schema of your data source no longer matches the schema Skyvia has cached: "Integration failed: Table 'TableName' schema validation failed: Absent columns: 'FieldName1', ...

    • HubSpot: 414 Request-URI Too Large / 400 Request Header or Cookie Too Large

      Overview The errors 414 Request-URI Too Large and 400 Request Header or Cookie Too Large are returned by the HubSpot API when a single API request exceeds the maximum allowed size. This typically occurs when querying HubSpot objects that have a large ...