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?
Audience XYZ is built as ( eVar1 contains "aem" AND event1 )
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.