Prerequisites:

• An MS dynamics account.
• Dynamics Domain Name
• Web API Endpoint
• Application Client ID
• Tenant ID
• Client Secret

Getting Started:

• Log in to your Datahash account on https://studio.datahash.com/login
• Navigate to the CRM category under the Sources list in the left section.
• Click on the “MS Dynamics” connector tile

• Choose the type of Client Credentials.
• Provide the following details:

1. Dynamics Domain Name: Domain Name for the MS Dynamics 365 account. You can find it in the address bar after you log in.
2. Web API Endpoint: It is a service URL required for authentication. You can find it in Microsoft Power Apps > Settings > Developer Resources.
3. Application Client ID: The client ID is a distinctive identifier assigned to an application during its Azure Active Directory (AAD) registration.
4. Client Secret: A client secret is confidential info an app uses to verify its identity when authenticating with Azure Active Directory (AAD). 
5. Tenant ID: A Tenant ID (or Directory ID) is a unique identifier linked to an Azure Active Directory (AAD) instance, serving as a global identifier for each Azure AD tenant.

Getting the Credentials:

• Login to your MS Dynamics account & copy the address bar to get the domain.
• 

.

• Go to Microsoft Azure. Navigate to Microsoft Entra ID (formerly Azure Active Directory) > App Registrations > New Registration.

• Register your Application by providing the details.

• You can copy the Application Client ID & Tenant ID.

• Create a new Client Secret for the Application by following the steps in the screenshot.

• Copy the client secret and note it for later use. Make sure to copy the Value field, as below.

• For the Web API Endpoint you need to go to Microsoft Power Apps > Settings > Developer Resources..

• Once done, click on Validate Credentials.

• Choose the data entity as Offline Events.

• Select the MS Dynamics module from which you want to track the lead status updates into the Offline Conversion API and provide a name to the connection.

• Next step is to map the CRM fields with the data points required for Offline Conversion API integration.
• Configuration: Select the following column name:

1. Offline Event: This field indicates the identifier for the offline event in the CRM.
2. Event time: This is the field that indicates the time at which the lead is captured
3. Last Modified Date: This is the field that indicates the lead’s most recent update time to synchronize the latest updates. The default sync frequency is daily.

• Personal Information: Now you need to map the offline schema to MS Dynamics column name. Here, the details of the User are asked.

• Product: In similar way as done above we need to map the offline events schema of the product to the MS Dynamics.
• Once done, click on “Test Connection” to proceed.

• Once done, you can view the latest leads data available in your CRM as per the mapping provided above.

• You can check for errors if any are shown in the table data itself.
• Click Finish to complete the setup.

•  You can access the set-up again by clicking on the edit button in the MS Dynamics connector widget.
• 

• The set-up configurations can be edited if required, from the Manage connections section.

• The source setup is completed, now the destination is to be set up. For that, refer to the documentation below:
• Set up Snapchat Offline Conversions API data destination