Welcome! How can we help?

Popular Searches: Hubspot, SendGrid, Data Studio, Copying Settings, Testing Number Swapping

Integrating CallTrackingMetrics with Microsoft Dynamics


HomeSupport HubIntegrations › Integrating CallTrackingMetrics with Microsoft Dynamics
Last Updated: 06/13/2019

The Microsoft Dynamics integration allows you to send call data from your CallTrackingMetrics account into Dynamics to create or update any object type in Dynamics, including leads, contacts, and custom objects.  The integration allows you to:

  • Assign your Dynamics campaigns to your CTM tracking sources
  • Map your CTM users to users in Microsoft Dynamics
  • Create triggers to create or update objects in Dynamics based on custom field mappings
  • Fire triggers in CTM based on whether a record is found in Dynamics

This integration is not available for all subscription plans.  Click here to learn how to check or upgrade your current subscription.

Requirements:

The account used to link to Microsoft Dynamics must have administrator access to your Microsoft Dynamics account.

 

Connecting CTM to Microsoft Dynamics

This guide will walk you through configuring this information for your account in order to establish the connection between CTM and Microsoft Dynamics.  To configure this integration, you will need the following pieces of information from your Microsoft Dynamics account:

  • API domain
  • Tenant
  • App
  • API scope
  • API secret
We recommend opening a notepad document to keep track of this information while you follow the setup instructions so you can easily enter it in your CTM settings later.

 

Create the API Secret

First, you will create the API Secret using the following steps.

  1. Log in to your Microsoft Azure account at portal.azure.com.
  2. Click “Azure Active Directory” in the left-hand navigation, then select “App registrations” and click “New registration.”
  3. Enter a name and click to save the new registration.
    • By default, the permissions are set to “Accounts in this organizational directory only.”  It is recommended to leave this setting as-is.
  4. Click “Authentication” in the left-hand navigation.
  5. Here, you will need to add two redirect URIs:
    • https://app.calltrackingmetrics.com/link-dynamics
    • https://app.calltrackingmetrics.com/access-dynamics
  6. Click Save.
  7. Click “Certificates and Secrets” in the left-hand navigation, then click “New client secret.”

  8. Enter a name for the secret.  It is recommended to set the expiration to “never” so that you do not have to renew the secret.
  9. Click to save, then immediately copy the secret and paste it to a notepad document.  This is the API Secret you will need to enter in your CTM settings for Microsoft Dynamics.
    This is the only time the secret will be displayed and it cannot be retrieved after you navigate away from this screen.  If you lose the secret, you will need to create a new one following these steps.

 

Create the API Scope, App ID, and Tenant ID

Next, you will create the API Scope, App ID, and Tenant ID using the following steps.

  1. Next, you will create the API Scope, App ID, and Tenant ID using the following steps.
  2. Click “API Permissions” in the left-hand navigation, then select “Add a permission.”
  3. A list of commonly used APIs will appear.  You will need to add permissions for both “Data Export Service for Microsoft Dynamics 365” and “Dynamics CRM.”
  4. First, click Data Export Service for Microsoft Dynamics 365.
  5. Enter “user_impersonation” in the permissions field, then select the option “Grant admin consent.”
  6. Click to save.
  7. Repeat the previous steps to add “user_impersonation” for  the Dynamics CRM API.
  8. Next, click “Expose an API” in the left-hand navigation, then select “Add a scope.”
  9. You will be prompted to enter an Application ID URI.  You may use the default here, or enter a different one of you prefer (this cannot be changed later).
  10. Click Save and continue.
  11. Set the scope name to “user_impersonation.”
  12. Enter any name and description for the scope.
  13. Leave the consent option set to “Admins only” and make sure the state is set to “Enabled.
  14. Click Add scope.
  15. Copy the scope you have created and paste it into your notepad document.  This is the API Scope you will need later.
  16. Click “Overview.”
  17. Copy the Application (client) ID and paste it into your notepad document.  This is the App ID you will need later.
  18. Copy the Directory (tenant) ID and paste it into your notepad document.  This is the Tenant ID you will need later.

 

Enter Information in CallTrackingMetrics

Now, you will need to open the Microsoft Dynamics integration page in CallTrackingMetrics and enter all of the information you have saved.

  1. Navigate to Settings → Integrations → Microsoft Dynamics.
  2. Enter all of the following information into the provided fields:
    • API domain: the domain for your Microsoft Dynamics implementation (ex: mydomain.crm.dynamics.com). (https:// will be added automatically, so there is no need to enter it here)
    • Tenant: the “Directory (tenant) ID” you copied in step 18 under “Create the API Scope, App ID, and Tenant ID” above.
    • App: the “Application (client) ID” you copied in step 17 under “Create the API Scope, App ID, and Tenant ID” above.
    • API scope: this is the scope you copied in step 15 under “Create the API Scope, App ID, and Tenant ID” above.
    • API secret: this is the API secret you created and copied in step 9 under “Create the API Secret” above.
  3. Click Connect to Microsoft Dynamics.
  4. Select the Microsoft account you would like to use (this account must be an administrator in Microsoft Dynamics), check the box to allow permissions, and click Accept.
  5. Scroll to the Default Lead Ownership section of the integration page and select the default owner you wish to use for leads created or updated by the integration.  You may choose a specific user, or you may choose to have the lead assigned to the agent who answered the call.
The lead owner you choose must be mapped to a user in Microsoft Dynamics; otherwise, the user who linked the integration will be the default owner.

 

Agent Mappings

Once your accounts have been linked, you may map users in your CTM account to the corresponding users in your Dynamics account.  

  1. From the Microsoft Dynamics setup page, click or scroll to the Agent Mapping section.
  2. This section will populate with the list of users detected in your Microsoft Dynamics account.  Click the Select an agent drop-down and select the corresponding CTM user name for each user you would like to map between accounts.
  3. Click Save Mappings.

 

Field Mappings

Field Mappings are used to determine what data from your CallTrackingMetrics account will appear in your Microsoft Dynamics account and where.  You can create mappings for any Dynamics object type (such as a Lead or Contact), then use triggers to specify when those mapped fields will be updated.

  1. From the Microsoft Dynamics setup page, click or scroll to the Field Mappings section.
  2. Click Add Mapping.
  3. Use the drop-down menu to select the type of object you’d like to create a mapping for (such as a Lead).
  4. For each Dynamics field you wish to map, use the drop-down menu to select the corresponding CTM field.  You may also choose a default value for each mapped field and select whether new data will overwrite existing values in Dynamics.

    First Name and Last Name are required fields for Leads in Dynamics.  Make sure you always have both of these mapped.
  5. Click Untitled Mapping at the top of this list and enter a name for this mapping.  It is helpful to use a name that gives you an idea of what fields have been mapped to make trigger setup easier later on.
  6. Click Save Mappings.

Existing mappings will be displayed in the Saved Mappings tab.  You may edit or delete them from this view at any time.

 

Creating Triggers

When you have created the mappings for the fields you wish to update in Microsoft Dynamics, you will need to create one or more triggers to specify when that data will be updated.  Click here to learn more about triggers.

  1. Navigate to Calls → Triggers and click New Trigger.
  2. Enter a name for your trigger.
  3. Use the drop-down menu to select when you would like this trigger to run.  For Dynamics, you may wish to run a trigger at the start of a call, at the end of a call, or when contact information is manually updated.
  4. Select to have the trigger run for all activities or assign specific traffic numbers to this trigger.
  5. Click +Add Workflow
  6. Select the rules that should apply to this trigger.  You may wish to set rules for calls over a certain duration, or to only have a trigger run for first-time contacts.
  7. Click Add Action and select MS Dynamics Record Sync.
  8. Under Entity Mapping, select the name of the mapping you wish to use with this trigger.
  9. Select whether you would like to only add new records, only update existing records, or both (Insert Only, Update Only, or Update or Insert).
  10. Check the applicable boxes if you would like to associate the contact to the activity and if you would like to set a record owner (other than the default).
  11. Click Save Changes.

Linking Dynamics Campaigns to Tracking Sources

Once the integration is activated, you may choose to link your CallTrackingMetrics tracking source to your Microsoft Dynamics campaigns.  (This step is not required for the integration to work.)

  1. Navigate to Numbers → Tracking Sources.
  2. In the list of tracking sources, locate the source you wish to link to one of your Dynamics campaigns and click assign campaign.
  3. In the pop-up that appears, use the drop-down to select the campaign you wish to link to this source and click Save.
  4. The name of the linked campaign will now appear below the name of the tracking source in this list.  You may edit or remove the linked campaign at any time.

Was this resource helpful?
0 0


X