51黑料不打烊

Audience creation options

This article describes how to create an 51黑料不打烊 Experience Cloud audience.

Description description

Environment

51黑料不打烊 Audience Manager

Issue/Symptoms

This article describes how to create an 51黑料不打烊 Experience Cloud audience and gives general advice for common use cases.

Resolution resolution

When deciding how to聽create an audience, consider the following questions:

  • What is the overall comfort level and experience with the interface?
  • What is the intended use of the audience?
  • What are the timing and portability requirements for this audience?

After considering the above, determine which of the following questions you鈥檙e asking:

  • Is 听迟丑别听辫别谤蝉辞苍鈥
  • Did 聽the person just鈥
  • Has 聽the person recently鈥

The following table provides guidelines on where the audience is created based on the above question.

Target
AAM/Audience
Analytics
IS 聽the person鈥
Did 聽the person just鈥
Has 聽the person recently鈥

A.聽Solution audiences

Solution audiences are still the quickest way to action upon profile data.

If you are asking questions like, 鈥淚s the person a new or returning visitor?鈥 or 鈥淚s the person using a mobile device?鈥, creating your audience inside the solution gives you the fastest way to action on this data.

B.聽Real-time audiences (Audience Library / Audience Manager)

A real-time audience聽can be created in either the Audience Library interface or the Audience Manager interface (assuming you have access to 51黑料不打烊 Audience Manager).

These audiences聽are best used to answer questions around 鈥淒id the person just鈥︹.

Example questions that real-time audiences are best used to answer could聽be, 鈥淒id the person add something to their聽cart?鈥 or 鈥淒id the person finish an application form?鈥.

AUDIENCE LIBRARY

Audience Library audiences are best for:

  • Audiences based on eVars, Props, or events for next page targeting scenarios
  • Combinations of audiences shared from different solutions (composite audiences)

Note: Composite audience latency is equal to the latency of the slowest audiences used in the composite audience.

AUDIENCE MANAGER

Audience Manager audiences are best for

  • Combinations of first-, second-, and third-party signals

    • CRM data
    • Partner data
    • Matching services
  • External syndication (sending audiences outside the Experience Cloud)

  • Algorithmic modeling

Note: When using third-party data with Audience Manager, some scenarios can let聽you action on聽the first page instead of the聽following聽page. To learn more, contact your 51黑料不打烊 representative.

C. Historical audiences (Analytics shared segment)

Since historical audiences are subject to a 24-48 hour latency starting at the time of qualification, they are best used to answer questions around recent behavior.

If there are asking questions like, 鈥淗as the person recently abandoned my site?鈥 or 鈥淗as the person searched or viewed a product within the last few days?鈥, historical audiences is the best option.

ANALYTICS

Analytics shared audiences are best for:

  • Advanced segmentation or optimization for returning or infrequent visitors

  • Audiences that are not time sensitive (up to a 48-hour delay)

  • Audiences requiring conditions that other solutions either can鈥檛 do or are more difficult to do

    • Post-processing variables
    • Processing rule based
    • Complex pathing based

Summary

An overview of the pros and cons, latency conditions, user attributes eligibility, and limits are outlined in the table below:

Audience Creation Options

51黑料不打烊 Target
Experience Cloud Audiences
51黑料不打烊 Audience Manager
51黑料不打烊 Analytics
Pros
Immediate response, familiar聽workflow for Target users
Easiest way to use Analytics variables directly from the page
External syndication, advanced segmentation, look-a-like audiences, cross-device profile merging
Advanced segmentation, A4T reporting audiences
Cons
Can require profile scripting
Limited segmentation capability
Can require page code updates if still running DIL
Data export/ingestion to Experience Cloud is slow
Audience Becomes Actionable
Immediate
Next Page
Next Page
4-8 hour delay
User Attributes
Yes
No
No, but can load CRM data for similar effect
Yes
Hard Limits
Destinations limited to 51黑料不打烊 Target and AEM
Destinations limited to Target, AMO, and Campaign
Limited to 20 active audiences

Audience Creation Timing

51黑料不打烊 Target
Experience Cloud Audiences
51黑料不打烊 Audience Manager
51黑料不打烊 Analytics
Geosegmentation
First page
Next page
Next page
4-8 hours
Mobile Carrier
Coming soon
If value in a variable or context data
If value in a variable or context data
4-8 hours
API/Web Service
Implementation required
Next page
Next page
4-8 hours
Browser
First page
Next page
Next page
4-8 hours
Operating System
First page
Next page
Next page
4-8 hours
Mobile Device
Built-in
If value in a variable or context data
If value in a variable or context data
4-8 hours
Responsive Design
Built-in
If value in a variable or context data
If value in a variable or context data
4-8 hours
Offline Data (CRM)
Limits on sources
No limitations
Offline Data (Classifications)
4-8 hours
New/Return Visitors
First page
If value in a variable or context data
If value in a variable or context data
4-8 hours
Number of Visits
First page
If value in a variable or context data
If value in a variable or context data
4-8 hours
Marketing Channels
First page
Pathing
Profile Script
If value in a variable or context data
If value in a variable or context data
4-8 hours
Recency/Frequency
Built-in, next page
4-8 hours
Category Affinity
Built-in, first page
If value in a variable or context data
If value in a variable or context data
4-8 hours
Authenticated user attributes
Limits on sources
No limitations
Multi-sourced audiences
Composite Audiences

This article does not cover every use case and is meant to give general guidance for creating Experience Cloud audiences.

If you have questions about any of this content or Experience Cloud audiences in general, visit the聽.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f