Microsoft Dynamics 365 Lead Delivery Follow

Overview

Microsoft Dynamics 365 Lead Delivery sends leads from your Convertr campaign to Microsoft Dynamics 365 in real time, creating a Lead record for each delivered lead.

This removes manual exports and gets qualified leads into your sales team's workflow as soon as they pass processing.

In this guide, you'll learn how to set up Microsoft Dynamics 365 Lead Delivery in your Convertr campaign.

Please note:

  • This connection creates and updates standard Lead records. If you need to write to custom entities or non-standard fields, use custom setup via HTTP Integration instead.
  • You'll need an Azure app registration with permission to create leads in your Dynamics environment.

 

Adding Microsoft Dynamics 365 Lead Delivery Job

To add the Microsoft Dynamics 365 Lead Delivery job to your campaign:

  1. Go to Processr > Integration tab.
  2. Click Add to create a new job.
  3. From the dropdown, select Microsoft Dynamics 365.
  4. Complete the configuration sections as shown below and click Save.

 

Configuring Microsoft Dynamics 365 Job

API

This section controls how Convertr authenticates with your Dynamics environment.

Credential Source offers two options:

  • Credentials Manager (recommended) — select a saved credential set from the Manager Credentials dropdown. Credentials are stored centrally, so they can be updated once and the change applies to every campaign using them. They are not visible in the campaign configuration.
  • Manual — enter the Client ID, Client Secret, Tenant ID and Instance URL directly. These values are saved in this campaign's configuration and are visible to anyone with access to it, and must be updated separately in each campaign that uses them.

Generate your credentials in Azure:

  1. In the Azure portal, go to Microsoft Entra ID > App registrations and select or create your application.
  2. On the Overview page, copy the Application (client) ID and the Directory (tenant) ID.
  3. Go to Certificates & secrets > New client secret, then copy the secret Value immediately — Azure only displays it once.
  4. Your Instance URL is your Dynamics environment address, for example https://yourorg.crm.dynamics.com.

Please note: The app registration must have permission to create Lead records in your Dynamics environment, and a matching application user must exist in Dynamics with an appropriate security role.

Update If Exists

This section controls what happens when a lead is delivered with an email address that already exists in Dynamics.

  • Yes — the existing record is updated with the new lead data.
  • No — a new record is created alongside the existing one with that email address.

Subject

Enter the value written to the Subject field of every Lead record created by this campaign. This is the record's topic in Dynamics and is commonly set to the campaign name, so your sales team can see at a glance where the lead came from.

This field is required.

Mapping

In this section, you can configure how your Convertr lead fields map to your Dynamics fields.

A default mapping covering the most common fields is provided and suits most campaign setups. You can adjust this list to better fit your needs:

  • Remove the mappings you don't need. You can re-add them later with the Add button.
  • Add a new row for any additional field you want to deliver.
  • On the left, enter the Dynamics field name — this is the logical name of the field, for example emailaddress1. You can find it in Dynamics under Settings > Customizations > Entities > Lead > Fields.
  • On the right, choose the Convertr lead field that supplies the value, or type a field name manually if it isn't in the list.

Please note: If the Dynamics field name doesn't match a field that exists on the Lead entity, delivery will fail for that lead. Check the logical name rather than the display name shown on the form.

 

Testing the Setup

To verify your configuration:

  1. Submit a test lead to your campaign.
  2. Open the Leads tab of your campaign.
  3. Click View to open the lead details.
  4. Go to the Processr Log tab and confirm the Microsoft Dynamics 365 job completed successfully.
  5. In Dynamics, open Sales > Leads and confirm the record was created with the expected field values and Subject.

 

Troubleshooting

If your leads aren't appearing in Dynamics:

  1. Go to the Processr Log and Provider Log tabs in the lead view.
  2. Check the Microsoft Dynamics 365 job entries for errors.

Common causes:

  • Authentication errors — the Client Secret has expired, or the credentials don't match the environment in the Instance URL. Client secrets in Azure expire on a set schedule and need to be regenerated.
  • Permission errors — the application user in Dynamics doesn't have a security role that allows creating or updating Lead records.
  • Field errors — a mapped Dynamics field name doesn't exist on the Lead entity, or the value doesn't match the field type (for example, text delivered into an option set field).

If the issue persists, please contact our support team.

 

Complex Setup

Contact our support team for assistance with complex setups.

Articles in this section

See more

Related articles