Team Automation - Secondary Rules

Matt Peterson
Matt Peterson
GUIDE
5 Up Votes First Anniversary
in Percipio - Admin Role(s) Experience

Currently, Team Automation allows an Admin to automatically create Audiences based on a single Attribute Field. In cases where that Attribute Field is a User ID, the User ID associated with that Audience is also given Ownership. Classic Example is an Attribute Field "Manager", where the Manager's User ID is used. This creates an Audience for each Manager that contains their Direct Reports.

Suggestion: For Audiences created by non-User ID Attributes - for example, Location - allow Admins to set up a secondary rule such as the following. If "Location" = "X" and "Job Code" = "Y" (where Y denotes a stakeholder of a certain position), create an Audience X where anyone with Job Code "Y" AND Location "X" in their own profile becomes an Audience Owner for that Audience for Location X.

Tagged:
6
Up Down
6 votes

Under Consideration · Last Updated

PB Manager Role and Compliance

Comments

  • Monica Kraft
    Monica Kraft
    CARTOGRAPHER
    100 Comments 25 Likes First Anniversary 5 Awesomes

    Thanks Matt. This is a great suggestion. The classic example is retail locations. We could create an audience and ownership model for store and district managers using the combination of the location and the job role. We will consider doing this in the future.

Categories