and simultaneously (in the same environment and with the same target audience) have the ability to use the Card Add-In connecting ContactId from Customer Profile in Customer Insights with ContactId (using "Proyect attribute" functionality) in Dynamics 365 Sales so as to personalize a Contact Form in D365 Sales where to use Customer Insights information (attributes, measures for the related account, activities, segments).
Comments
To help us better understand your suggestion, please answer the following questions:
1) Could you describe how you are ingesting the data from Dynamics 365 Sales into CI: What's the data structured like in CI?
2) You mention the functionality "projected attributes": This is available for segments, but it doesn't work on the Customers entity. What problem were you hoping to solve with projected attributes?
Independent from your answers, I'm sharing the product team's goals regarding using CI data in Dynamics 365 apps:
Customer insights’ goal is to offer an effortless way to surface its valuable data in Dynamics 365 apps and Power Platform. The Customer Insights card add-in has no GA date, because most customers are transitioning to use the data through the Dataverse that provides additional customization options. This means Dataverse with its connectors and API are the sustainable consumption service. For time being, the card add-in is our out-of-the-box solution for showing some Customer Insights data in Dynamics 365 apps.
Category: Outbound Connectors & Extensibility
Nils Keller (administrator) on 10/10/2024 3:21:59 AM
We have plans to incorporate account insights into the standard release of CI-Data in the future. As a result, we've deprecated the use of the standalone B2B version in favor of a single instance that can provide both customer and account insights.