Send Attributed Leads to ActiveCampaign

Able sends attributed leads to ActiveCampaign as contacts, allowing to quickly integrate any website form with ActiveCampaign API.

Able CDP ActiveCampaign API integration simplifies adding and updating contacts in ActiveCampaign by providing an interface, linking Able form tracking with server-side ActiveCampaign API.

To send attributed forms to ActiveCampaign from Able:

  1. Locate API URL and Key in ActiveCampaign Settings in the Developer section.
  2. Open API Credentials in the Formsable. Add a new credential, copying settings from the ActiveCampaign.
  3. Open Funnel tab, press Add Outbound, select the ActiveCampaign credential and choose desired event type. For example, Lead or Contact. Press Save.

Able will automatically map fields in the tracked forms to ActiveCampaign. In addition to standard field names such as firstName and lastName, any additional form fields will be mapped automatically provided ActiveCampaign has Custom Fields with the same names.

This integration only creates and updates ActiveCampaign contacts. Please refer to the ActiveCampaign Events API integration guide if you'd like an event to be sent as ActiveCampaign event and displayed on the contact timeline in ActiveCampaign as well.

To leverage Formsable attribution, create custom fields with the same names as the Able attribution details: Landing Page, Referrer URL, UTM Campaign, UTM Source, UTM Medium etc. When such custom fields are present in ActiveCampaign, Able will automatically populate them with its attribution details.

Lead fields called tags and lists have a special meaning. Able attempts to locate matching ActiveCampaign tags and lists and adds them to the contact if available. These fields can have multiple comma-separated tags or list names, for example: "form-lead,landing-page-one".

What else you can do

Track Leads

Send Events Using Webhooks

Events can be sent to Able CDP from custom apps using its inbound webhook. This is convenient to attribute purchases and other conversions that aren't necessarily reflected in the payment system. For example, when the service usage accumulates before being invoiced once a payment threshold is reached or next billing cycle occurs.