Emma Meade

While working in Customer Insights - Journeys, we had an issue with using multiple Attribute Groups in the Segment Builder. After talking to Microsoft Support, we learned that this was still a preview feature. We also learned that having Behavioral Groups, Existing Segments, and explicitly including or excluding records in Segments are all preview features.

There is only one piece of documentation that states that having multiple Attribute Groups is still a preview feature and there is no indication that it's in preview mode in the app itself. There is no documentation and nothing in the app that states that any of the other features mentioned above are in preview mode.

Please add something that indicates these features are still in preview mode, preferably in the Customer Insights - Journeys app itself, so that users can tell when they can use that feature in production, and whether, if there are any issues, it's because it's in preview or if it requires Microsoft Support.

Currently, you can only select one path to connect an Activity to a Customer Profile table (ex: If you're building Customer Profiles off of Contacts and Leads, you can only select one way to connect an Activity to a Contact, and one way to connect an Activity to a Lead. )

Since Activities may not directly refer to that Contact/Lead, but might connect to the Opportunity the Contact is tied to, or there might be another field (like the "To" line in an email activity), it'd be helpful to be able to specify multiple pathways where, similar to mapping in the Data Unification, if the first path doesn't yield results, it moves the next path, and so on.

Sometimes there are attributes that don't fully fit an activity, but are needed for situations like predictions.

For instance, if you want to make predictions based on SalesOrder activities, you need to have the IsReturn field filled. If you're making SalesOrders based on data that doesn't have an IsReturn field, it would be helpful to say when you're mapping the table that IsReturn should always be false.