When analyzing Dynamics 365 Customer Insights data using Azure Synapse Analytics, the IT department should consider the following key points: Data sources based on a Common Data Model folder are supported when configuring an export to Azure Synapse Analytics, Administrator role access in Dynamics 365 Customer Insights is required to set up the connection between Dynamics 365 Customer Insights and Azure Synapse Analytics, and data can be exported to Azure Synapse Analytics on demand, or every time there is a scheduled refresh.
To create a segment of customers who are more interested in dogs than cats, you need a measure that directly compares the interests of dogs and cats. The 'Interest affinity score' measures the strength of interest in a specific category (in this case, dogs) as compared to other interests (such as cats) within a demographic. This makes it a suitable measure to determine which customers have a stronger preference for dogs over cats.
Real-time ingested activities show up in the timeline but are excluded from measure calculations. This means that while the real-time ingested data appears promptly in the timeline for visibility, it does not immediately update the measures calculated within Dynamics 365 Customer Insights. The lag in reflecting the updated order amount can be attributed to the exclusion of real-time data from the measurement calculations until a subsequent process updates these metrics.
Using Microsoft Power Automate to post a Microsoft Teams message when the number of members in a segment falls below a certain threshold is a suitable requirement that can be satisfied with out-of-the-box Power Platform capabilities. Power Automate offers robust capabilities for automating workflows and setting up alerts based on predefined conditions such as segment membership thresholds. This capability is a crucial feature for managing customer retention strategies, allowing the team to react promptly to variations in customer engagement.
The Microsoft Dynamics 365 Customer Insights REST API allows for specific actions. Firstly, it is possible to update customer attributes, such as a customer's residence type. Additionally, the API provides capabilities to manage data sources, including deleting an existing data source and adding a new data source to be ingested. However, updating a customer's predicted churn score is not feasible through the API as churn scores are typically calculated based on data rather than being manually updated. Defining new measures for analysis, like total accessory spend, is generally handled within the dashboard configuration and not directly through the API.