Audience UI

[roborourke]

The audience UI for analytics would be an interface on top of Pinpoint's audience segments.

We can provide an interface similar to that in Pinpoint whereby users can select from some filters based on the endpoint or user data eg. operating system / locale to create named segments. These segments could then be applied for any general analytics data we gather and display, additionally the segments could be used for features including:

• campaigns / push notifications
• experience blocks
• experiments

This is the pinpoint console UI for creating segments based on behaviours like activity and further filtering by endpoint attributes and demographics. I'm not sure if it allows you to use user attributes for filtering too.

[joehoyle]

Interesting, could we use this (actual UI) as a first EB "DMP"? cc @elodiebouneau ?

[grarighe]

I've added some examples of audience management features in this doc. There is so much to go through that I thought I'd share it in the meantime. You can also see examples of UI.

[roborourke]

@grarighe thanks for this, we went over it all yesterday and have some good ideas to move forward with, will be an update soon

[elodiebouneau]

@roborourke and I had a productive call yesterday to go over the details of audience UI. I will post notes and wireframes in the next couple of days to summarize our thoughts

[elodiebouneau]

Here is the draft mockup from our call @roborourke

A few notes:

• Title and Description should have max characters.
• Ability to select 2 audiences in the GB interface
• The order of the audiences expresses precedence if a user is in 2 difference audiences and they are both used in the same zone
• Audience names are unique; Descriptions are not.
• When user clicks on "edit" or "delete" and the audience is in use, a warning should be shown to let them know what will happen to the "experiences" currently on.

List of Rules we talked about:

• Client time
• Location
• OS
• Browser
• Device
• External Campaign (utm)
• First-time visitor
• Phase next: Pluggable sources (Weather, etc)

Remaining questions I would love your opinion on:

1. Should we put an audience size estimate in the main table?
2. Should we be able to "browse" old audience versions?
3. Should we have premade audiences? If so, which?

[elodiebouneau]

@roborourke What do you think? How can we make this better? Is there anything not needed? Anything missing?

[roborourke]

One idea I'd like to explore is how the interface could work in a similar way to the media modal popup. This would allow users to create and edit audiences in context whether it's in the gutenberg editor creating an experience block or the main audience management section.

Ability to select 2 audiences in the GB interface

Can you elaborate on this a bit regarding the context? I'm not sure we need to worry about this just yet, at least in the scope of this issue.

To answer your questions:

Should we put an audience size estimate in the main table?

Yeah, if we have that data cached. We can update the estimates async on a schedule.

Should we be able to "browse" old audience versions?

Not directly as it'd be too much data, perhaps just from the specific audience edit screen.

Should we have premade audiences? If so, which?

I think it's too early to tell. We could perhaps make a way to configure / register audiences through code though.

---

Re the mockup I think it captures the raw data and UI ok.

• showing the audience version is a really nice touch! I'd probably just do a number eg 1, 2, 3 as it'll be generated rather than explicitly written by someone
• we should probably make the "Add rule" link into a button, can iterate on that with some user tests
• I'm a bit worried the UI is squashed in that column, having more space would allow us to be more flexible and accommodate future changes more easily in a visually cleaner way
• given we'll likely store audiences as a post type to take advantage of revisions it'll be easier to use that as the default WP UI I think. The way audiences will be selected shouldn't be affected - I don't think we'd be using the default taxonomy picker at any rate

Cheers for pushing this forward. Going to research the Pinpoint audiences API some more to see if it's worth storing things there or if we'll have more flexibility rolling our own.

[elodiebouneau]

@karenames has been working on an update

[karenames]

I've worked on this a bit and tried to integrate your suggestions
@roborourke could you take a look at it and let me know your thoughts? I will then continue updating
https://whimsical.com/65bC9F8LJg3SqucvQ5jddK

[goldenapples]

This is looking really good! A few suggestions

In the list table, I think the "Last Modified" field is much less interesting to users than showing metrics about the audience, Depending on what's going to be available in the first release, could it show one of these instead of Last Modified:

• audience size (either the raw numbers, or graphs showing things like current percentage of user base, or growth over time)
• comparison to baseline in any vanity metrics available
• number of experiences served, or experiment results

I wonder if it's feasible to also show the actual audience definition logic, something like

Device == laptop AND Country == Australia

rather than depending on the user-supplied Description field.

I like the Edit Screen UI a lot, especially expanded like in the last Whimsical sketch. Actually, seeing the UI with that much space makes me think it would work well as a block editor interface. Is it worth mocking these audience selectors up as Gutenberg blocks to see what can be done graphically with them?

(Apologies for the drive-by comment, I was just reading through the issue and wanted to offer some suggestions!)