Audiences by report Suite - Analytics Dimensions - Duplicate Audiences?

Great, thanks Jantzen

Hi Jantzen.Belliston ,

I am confused with "Audience Library audiences are created at the experience cloud level, meaning they span report suites."

If an audience is created for report suite A with a condition "pageName contains Homepage", will that criteria be tied to report suite A data or all other report suites existing in the Adobe Experience Cloud will be evaluated too?

Hi Andrey Osadchuk​,

All other report suites will be evaluated too. With a real-time audience created in the Audience Library interface, you are creating a set of rules that will sit at the Experience Cloud level. This is how they are able to be qualified for in real time. There is no concept of report suites. To have that concept would require that the audience be subject to Analytics processing delays and thus not be real-time.

This is why if you tried to create the same rule (pageName = home) using two different report suites as reference, you would receive an error. The report suite selector is there for context only. Whatever is selected in the dropdown is used to pull back the friendly names of the variables. This way you would see something like "Subscriptions (event 3)" rather than just "event 3".

Hopefully this helps,

Jantzen

Let's consider the following scenario:

Report Suite A

• eVar1 is populated with onsite search keywords
• event1 counts onsite searches

Report Suite B

• eVar1 is populated with article titles
• event1 counts form submissions

Audience created in Audience Library

• Audience XYZ is built as ( eVar1 contains "aem" AND event1 )

Journeys:

• Visitor Jantzen came to site A, looked for "aem 6.3".
• Visitor Andrey came to site B, viewed an article "What's new in AEM 6.3" and submitted a form to get subscribed to a newsletter.

As a result, the Audience XYZ will contain both visitors. This looks confusing because the author could be thinking either about Searchers on site A or Engaged visitors on site B. The confusion was partly because while the Audience creation the author chose Dimension (eVar) and Metric (event) names rather than variables. Another factor causing confusion is that in the right-hand side area the Audience Summary was confirming the criteria is linked to the chosen report suite:

(Raw Analytics Data using Report Suite A) Visitors where Onsite Search Keywords ( evar1 ) contains aem and (Raw Analytics Data using Report Suite A) Visitors where events matchesregex Searches

If the above is accurate, it means that if there is a necessity to build an Audience tied to a report suite SDR, the report suite ID should be a part of the segmentation criteria. Unfortunately, it is missing in the Dimension drop-down menu.

I wonder how many users realize how Audiences work.

Hi Andrey,

The scenario you've pointed out is exactly why we recommend customers have a standard data model across all their web properties. In your above scenario, your audience size listed in Audience Library would be inflated and, if using Target, you might present an experience to someone that hasn't qualified in the way you thought.

A solution for you would be to add additional conditions to the real-time audience that would limit the qualifying audience to the web property you were targeting. You should be able to use the Page URL to accomplish this.

Cheers,
Jantzen