Meta Lead Ads

⌘K
  2. Home
  4. Docs
  6. Meta Lead Ads
  8. Step 2: Set up data desti...
  10. Option 5: Set up MS Dynamics Data Destination for Meta Lead Ads

Option 5: Set up MS Dynamics Data Destination for Meta Lead Ads

Video Walkthrough

Description  

The MS Dynamics connector in Datahash enables seamless transfer of Meta Lead Ads submissions directly into your Microsoft Dynamics 365 CRM, ensuring leads are instantly available for follow-up and nurturing.

Prerequisites  

  • MS Dynamics account
  • Dynamics Domain Name
  • Web API Endpoint
  • Application Client ID
  • Tenant ID
  • Client Secret
  • Defined field in MS Dynamics CRM module to capture Meta Lead ID

Setup Instructions  

  1. Login to Datahash
  2. Select MS Dynamics as Destination
    • Navigate to CRM category under Destinations
    • Click on the MS Dynamics connector tile



Choose the type of Authentication.

Provide the following details.

  • Dynamics Domain Name: Domain Name for the MS Dynamics 365 account. You can find it in the address bar after you log in.
  • Web API Endpoint: It is a service URL required for authentication. You can find it in Microsoft Power Apps > Settings > Developer Resources.
  • Application Client ID: The client ID is a distinctive identifier assigned to an application during its Azure Active Directory (AAD) registration.
  • Client Secret: A client secret is confidential info an app uses to verify its identity when authenticating with Azure Active Directory (AAD).
  • 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.

3. Prepare MS Dynamics

  • Ensure your MS Dynamics CRM has a field for Meta Lead ID
     (mandatory for mapping)
  • Identify any other mandatory fields in your CRM (marked with an asterisk)

4. Enter Authentication Details

  • Dynamics Domain Name – Found in the browser address bar after logging in
  • Web API Endpoint – Found in Microsoft Power Apps → Settings → Developer Resources
  • Application Client ID – From Azure Active Directory app registration
  • Client Secret – Generated during Azure AD app registration
  • Tenant ID – From Azure Active Directory properties
  • Choose Authentication Type
  • Click Validate Credentials

5. Select Source

  • Choose Meta Lead Ads as the source type
  • Select the connection name from your existing Meta Lead Ads Source
  • Provide a name for this destination connection



6. Field Mapping

  • Map Meta Lead Form Fields to the corresponding MS Dynamics Schema Fields
  • Meta Lead ID mapping is mandatory
  • Map all other CRM mandatory fields
  • Map any additional fields as needed
  • Click Test Connection

7. Complete Setup

  • Once verified, click Finish
  • The connection will appear in your dashboard

Managing Instances  

Add a New Instance  

  • Click the Edit icon in Manage Connections
  • Repeat the setup with a different connection name or mappings
  • Click Test Connection
  • Click Finish
  • New instance appears in Manage Existing Connections

Edit an Existing Instance  

  • Click the connection name in Manage Existing Connections
  • Click Edit (top right)
  • Update any values or field mappings
  • Click Test Connection
  • Click Finish
     (If Cancel is clicked, previous settings remain active)

How can we help?