Customer Issue
We recently blocked a user who had created a number of audiences, and all those audiences now show zero users.
Audience counts showing the wrong number of users. In audiences shows a lower count, but in delivery shows as the full count.
Environment
- Studio | People | Audiences
Issue Details
In some areas, audiences created by a restricted user show only users in the creators audience permissions.
As blocked users do not have permissions for any audiences, when a user is blocked or demoted from a Studio user to a Member, any audiences they have created may show as having no users and will display (0) next to the audience name.
Example scenario 1 - audience created by a restricted user:
- A Community Admin with permissions to manage users located in London creates an audience containing these users.
- A Brand Super Admin edits the audience to add a person to the audience.
User Samantha Corder is not in the Community Admin's permitted audiences. This displays with a (0) next to their name and the total 13 users only includes London users. - Check the Preview tab.
The audience contains 14 users, including Samantha Corder. - Assign this audience to a campaign.
13 shows for the audience, but 14 shows as total users.
The Review tab shows 14 users.
Example scenario 2 - audience created by a blocked user:
- Assign an audience to a campaign that was created by a blocked user.
Audience shows 0 users but Plan shows users will be targeted. - Check the Review tab.
The full scope of the audience is shown.
Resolution
The audience can still be used since this is a visual issue, however, duplicating the audience as a Brand Super Admin will also fix the issue as the audience will now be created by an active admin.
Please check the current status of this issue on the Known Issues Tracker. (Issue ID: CSUP-2362)
Comments
3 comments
Please see the "Resolution" section of this article for an update on interim solution to this issue.
Product Engineers have now resolved this issue. Audience user count's should now appear accurately.
We regret to inform you that we have rolled back the recent fix for this issue. The fix was causing the Deliver page to load slowly for Studio users with large audience restrictions. We are working on a solution and will update you on the re-release timeline. In the meantime, please refer to the Issue Details and Resolution section of this article for available workarounds.
Article is closed for comments.