With the release of Orchestrator, we have made working with activities much more intuitive and easy!
You may be used to filtering on activities throughout Engagio by searching for an activity category and then specifying the details of the activity--which may have made it difficult to find the activities you were looking for without a deep understanding of how activities and activity attributes sync to Engagio.
With Orchestrator, we have changed how you filter on activities by making them a first-class citizen in selectors.
Let's say you want to filter on accounts where there have been form submissions in the past week:
Just search for exactly what you are looking for! In this case, Fill out Form:
Notice that once you add the activity card to the selector, you can apply relevant constraints to that activity. In the case of a Form Fill Out, you can specify Client IP, Query Parameters, Referrer URL, and Webpage to get extremely targeted with the results you want to return.
Previously these activity attributes that are now constraints were accessed through additional "activity detail" filters, which could make finding the right attribute in the right context very difficult. Having the relevant constraints directly accessible from the activity card makes accessing the right attributes effortless.
We have also applied this change to how Activity Fields from admin are used.
Let's look at the Sales Engagement vs. Marketing Engagement Field. In admin it is represented as follows:
When referencing these activities in a selector, they are now represented just like other activity cards, where all of the relevant constraints are self-contained within the same activity card.
Any other Activity Fields you create will be represented this way.
While we have made working with activities when building filters, lists, and reports more intuitive through activity cards, when looking at activity data holistically from an analytics perspective--where you want to see information about the activities--you should still continue to add these broader bucketed fields to various grid views: