Start and stop campaigns from a CRM field

How a contact field in HubSpot, Salesforce, Pipedrive, Attio, Dynamics 365, GoHighLevel, monday.com or Zendesk starts a campaign and stops it, and what ACR logs back.

Last reviewed November 7, 2026

The start field

Each CRM connection adds a text field to your contacts. Put a campaign's ID in it and ACR starts that campaign for the contact. The value names one campaign, and that campaign must use the CRM as its lead source. A CRM campaign has one trigger, Contact field set, and its lead source step shows the campaign's ID and stop value with Copy buttons.

ACR starts the campaign only when all of these hold:

The campaign is published and its Contact field set trigger is on.
An admin has pressed Start reading on the CRM connection. Before that, ACR stores nothing from the CRM.
The contact has a phone number or an email. Salesforce records need a phone number.
The campaign's cap, cooldown, start conditions, consent and country rules let the contact in.

Setting the same ID again does nothing. An ID that belongs to no campaign using this CRM starts nothing, and the lead's events say why.

Stopping, and starting again

The stop value, the campaign's ID followed by -stop, always stops that campaign's open run for the contact. What clearing the field does depends on the CRM:

CRM	Start field ACR creates	Clearing it	How ACR hears of a change	Connect today?
HubSpot	ACR Active Campaign ID, a contact property	Stops nothing	HubSpot notifies ACR, and the campaign starts within a minute	No: needs Growth Dept's HubSpot app
Salesforce	ACR Campaign ID, on Leads and Contacts	Stops nothing	ACR checks every 3 minutes	No: needs Growth Dept's Salesforce app
Pipedrive	ACR Active Campaign ID, a person field	Stops	Pipedrive webhook	Yes, with a personal API token
Attio	ACR Active Campaign ID, a people attribute	Stops	Attio webhook	Yes, with an access token
Microsoft Dynamics 365	ACR Active Campaign ID, a contact column	Stops nothing	ACR checks every 3 minutes	No: needs Growth Dept's Microsoft app
GoHighLevel	ACR Active Campaign ID, a contact field; `0` also stops	Stops nothing	GoHighLevel webhook	No: needs Growth Dept's Marketplace app
monday.com	ACR Campaign ID, a column on the board you pick	Stops	monday.com webhook	Yes, with a personal API token
Zendesk	ACR Active Campaign ID, a user field	Stops	Zendesk webhook	No: needs Growth Dept's Zendesk app, which Zendesk approves

To run a campaign again for the same contact, stop or clear it first, then set the ID again; the campaign's cooldown still applies. Salesforce and Dynamics 365 only show ACR records whose field holds a value, so there, set the stop value and let a check pass before you set the ID again.

While the campaign's consent rule is on, calls and texts need the contact's recorded opt-in, and by default so does email. Map your CRM's opt-in fields to consent.sms, consent.calls and consent.email with field mapping, and keep An opt-in field you mapped from your CRM ticked under Consent that counts on the Compliance step. HubSpot, Salesforce and Dynamics 365 bring only a fixed set of fields, so for their contacts an opt-in can only come from consent ACR already holds for the same email or phone.

Do-not-contact fields come across as opt-outs: HubSpot's email opt-out, Salesforce's Email Opt Out and Do Not Call, the do-not-phone and do-not-email options in Dynamics 365, GoHighLevel's Do Not Disturb, and the opt-out fields ACR creates in HubSpot, monday.com and Zendesk. An opt-out always wins. Consent has the full rule.

Microsoft Dynamics 365

Enter your environment's address, such as https://yourorg.crm.dynamics.com, and sign in with a Microsoft account that can customize the contact table. Create the contact column adds ACR Active Campaign ID with your environment's default publisher prefix; to use a column you made, give its logical name when you connect. ACR reads the name, email, mobile or business phone and country.

With Log activity in Microsoft Dynamics 365 on, calls become phone call activities, emails become email activities and texts become notes, and an opt-out sets the contact's do-not-phone, do-not-email and do-not-bulk-email options.

monday.com

Connect with a personal API token from your profile picture, Developers, My access tokens. Under Board with your contacts, choose the board where each item is a contact, with its name and its phone, email and country columns. Add the columns and webhook adds two text columns, ACR Campaign ID and ACR Do Not Contact, and a webhook for the first. Anything written in ACR Do Not Contact counts as an opt-out of every channel.

With Log activity in monday.com on, ACR posts an update on the item for each call, email and text, and fills ACR Do Not Contact when someone opts out. A webhook made with a personal token is not signed, so its private address is the only check; ACR reads the item itself before acting on it.

Zendesk

Enter your Zendesk subdomain and sign in as an admin. Create the user fields and webhook adds ACR Active Campaign ID and ACR Asked Not To Contact, and a signed webhook for changes to the first. A ticked ACR Asked Not To Contact counts as an opt-out of every channel. Zendesk does not let outside apps use a customer's API token, so Zendesk connects only through Growth Dept's app.

With Log activity in Zendesk on, each call, email and text is added to the top of the user's notes, which keep the newest 10,000 characters, and ACR ticks ACR Asked Not To Contact when someone opts out. ACR opens no tickets, so customers get no Zendesk emails from it.

Logging activity back

Each CRM connection has a Log activity in switch, off until an admin turns it on. From then on, ACR logs each call, email and text on the contact the lead came from, about every minute and 25 at a time. A call is logged once its result is in, or after 30 minutes. A failed entry is tried up to 5 times. Opt-outs are covered in Pass opt-outs back to your connected tools.

Every CRM connection has been tested against a simulated version of the vendor's API only. None has been connected to a live CRM account yet.