The Microsoft Dynamics 365 CRM Integration for APSIS One enables you to use all the data from your CRM in any marketing channel connected to your APSIS One account.
Simply map consent, important data fields or Marketing Lists to APSIS One to start creating data driven marketing activities today.
Curious to know how our integration to Dynamics works? Get a quick introduction into how to leverage customer data across the two systems. If you're hungry for inspiration, find out how a CRM integration can boost your sales and marketing today.
Ensure a smooth installation and configuration by following the step-by-step guides. Get an overview of the solution and deep-dive into specific aspects about security and authentication.
Syncing data between APSIS One and Dynamics CRM
There are two features that empower data transfer from Microsoft Dynamics 365 CRM into your APSIS One account: Real-time Sync and Full Sync.
A Real-time sync takes place whenever a contact card is created or updated. This results in a corresponding Profile being updated or created in APSIS One, matching the state of the contact.
A Full sync systematically goes through all contacts in your Microsoft Dynamics account and either creates a new Profile in your APSIS One account, or updates the existing Profile data. We recommended using this feature after setting up your initial mappings, or when you intend to sync new mappings.
What comes after the sync? Syncing your customer data into APSIS One Profiles is great for a comprehensive overview of your platforms... But, without Consent Mapping, you can't communicate with your customers! Make sure to set up the Consent Mapping for both the Email and SMS channels.
When a Profile is created in the APSIS One account, it will receive the contact ID as a unique identifier, and Email and SMS consent is updated accordingly. All data is written through Microsoft Dynamics 365 CRM.
If a Real-time or Full sync detects a new email address for a Profile, the following will take place:
1. The new email address will be opted-in to all Topics which the old address had given consent to;
2. The old email address will be opted-out from all Topics and lose any consent, as it's no longer in use.
How do you integrate?
Here's a summary of the process of integrating Microsoft Dynamics 365 with your APSIS One account. Click to jump right to a section in the article for a more detailed run-down.
You will require both an APSIS Integration User security role and an installation file in order to perform the installation.
1. Install Microsoft Dynamics 365.
2. Enable Microsoft Dynamics 365 with your APSIS One account.
3. Add Sync Conditions to sync Profile data that corresponds with your APSIS One Section.
4. Map APSIS One Attributes to the data from your contact card in your Microsoft Dynamics 365 CRM account.
5. Map the Consent lists and Topics to your subscriptions.
6. Sync your data!
The APSIS One Integration solution only works with Microsoft Dynamics 365 CRM for Sales: No other products from the Microsoft Dynamics 365 CRM family are currently supported.
The APSIS One integration is intended to work with all recent versions of Microsoft Dynamics 365 CRM for Sales, or any version above 18.104.22.168.
The installation does not change any local files and does not require any specific software to be installed on the end-user's system. The only prerequisite is a web browser. To see which browsers are supported please refer to Microsoft's official documentation.
Please note that currently the APSIS One Integration is not intended to work with an on-premises version of Microsoft Dynamics 365 CRM for Sales.
APSIS One Configuration Values
Here's a list of all APSIS One values sent to Microsoft Dynamics 365 CRM:
Discriminator for the Section on which the integration was installed.
Discriminator for the Keyspace created to use with the integration.
APSIS One API Client ID.
APSIS One API Client Secret.
The installation package includes one security role which is required to access the entities related to the APSIS One integration. The name of that security role is APSIS Integration User. and it can be combined with other security roles, including both built-in and custom roles.
This role ensures that users with this role have read-only access to the apsis_authentication and apsis_events entities.
Virtual entities to show APSIS data are still under development and the list will be extended as new functions are implemented.
Currently, only the apsis_event entity is implemented, which provides a list of Events shown on the Contact Card.
To read more, head over to the MSD Developer Guide on Virtual Entities.
APSIS Authentication Subsystem
The APSIS authentication subsystem is aimed to provide easy access to APSIS authentication token and consists of the CRMK.APSIS.Authentication plugin, registered automatically during the installation, and the apsis_authentication entity.
During installation, several configuration values holding APSIS credentials are pushed. These allow the subsystems to work as intended.
After the configuration, the authentication subsystem provides the APSIS authentication token. Once expired, it can be renewed.
The authentication subsystem is intended to work only for the purpose of integrating MSD with APSIS One, and not for users to interact with directly.
Get the token information as an output by retrieving the apsis_authentication entity.
About Microsoft Dynamics CRM
"Microsoft Dynamics 365 CRM is a set of intelligent business applications that helps you run your entire business and deliver greater results through predictive, AI-driven insights.
Read more on Microsoft Dynamics 365 CRM's website.