Switching experiences in Experience Targeting
- Topics:
- Experience Targeting
With Experience Targeting, you can control which experience visitors see as their profiles evolve.
The following list presents just a few scenarios in which visitors’ profiles can evolve, and you might want to present different content based on those changes:
Scenario | Details |
---|---|
Geographic Location | As visitors travel for business or pleasure, they might view your website or mobile app from different geographic locations. |
Customer Status | Visitors might be considered prospects before creating an account or purchasing a product. |
Category Affinity | The category affinity feature in Target automatically captures the categories visitors view and then calculates the visitors’ affinity for the category for targeting purposes. For example, visitors who viewed several articles on your website about a particular subject are presented with content related to that subject. |
Day of Week | As the weekend approaches, you might want to show visitors content about movies, dining, or other forms of entertainment. |
To use these capabilities in Target, it is important to understand the following information as you work with Experience Targeting activities:
-
Priority is controlled by the order of experiences, top to bottom. If a visitor qualifies for more than two audiences, that visitor receives content from the higher priority experience.
-
Visitors switch between experiences in an Experience Targeting activity if they start qualifying for the audience of a higher-priority experience.
For example, in the following activity setup, a visitor accessed your website from the United States and then traveled to Germany and visited your website a second time. During the first visit, this visitor qualified for Experience A (US visitors). After viewing your website from Germany, this visitor switched to Experience B (Germany visitors).
-
Visitors also switch between experiences if they stop qualifying for their current audience but start qualifying for a lower-priority experience.
-
If visitors stop qualifying for their current experience, and do not qualify for another experience, they see default content.
For example, in the following activity setup, a visitor accessed your website from the United States and then traveled to France and visited your website a second time. During the first visit, this visitor qualified for Experience A (US visitors). After viewing your website from France, this visitor remains in the original experience.
-
An experience targeted to “All Visitors” can be used as the last experience in the Experience Targeting activity to “catch” any visitors that have not qualified for any other experience. If an experience targeted to “All Visitors” is not the last in the order, other targeted experiences listed lower than this experience are still evaluated.
For example, in the following activity setup, a visitor accessed your website from the United States and then traveled to Germany and visited your website a second time. During the first visit, this visitor qualified for Experience A (US visitors). After viewing your website from Germany, this visitor remains in Experience A (US visitors).
If this is undesirable, you can create a new audience that is explicitly defined as the inverse of your targeted audience, as shown in the following example:
-
With a single-experience Experience Targeting activity, visitors remain in an experience even if they cease to qualify for the audience that put them in that experience.
If this is undesirable, you could create another experience targeted to the inverse audience (for example, “Not United States” as opposed to “United States”).
As another option, you could create an A/B Test activity targeted to your desired audience with 100% traffic allocation, as shown below:
-
The priority of experiences is defined by their order (top down) as they display in the Target UI.
This is important to keep in mind in scenarios where a visitor might qualify for more than one of your audiences. For example, if you have two experiences: one targeted to “United States” and one targeted to “New York,” a visitor located in New York qualifies for both audiences. Therefore, you must ensure that the “New York” experience is defined before the “United States” experience in the Target UI. This practice ensures that the more targeted “New York” experience has the higher priority, as shown in the following example:
Target
- Adobe Target Business Practitioner Guide Home
- Target release notes
- Introduction
- Introduction to Target
- Access Target from the Adobe Experience Cloud
- Target key concepts
- Understand the Target UI
- Target UI update FAQs
- Adobe Target AI Assistant
- Adobe Target welcome kit
- Target welcome kit overview
- Chapter 1: Introduction
- Chapter 2: Target at a glance
- Chapter 3: Develop your testing and personalization ideas
- Chapter 4: Tips for using Target
- Chapter 5: Inspiration for testing and personalization activities
- Chapter 6: Easily avoidable pitfalls
- Chapter 7: Create and run your first Target activity
- Chapter 8: Communicate your activity results
- Chapter 9: Next steps and resources
- Glossary
- How Target works
- Training and certification
- Training videos for Target Standard and Premium
- Target optimization and personalization FAQ
- Administer Target
- Implement Target
- Integrate Target with the Experience Cloud
- Adobe Analytics as the reporting source for Target (A4T)
- A4T overview
- Before you implement
- Analytics for Target implementation
- User permission requirements
- Create an activity that uses Analytics as the reporting source
- A4T support for Auto-Allocate and Auto-Target activities
- Use an Analytics tracking server
- A4T reporting
- Troubleshooting the Analytics and Target integration (A4T)
- A4T Frequently Asked Questions
- Expected data variances between Target and Analytics when using and not using A4T
- Integrate Target with Adobe Customer Journey Analytics
- Integrate Target with Adobe Journey Optimizer (AJO)
- Experience Cloud Audiences
- Integrate Target with Adobe Experience Manager (AEM)
- Integrate Target with Adobe Audience Manager (AAM)
- Integrate with Real-time Customer Data Platform
- Integrate Target with Adobe Campaign
- Adobe Analytics as the reporting source for Target (A4T)
- Activities
- Activities overview
- Target activity types
- A/B Test
- Auto-Allocate
- Auto-Target
- Automated Personalization
- Automated Personalization overview
- Random Forest Algorithm
- Create an Automated Personalization activity
- Upload data for the Target personalization algorithms
- Data collection for the Target personalization algorithms
- Estimate the traffic required for success
- Preview experiences for an Automated Personalization test
- Target Automated Personalization offers
- Manage exclusions
- Offer reporting groups in Automated Personalization
- Select the control for your Automated Personalization or Auto-Target activity
- Automated Personalization FAQ
- Troubleshoot Automated Personalization
- Experience Targeting
- Multivariate Test
- Recommendations activity
- Edit an activity or save as draft
- Priority
- Activity settings
- Success metrics
- Activity change log
- Troubleshoot activities
- Activity QA
- Audiences
- Experiences and offers
- Experiences and offers overview
- Visual Experience Composer (VEC)
- Visual Experience Composer overview
- Visual Experience Composer options
- Visual Experience Composer changes
- Include the same experience on similar pages
- Multipage activity
- Activity collisions
- Modifications
- Element selectors used in the Visual Experience Composer
- Mobile viewports for responsive experiences
- Visual Experience Composer best practices and limitations
- Troubleshooting the Visual Experience Composer
- Troubleshooting the Visual Experience Composer overview
- Troubleshooting the Visual Experience Composer and Enhanced Experience Composer
- Troubleshooting the Visual Experience Composer
- Troubleshooting the Enhanced Experience Composer
- Enabling mixed content in your browser
- Page modification scenarios
- Visual Editing Helper extension
- Visual Experience Composer helper extension
- Redirect to a URL
- Creating carousels that work in the Visual Experience Composer
- Form-Based Experience Composer
- Single Page App (SPA) Visual Experience Composer
- Offers
- Reports
- Recommendations
- Recommendations overview
- Introduction to Recommendations
- Plan and implement Recommendations
- Entities
- Criteria
- Criteria overview
- Create criteria
- Create criteria sequences
- Base the recommendation on a recommendation key
- The science behind Target’s recommendations algorithms
- Upload custom criteria
- Dynamic and static inclusion rules
- Use a backup recommendation
- Work with multi-value attributes
- Use Adobe Analytics with Recommendations
- Design
- Activity
- Recommendations as an offer
- Frequently asked questions
- Recommendations Classic documentation
- Troubleshoot Target
- Target APIs
- Resources and contact information