---
title: "ActiveCampaign Integration in 2 to 6 Weeks | JustAutomate"
description: "We connect ActiveCampaign to your CRM, shop and invoicing, settle which journey wins when a contact sits in two, and gate every send on consent."
url: "https://justautomate.ai/en/integrations/activecampaign/"
lang: en
---

CRM and sales

# ActiveCampaign integration from a scoring threshold to a sales call

ActiveCampaign is marketing automation with a CRM built in: conditional journeys, scoring and segmentation by behaviour. We connect it to your CRM, shop, invoicing and data warehouse, and along the way we settle the thing nobody wants to discuss: what happens when the same contact sits in three journeys at once. A contact with no marketing consent enters none of them.

 Book a free consultation [See how the workshop works](https://justautomate.ai/en/services/process-workshop/)

- 2 to 6 weeksfrom the workshop to working ActiveCampaign journeys wired into your CRM, shop, invoicing and data warehouse
- 15 minuteshow often the scheduled job pushes tags, scores and deal stages into HubSpot or Pipedrive, so a rep never logs into a second system
- 0 sends without consenta contact with no marketing consent does not enter a journey, because the entry condition checks it before the first email. Art. 6(1)(a) GDPR

The problem

## Why does the same customer get three emails from three journeys on a Wednesday?

An ActiveCampaign account grows in layers. The first journey was built by someone who has since left, the second by an agency, the third by a marketer in the week before a conference. Two years on there are several dozen journeys and nobody can say which of them actually run. On Wednesday the same customer gets a nurture email, a webinar reminder and a win-back offer, because every journey sees them on its own and none of them knows about the others.

The second thread is scoring and the deal. Points were once awarded for opening an email and landing on the pricing page, but nobody has recalculated the threshold since, so the rep treats it as noise and calls whoever they feel like. The deal lives in the CRM built into ActiveCampaign while sales works in HubSpot or Pipedrive, so there are two versions of the same pipeline. The question of how many opportunities you have this month has two answers and both can be defended.

The third cost is formal and the least forgiving. Marketing consent is [Regulation 2016/679](https://eur-lex.europa.eu/eli/reg/2016/679/oj), Art. 6(1)(a): without it a contact has no legal basis for a send and does not enter a journey. Art. 7(3) gives the recipient the right to withdraw consent at any time and requires withdrawal to be as easy as giving it. For email marketing [Directive 2002/58/EC](https://eur-lex.europa.eu/eli/dir/2002/58/oj), Art. 13, sets prior opt-in as the rule. With several dozen journeys and a few lists running at once, taking one person off all of them is manual work, which is why it tends to be done by halves.

- The same customer gets a nurture email and a win-back email on one day, because both journeys can see them
- The rep does not believe the score, because nobody knows what the points are actually for
- The deal lives in ActiveCampaign while sales works in HubSpot, so no pipeline number agrees with any other
- An imported contact with no marketing consent enters a journey before anyone notices

Why now

## What changed, so that sorting this out takes weeks rather than a quarter?

ActiveCampaign exposes a REST API and webhooks on the events that used to be caught by hand: a contact created, a tag added or removed, a deal stage changed, a journey finished. The full list of events, fields and limits sits in the [ActiveCampaign developer documentation](https://developers.activecampaign.com/). Make or n8n picks up each step a second after it happens, and nobody waits for an overnight export into a spreadsheet.

The second change is segmentation by behaviour rather than by list membership. Site tracking on your own pages sends page views and form submissions back into the account, so a condition in a journey can read "visited the pricing page twice this week" instead of "is on list number four". With a shop you also get events from Shopify, WooCommerce or PrestaShop: a completed order and an abandoned cart.

The third change is organisational rather than technical. Entry conditions, exit conditions and goals have been in ActiveCampaign for years, but almost nobody writes down which journey takes priority. Once the hierarchy is written down it can be coded once: onboarding pulls the contact out of nurture, an open deal blocks win-back, a manual campaign skips contacts already in a sales journey.

The fourth change is the AI agent. A journey will send and log the result, but it will not answer the question of which journeys a given contact is in right now, or how many contacts crossed the scoring threshold and never got a call. BOND, our company AI agent, answers that in a plain sentence in 5 to 10 seconds, reading from ActiveCampaign and your CRM at the same time.

The fifth thing is scope, so you know what is not here. This page is about the ActiveCampaign account itself and what happens inside it once there are several dozen journeys. One type of journey is covered separately under [automatic email sequences](https://justautomate.ai/en/automations/automatic-email-sequences/), and the layer above the tools, meaning a shared definition of a lead and one way of measuring campaigns, under [marketing automation](https://justautomate.ai/en/services/marketing-automation/).

What changes

## What do marketing and sales get out of it?

- ### One journey per contact, not three
The hierarchy of journeys turns into entry and exit conditions written into every automation. Onboarding pulls the contact out of nurture, an open deal blocks win-back, and a manual campaign skips contacts already in a sales journey.
Priority written down for every journey, not kept in the head of the person who built it
- ### A score sales actually believes
We set the threshold with the reps and recalculate it on your contacts from the last 90 days, so you can see how many people cross it today. Points go to behaviour a rep recognises: a return to the pricing page, a quote opened, a spec sheet downloaded.
Threshold recalculated on 90 days of history, not set by feel
- ### The contact reaches the rep with context
Crossing the threshold creates a deal in your CRM with tags, score and email history, assigns an owner and creates a task. The Slack notification says what this person read and when, so the call does not open with a question about how you can help.
Deal, owner, task and a Slack notification within seconds of the threshold being crossed
- ### One system of record, two systems
We map ActiveCampaign custom fields onto properties in HubSpot, Pipedrive or Salesforce and set the write direction field by field. A scheduled job pushes tags, scores and deal stages every 15 minutes.
Write direction set per field, synchronisation every 15 minutes
- ### Consent enforced by the entry condition
Marketing consent is an entry condition on every journey, not a field somebody checks at the end. Withdrawing consent removes the contact from every automation and every list in one move.
Art. 6(1)(a) and Art. 7(3) GDPR handled inside the account, not in an email to marketing
- ### Questions about the account in a plain sentence
Which journeys is this contact in. How many people crossed the scoring threshold this week and never got a call. Which automation produces the most unsubscribes. The AI agent answers from ActiveCampaign and the CRM at once.
An answer in 5 to 10 seconds, with no login to two systems

Proof

## Do you hand contacts over this way yourselves?

Yes, though not in ActiveCampaign. In our founders' agency the same job is done by an AI agent wired into HubSpot and the website forms, built with the method described above. Below is the scale of that work, together with what the number does NOT prove.

Built for ourselves. These are not client deployments but implementations inside the founders' own companies. We say so plainly, because proof you cannot verify is not proof.

- ![JustIdea Agency](https://justautomate.ai/klienci/justidea.png)![JustBot](https://justautomate.ai/agenci/justbot-80.webp)JustBottheir agent
JustIdea Agency, a performance marketing agency of around 30 people
23
people from the company work with the agent
38
systems wired in permanently
112
processes run without a human
475
thousand lines of the agent’s code
The agent is wired into HubSpot, the website forms, Slack and the data warehouse. Enquiries arrive from forms, from ads and from referrals, and the contact and the company are created in the CRM with no person involved.
8 of 38 systems it works in

  - Google Ads
  - Meta Ads
  - HubSpot
  - ActiveCollab
  - Ahrefs
  - GA4
  - Search Console
  - BigQuery
Before
A person read the enquiry, created the contact and the company in the CRM by hand and decided who to pass it to. Nobody checked along the way whether that company was already in the database.
After
The agent picks up the enquiry, creates the contact and the company in HubSpot, checks for a duplicate by domain and notifies the team on Slack. A person steps in at the conversation.
3,432 operations on leads and 1,301 on form submissions in 30 days, with no human involved

And in your company

## What if our account looks different?

We usually work with B2B companies of 10 to 200 people that have had ActiveCampaign for at least a year and built up history in it worth keeping. Agencies and training companies arrive with too many journeys, machinery suppliers and system integrators with a score that tells sales nothing, and shops with the question of how to connect an abandoned cart to a B2B pipeline when the same address sits in both.

Four sentences come up most often, and this is how we answer them.

- We have had ActiveCampaign for three years and nobody knows what still works in there.
That is the most common starting point, which is why day one of the workshop is an inventory: which journey has an active entry, how many contacts went through it in the last 90 days, who built it and what for. Usually half of them turn out to be dead. We switch those off before we build anything, because integrating a dead journey means paying to maintain a mistake.
- Why connect HubSpot when ActiveCampaign has a CRM of its own?
If sales works in ActiveCampaign and there is one pipeline, we leave it alone and we will tell you so. Connecting makes sense when the reps sit in a second system, because then the problem is not a missing integration, it is a missing decision about which system is the record for which field. We take that decision at the workshop, field by field.
- Our score tells us nothing and the reps ignore it.
Because the threshold was once set by feel and nobody recalculated it. We take your contacts from the last 90 days, look at how many people cross the threshold today and how many of them actually bought, then set it together with the reps. A score nobody has tested on their own data is a number, not a signal.
- We are afraid an automation will email someone who opted out.
Rightly so, because that is the fastest way to lose trust and your sending domain at the same time. Marketing consent is an entry condition on every journey, and withdrawing it removes the contact from every automation and list in one move, as Art. 7(3) GDPR requires. We test that on a test contact before the switchover, not after the first complaint.

Marketing automation

ActiveCampaign: journeys, tags, custom fields, scoring, deals, site tracking

CRM

HubSpot, Pipedrive, Salesforce, the CRM built into ActiveCampaign

Shop and orders

Shopify, WooCommerce, PrestaShop, BaseLinker

Invoicing and finance

Xero, sevDesk, Fakturownia, Comarch Optima

Data and reporting

BigQuery, Google Sheets, Google Analytics

Team and automation layer

Slack, Google Workspace, Microsoft 365, Make, n8n, custom API integrations

## Seven journeys and who wins when a contact is in two at once

The journeys that usually survive an account inventory. The third column matters most, because it settles the situation no tool will settle for you: two automations see the same contact on the same day.

| Journey                         | Entry condition                                     | Priority when the contact is in two at once              |
| ------------------------------- | --------------------------------------------------- | -------------------------------------------------------- |
| Nurture after a form submission | marketing consent and a tag from the enquiry source | gives way to any sales journey once a deal exists        |
| Scoring threshold crossed       | score above the threshold agreed with the reps      | takes priority over nurture and over manual campaigns    |
| Onboarding after signature      | deal on the stage "Contract signed"                 | pulls the contact out of nurture and out of win-back     |
| Win-back                        | no activity for an agreed number of days            | does not start at all while the contact has an open deal |
| Abandoned cart                  | event from Shopify, WooCommerce or PrestaShop       | runs in parallel, capped at one message a day            |
| Upsell to existing customers    | base product bought and onboarding closed           | gives way to a support ticket from the same address      |
| Newsletter and manual campaigns | segment by tags and on-site behaviour               | excludes contacts already in a sales journey             |

Entry conditions and priority are agreed at the workshop, because that is a commercial decision rather than a technical one. A first rollout usually covers three to four journeys, and the rest follow once those hold up.

How we work

## Five steps from several dozen journeys to one working account

Process first. Tools second. Each step ends with something you can judge before you decide on the next one.

1. ### Workshop and account inventory
We list every automation, list, tag and custom field: which journey has an active entry, how many contacts went through it in the last 90 days, who built it. We talk to the reps as well as to marketing, because they are the ones who know whether the score means anything to them. We check where consents are stored and where imported contacts came from.
2. ### Design: hierarchy, field map, threshold
A hierarchy of journeys with entry and exit conditions, a map of custom fields onto properties in your CRM with a write direction per field, a scoring threshold recalculated on 90 days of history and a legal basis for every journey. Then the tooling choice: ActiveCampaign journeys alone, Make, n8n or a custom API integration.
3. ### Build alongside the current account
New journeys and webhooks run next to the existing ones, with nothing switched off. We push test contacts through them in several variants: one that opens, one that stays silent, one with consent withdrawn, one sitting in two journeys at once. Deliverability is checked on real Gmail and Outlook mailboxes, not in a preview pane.
4. ### Switchover and training
We disable the dead journeys and move the rest into production with monitoring on webhook and sync errors. The team gets documentation of the hierarchy and the field map, and learns to add a journey, change an entry condition and read the unsubscribe report without raising a ticket with us.
5. ### Measurement at 30 and 90 days
After 30 days we look at real data: how many contacts crossed the threshold, how many got a call, where the hierarchy worked against the intent, how unsubscribes split across journeys. After 90 days we compare pipeline stages before and after. We tune to what actually arrives, not to what we assumed.

Before and after

## How the week changes in marketing and in sales

### Before

- Nobody knows how many journeys in the account really run, so nobody switches anything off
- A customer gets two emails from two automations on one day and replies in anger
- The rep digs through the account to see what the contact opened, or does not bother
- The number of opportunities in ActiveCampaign does not match the number in the sales CRM

### After

- The inventory of journeys is written down and dead automations are off, with the date noted
- A contact is in one journey at a time, because priority is coded into the entry conditions
- The rep gets a deal with tags, score and email history, plus a task in the CRM
- Tags, scores and deal stages reach the CRM every 15 minutes, in the agreed direction

The first switched journeys are visible on the day they go live. We judge the scoring threshold and the hierarchy after 30 days on real contacts, and after 90 days we compare pipeline stages before and after.

For the person signing this off

## What the head of marketing or sales gets out of it

You stop answering the question of why a customer got two emails in one day, because journey priority is written into the account rather than into somebody's memory. The account also stops being a black box left behind by an agency: you have an inventory of automations, a field map and a date from which each journey either runs or is switched off.

The second thing matters more in front of the board. You know how many contacts crossed the scoring threshold and how many of them got a call rather than another email. That is the one number tying the marketing budget to the work of sales, and today you do not have it, because it sits in two systems.

- Inventory of automations and journey hierarchy written down, independent of whoever built them
- Write direction set per field, so two systems stop overwriting each other
- Consent and its withdrawal handled in the account, under Art. 6(1)(a) and Art. 7(3) GDPR
- A new journey and a changed entry condition done on your side after training, with no ticket to us

What it costs

## The workshop has a fixed price, the rollout is quoted after it

The process workshop costs **EUR 3,500 net per week** and runs from one to seven weeks depending on scope. For a single ActiveCampaign account one week is usually enough, two when the write direction has to be settled for several dozen fields and two pipelines at the same time. The rollout is quoted after the workshop, because the price depends on how many journeys survive and how many systems hang off the other side.

You pay ActiveCampaign, Make and n8n directly, and the same goes for language models, where the provider charges EUR 0.005 to 0.07 per query. No commission from us and no middleman who one day disappears along with access to your account.

- ### Process workshop
EUR 3,500 net
per week, usually one week for a single ActiveCampaign account
A self-contained piece of work. It ends with an account inventory, a journey hierarchy and a field map any implementer can build from, including your own team.

  - Inventory of automations, lists, tags and custom fields with contact counts from 90 days
  - Journey hierarchy with entry and exit conditions and priority when two collide
  - Field map onto properties in your CRM with a write direction per field
  - Scoring threshold recalculated on your data and a legal basis for every journey
 Start with the workshop
- Most popular
### Workshop and integration rollout
Quoted after the workshop
scope follows from the number of journeys and the systems on the other side
The option most companies choose. A working account connected to the CRM, the shop and invoicing 2 to 6 weeks after the workshop.

  - Everything in the workshop
  - Webhooks and synchronisation every 15 minutes with HubSpot, Pipedrive or Salesforce
  - Handover to sales: deal, owner, task and a Slack notification
  - Shop and invoicing connected, email history in BigQuery or Google Sheets
  - Switchover with error monitoring and training on entry conditions
 Talk about a rollout
- ### Integration and an AI agent
Quoted after the workshop
for teams that ask about the pipeline more often than they read reports
Everything in the rollout plus BOND, the company AI agent that answers questions about the account and the pipeline in a plain sentence.

  - Everything in the integration rollout
  - AI agent wired into ActiveCampaign and the CRM: where a contact sits, who crossed the threshold, which journey loses people
  - Alerts on contacts past the scoring threshold with no call for longer than the agreed limit
  - Access for marketing and sales, an answer in 5 to 10 seconds
 Ask about the agent

The workshop ends with a document: an account inventory, a journey hierarchy, a field map and a scoring threshold recalculated on your data. That document stands on its own without us and any implementer can build from it. If it turns out that switching off three dead journeys and fixing the entry condition on a fourth is enough, we say so and show you how. The engagement then ends at the workshop rather than at a rollout you do not need.

## Frequently asked questions

What is an ActiveCampaign integration?

It is the connection between your ActiveCampaign account and the systems your company actually works in: the sales CRM, the shop, the invoicing system and the data warehouse. The integration layer receives webhooks on a contact created, a tag added, a deal stage changed and a journey finished, then writes the result wherever the system of record is. Along the way we clean up the account itself, because integrating several dozen journeys of which half are dead costs more than switching them off.

How long does an ActiveCampaign integration take?

One week of workshop and 2 to 6 weeks of rollout. Connecting a single CRM through a webhook and a scheduled job every 15 minutes often closes in 2 weeks. The upper end applies to accounts with several dozen journeys, two pipelines and a shop, where the write direction has to be settled separately for every field.

What happens when the same contact is in several journeys at once?

We settle that at the workshop and it matters more than the choice of tool. Every journey gets an entry condition, an exit condition and a place in the hierarchy: onboarding pulls the contact out of nurture, an open deal blocks win-back, a manual campaign skips contacts already in a sales journey. Without that hierarchy the customer gets three emails in one day while the tool behaves correctly, because each journey sees them on its own.

Do we need a second CRM when ActiveCampaign has one built in?

If sales works in ActiveCampaign and there is one pipeline, you do not, and we will tell you so. A second system makes sense when the reps already sit in it and keep their quoting and reporting there. The question is then not integration as such, but which system is the record for which field, so that the two stop overwriting each other.

How do you recalculate scoring so that reps believe it?

We take your contacts from the last 90 days and check how many people cross the threshold today and how many of them actually reached a conversation or a purchase. Points go to behaviour a rep recognises: a return to the pricing page, a quote opened, a spec sheet downloaded. The threshold is set together with the sales team, because they will be making the calls and they have to find it sensible.

Can a contact with no marketing consent enter a sequence?

No. Marketing consent is an entry condition on every journey, so a contact from an import or from a form with the box unticked will not get the first message. The basis is Art. 6(1)(a) GDPR, while Art. 7(3) gives the right to withdraw consent at any time and requires that to be as easy as giving it. Withdrawal therefore removes the contact from every automation and every list at once, not from one.

How does ActiveCampaign data reach reporting?

Send history, opens and clicks are loaded into BigQuery or Google Sheets through the API, in batches rather than one query at a time. Only there can they be joined with shop orders and CRM stages, so cohort analysis and a retention report run on one dataset. Looker Studio reads from that with no overnight export and no person pasting a spreadsheet.

What does the AI agent do around ActiveCampaign?

BOND connects to ActiveCampaign and your CRM and answers questions that today need two reports side by side: which journeys a given contact is in, how many people crossed the scoring threshold and never got a call, which automation produces the most unsubscribes. The answer arrives in 5 to 10 seconds. Rolling out the agent takes around 2 months and is a separate stage after the integration.

## Let us check how many journeys in your ActiveCampaign really run

The free consultation takes 30 minutes. You tell us how long you have had the account, who built the automations and where sales works. We show you what can be fixed with an entry condition alone and what needs a connection to the CRM, the shop or invoicing. You do not have to share access to the account. You write to Paweł, one of the founders, and get an answer within one business day.

We run at most two rollouts at a time, so that someone is actually sitting on each of them.

[Book a free consultation](https://justautomate.ai/en/contact/)

**PS.** If somebody at your company got two emails from two automations on one day this week, that is exactly this problem. Once it is sorted the contact has one journey and one reason to reply, and the rep receives them with tags and a score rather than a link to the account. Writing down the hierarchy of journeys is where the workshop starts.

## Related

- [Automatic email sequences](https://justautomate.ai/en/automations/automatic-email-sequences/)
- [Marketing automation](https://justautomate.ai/en/services/marketing-automation/)
- [HubSpot integration](https://justautomate.ai/en/integrations/hubspot/)
- [API integration](https://justautomate.ai/en/services/api-integration/)
- [BOND, business AI agent](https://justautomate.ai/en/services/bond-business-ai-agent/)
- [Process workshop](https://justautomate.ai/en/services/process-workshop/)

---

**JustAutomate** · contact: contact@justautomate.ai · form: https://justautomate.ai/en/contact/