Microsoft Dynamics 365 + Growth Dept ACR
Built and tested. A contact column starts a campaign; it connects once Growth Dept registers its Microsoft app.
Ready once our app is registered
Overview
ACR checks your Dynamics 365 environment every three minutes for contacts whose ACR Active Campaign ID column changed, and starts the campaign it names. Setting the stop value ends it. Calls and emails are logged as phone call and email activities, texts as notes. Calls and texts still need the contact's recorded consent: map the opt-in fields your CRM keeps, or the campaign's consent rule skips them. It is built and tested against the vendor's documented API, and it connects once Growth Dept registers its app with Microsoft.
What Microsoft Dynamics 365 is
Microsoft Dynamics 365 is Microsoft's family of CRM and business applications.
How it connects, once the app is registered
The connection is built and tested. No store can connect it until Growth Dept registers its app with Microsoft Dynamics 365.
- 1
Connect your environment
Enter your environment's address and sign in with an account that can customize the contact table.
- 2
Let ACR add its field
ACR adds the ACR Active Campaign ID column to Dynamics 365, plus the webhook or check that tells it when the field changes.
- 3
Start a contact
Set the ACR Active Campaign ID column to the campaign's ID, by hand or with a Power Automate flow. ACR imports the contact and starts that campaign.
- 4
Stop a contact
Set the column to the campaign's stop value. Clearing it stops nothing.
- 5
Start reading and publish
Reading stays off until an admin starts it, with a confirmation. Then publish the campaign and switch its trigger on when you are ready.
What you can do today
No store can connect Dynamics 365 directly yet. If Dynamics 365 can post an event to a web address, the Custom API route below works today, because a Custom API campaign accepts events from any sender.
- 1
Create a Custom API campaign
Choose Custom API as the campaign's lead source. ACR shows a private trigger URL with its own token.
- 2
Send the event from Dynamics 365
Have an automation post the record to the trigger URL when your chosen column changes.
- 3
Use ACR's field names
Name the event checkout/updated and send the shopper's unique_id, email or phone, first_name, final_price and cart_link, as the API reference shows.
- 4
Send the purchase too
Post checkout/completed with the same unique_id to the same trigger URL when the shopper pays, so outreach stops for anyone who has already bought.
- 5
Test and publish
Run a practice conversation, then publish the campaign and switch its trigger on when you are ready.
Waiting on Microsoft Dynamics 365?
Tell us how you use Microsoft Dynamics 365. We will say what ACR can do for your store today and what is still ahead.