Send segments to Dynamics 365 Marketing

Dynamics 365 Marketing helps you build personalized journeys across any touchpoint to strengthen your relationships with your customers. Dynamics 365 Marketing consists of two primary modules – Real-time Marketing and Outbound Marketing – along with event management capabilities. Create graphical emails and design interactive customer journeys to support all of your marketing campaigns.

Send static segments to Dynamics 365 Marketing from Amperity, and then manage collections of contacts. Build customer journeys using any combination of contacts – all contacts, by demographic, by behavior, by firmographic, or by other considerations – to narrow your segments down to the right audience for your marketing campaign.

What is a static segment in Dynamics 365 Marketing?

A static segment represents a static list of customers who are selected on a per-contact basis rather than created logically based on field values.

Static segments are added, and then submitted to the marketing-insights services each time they are loaded to Dynamics 365 Marketing, after which they are reevaluated by Dynamics 365 Marketing. Customers in a static segment are available from the Members tab in the Dynamics 365 Marketing user interface.

Note

This destination uses the Microsoft Dynamics Segmentation API to send static segments to Dynamics 365 Marketing. If the static segment does not exist, it will be created. If the static segment does exist, it will be truncated, and then loaded.

This topic describes the steps that are required to send segments to Dynamics 365 Marketing from Amperity:

1. Get details

2. Build a query

3. Add destination

4. Add data template

Get details

Dynamics 365 Marketing requires the following configuration details:

	Microsoft Azure must be configured for your Power Apps application, after which your Dynamics 365 Marketing application must be added to the Microsoft Power Platform. You will need to provide your Azure Active Directory tenant ID, Azure client ID, and your Azure client secret.
	The environment region and environment name Dynamics 365 Marketing. For example: “crm” (region) and “acme” (name).

Build query

You will need to build a query that outputs fields that can be mapped to static segments in Dynamics 365 Marketing.

Important

Query results must include the contactid field, which is the same as the contactid field for Microsoft Dynamics 365 CRM Contact.

Add destination

Configure Amperity to send segments directly to Dynamics 365 Marketing.

To add a destination

	Open the Destinations tab to configure a destination for Dynamics 365 Marketing. Click the Add Destination button to open the Destination dialog box. Enter a name for the destination and provide a description. For example: “Dynamics 365 Marketing” and “This sends segments to Dynamics 365 Marketing”. From the Plugin drop-down, start typing “dyn” to filter the list, and then select Dynamics 365 Marketing.
	Credentials allow Amperity to connect to Dynamics 365 Marketing. The credential type is set automatically. You may use an existing credential or you may add a new one. Select an existing credential from the Credential drop-down. – or – Select Create a new credential from the Credential drop-down. This opens the Credential dialog box. Enter the name for the credential, and then add a description. Dynamics 365 Marketing has the following settings: Azure Active Directory tenant ID Azure client ID Azure client secret When finished, click Save.
	Each destination has settings that define how Amperity will deliver data to Dynamics 365 Marketing. These settings are listed under the Settings section of the Destination dialog box. The following settings are specific to Dynamics 365 Marketing: Setting Description Environment region The environment region for your instance of Dynamics 365 Marketing. For example: “crm”. Environment name The environment name for your instance of Dynamics 365 Marketing. For example: “acme”.
	Business users are assigned to the Amp360 User and/or AmpIQ User policies. (Amp360 User allows access to queries and orchestrations and AmpIQ User allows access to segments and campaigns.) A business user cannot select a destination that is not visible to them. Business users – including users assigned to the DataGrid Operator policy – may have restricted access to PII. What is restricted access to PII? Restricted PII access is enabled when the Restrict PII Access policy option that prevents users who are assigned to that option from viewing data that is marked as PII anywhere in Amperity and from sending that data to any downstream workflow. You can make this destination visible to orchestrations and allow users with restricted access to PII to use this destination by enabling one (or both) of the following options: Note To allow business users to use this destination with campaigns, you must enable the Make available to campaigns option within the data template. This allows users to send campaign results from Amperity to Dynamics 365 Marketing. The other two settings may be configured within the data template instead of the destination.
	Review all settings, and then click Save. Important You must configure a data template for this destination before you can send data to Dynamics 365 Marketing.

Add data template

A data template defines how columns in Amperity data structures are sent to downstream workflows. A data template is part of the configuration for sending query and segment results from Amperity to an external location.

To add a data template

	From the Destinations tab, open the menu for a destination that is configured for Dynamics 365 Marketing, and then select Add data template. This opens the Add Data Template dialog box. Enter the name of the data template and a description. For example: “Dynamics 365 Marketing” and “Send segments to Dynamics 365 Marketing.”.
	Verify business user access to queries and orchestrations and access to segments and campaigns. A business user may also have restricted access to PII, which prevents them from viewing and sending customer profile data. If business user access was not configured as part of the destination, you may configure access from the data template.
	Verify all configuration settings. Note When the environment region and environment name settings were are not configured as part of the destination, you must configure them as part of the data template before making this destination available to campaigns.
	Review all settings, and then click Save. After you have saved the data template, and depending on how you configured it, business users can send query results to Dynamics 365 Marketing to Dynamics 365 Marketing.