Skip to main content

​
Why don’t my Active Campaign numbers change when I narrow the date range?

Active Campaign reports cumulative per-campaign totals rather than time-series rows. The ActiveCampaign API returns a single running total for each campaign metric (opens, link clicks, unsubscribes, and so on) and does not accept date-range parameters, so a narrower date range cannot reduce those totals. In a widget, the date range instead scopes which campaigns appear — campaigns are bucketed by their created and sent timestamps — while each campaign’s figures stay at their full lifetime value. This is expected behavior for the connector, not a data error. For the full breakdown and metric catalog, see the Active Campaign data reference.

​
Why does connecting Active Campaign ask for an API URL as well as an API key?

Each ActiveCampaign account has its own account-specific base URL, in the form https://<account>.api-us1.com (or a regional equivalent). Adriel builds every request from that base URL, so the API URL and the API Key are both required at connection time: the key alone cannot identify which account to query, and a generic host will not resolve to the correct account. The API URL and API token both appear in the ActiveCampaign account under Settings → Developer. Full connection steps are in How to connect Active Campaign to Adriel.

​
Why is Active Campaign labelled beta?

Active Campaign is currently a beta connector. Its coverage and behavior may still change, and reporting is limited to what the ActiveCampaign campaigns endpoint exposes — cumulative per-campaign metrics with no intra-campaign, send-level, or recipient-level granularity. Existing dashboards keep working through beta; the label signals that refinements are still landing.

​
Why are some of my Active Campaign campaigns missing from the dashboard?

The connector reads the campaign list in pages and stops at a fixed ceiling of 600 campaigns per data source. Accounts with more than 600 campaigns will not have every campaign represented, and the extras are dropped rather than partially loaded. Each sync also replaces the entire campaign snapshot rather than adding to it, so the dashboard reflects the campaigns present in the most recent successful sync. To keep the most relevant campaigns in view, splitting a very large account across more focused data sources helps stay under the ceiling.

​
My Active Campaign connection shows an error or returns no data — what should I check?

The most common causes map to specific messages surfaced by the connector:
  • The provided Token is invalid. — the API token was rejected (HTTP 403). Reconnecting with a freshly copied API Key from the ActiveCampaign account usually resolves it.
  • The provided API URL is invalid. — the API URL is malformed or does not resolve. It should be the full account URL, for example https://<account>.api-us1.com, copied exactly from the ActiveCampaign developer settings.
  • Payment Required — ActiveCampaign returned an account billing issue (HTTP 402), which automatically disconnects the data source until the account is in good standing and reconnected.
Reconnection steps are covered in How to connect Active Campaign to Adriel. If the connection is valid and the error persists, email support@adriel.com with the data source name and the exact message shown.