Dynamics 365 Customer Insights - Data

We propose the implementation of additional functionalities within Dynamics 365 Customer Insights - Data to enhance rule setup flexibility and adaptability.

1. Inclusion of "Is Not" Functionality: We suggest incorporating the same capabilities found in the "Is" statement into the "Is Not" statement. This enhancement would provide users with comprehensive options when setting up rules across various scenarios. Right now when we want to specify a segment using the "Is" statement, we then have the following 12 options: "Specific date", "after", "on of after", "before", "empty", "within last", "between", "month of", "year of", "day of month", and "day of week". While if we choose "Is not" we have the following 3 options: "Specific date", "empty", and "between".
2. Dynamic Date Rules: We advocate for the introduction of dynamic date rules to enable more versatile segmentation based on temporal criteria. For instance, users may seek to identify customers who made purchases one or two years ago. Presently, segments can be created statically using the "between" rule, but a dynamic approach would significantly benefit users, especially as the platform transitions to Real-Time marketing strategies.

By implementing these enhancements, Dynamics 365 Customer Insights - Data would offer increased flexibility and efficiency in rule setup, empowering users to derive deeper insights and optimize marketing strategies effectively.

It is not currently possible to delete topics in commercial consents from compliance profiles. 

However, as the purpose of topics is to target marketing emails, they are sometimes temporary. 

Therefore, the ability to delete them would improve the user experience and reduce confusion through leaner tables.

Hello all,

We have been having discussions with Product Group - both CI and PQ teams as there is a request from Franklin Templeton on PQ connector improvement.

The connector as of now supports connection with Snowflake DB but it can use AAD or Basic Authentication. To best fit the business requirement the connector should support the additional authentication layer - OKTA.

Let us now if this request can be considered into the roadmap.

In the process of defining the customer's activities, being able to select one more additional attribute of the activity. (Currently in the "Activity unifiation" stage of the "Create an activity" process, it is only allowed to select one "additional details"). Thanks

The Timeline section, makes the created activities available there. Each activity definition comes from an Entity that has more detailed information. It would be very useful to access from the Timeline section and be able to obtain a list with more details for each activity. Thanks

When you add Customer interactions to contact´s timeline by using Custom Connector

You´ll receive ALL interactions from the contact e.g. when he receives an email, opens it etc. Users who have the READ privilege to see these records will have a timeline which is by far too cluttered so other important activities will become almost lost or the user has to dig further down the timeline to find those activities.

How can we configure the connector to make e.g. only showing Email sent from Customer Insights and make this setting global instead of per user based?

In the New Customer Connector pane there is this option called Configuration path is that the right place? I haven´t seen any documentation regarding it.

Thanks