I'm in the process of setting up a marketing Cloud Audience that is defined by raw analytics data dimensions (ie. evar66 contains "+").
This process forces you to identify a report suite, which leads me to believe i need to create the duplicate Audiences for each of the report suites where I want to use this audience. The problem is that when I do that, i get an Error message that states "Segment 'audiencName' exists with the same rule for the same data source and same merge rule."
I have a feeling that although you define a report suite in the audience rules, when an audience definition (excluding report suite) exactly matches an existing one, it sees it as a dupe.
Has anyone encountered this yet? Is it possible that although the Audience is defined by a specific report suite it actually transcends all report suites?
The report suite selection tool is used for an API call to pull back the variable names for that report suite. It is simply there for your convenience. As you pointed out, you are not able to create multiple segments that duplicate the audience. Audience Library audiences are created at the experience cloud level, meaning they span report suites.
We will be making a change to the UI soon that should hopefully make this more clear. Watch for a post from me in the Audiences community in the next week or so. I'll also promote the post on our Twitter handle @AdobeExpCloud
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.
Let's consider the following scenario:
Report Suite A
Report Suite B
Audience created in Audience Library
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 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,
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?
Great, thanks Jantzen