Site Pages
- Topics:
- Audiences
You can target visitors using Adobe Target who access a specific page on your site.
-
In the Target interface, click Audiences > Create Audience.
-
Name the audience and add an optional description.
-
Drag and drop Site Pages into the audience builder pane.
-
Click the Select drop-down list, select one of the following options, then configure the rule as desired.
The available options and evaluators in subsequent drop-down lists in the rule vary depending on which option you choose. The following illustration shows the available options if you choose Current Page:
The following options are available in the initial drop-down list when you choose Select.
-
Current Page: The page the user is viewing.
The following options are available in the second drop-down list if you choose this option:
- URL (For more information about how Target evaluates URLs, see Targets and audiences FAQ.)
- Domain
- Query
- Subdomain
- Top-Level Domain
- Path
- Hash (#) fragment
-
Previous Page: The page the user was viewed before clicking to the current page. The user must click from the previous page to the current page for the page to be tracked. The previous page is not tracked if the user types a new URL in the browser. The actual content of this page depends on the design of your site. For example, if the current page displays information about a specific product, the previous page might be a category page where the visitor selects the specific item. For example, a page displaying several cameras of a certain type, or it might be the home page that leads to the final page.
The following options are available in the second drop-down list if you choose this option:
- URL (For more information about how Target evaluates URLs, see Targets and audiences FAQ.)
- Domain
- Query
- Subdomain
- Top-Level Domain
- Path
-
Landing Page: The landing page is the first page the visitor sees when accessing your site. For example, if the visitor clicks a link on Google that leads to a category page, then the category page is the landing page. If the link leads to your home page, then the home page is the landing page. The landing page is remembered for the visitor’s session. You can target deeper in the site based on what the visitor’s landing page was in this session.
The following options are available in the second drop-down list if you choose this option:
- URL (For more information about how Target evaluates URLs, see Targets and audiences FAQ.)
- Domain
- Query
- Subdomain
- Top-Level Domain
- Path
- Hash (#) fragment
NOTE
Thelanding.url
object is reset on a subdomain change or direct URL replacement. -
HTTP Header: This option evaluates the information in the HTTP header of the Target request. For example, if the HTTP header contains language information, you could create a rule that contains the
Accept-Language: es
condition to target visitors who access the page in Spanish.The following options are available in the second drop-down list if you choose this option:
- Accept
- Accept-Charset
- Accept-Encoding
- Accept-Language
- Authorization
- Cache-Control
- Connection
- Content-Length
- Content-MDS
- Content-Type
- Date
- Expect
- From
- Host
- If-Match
- If-Modified-Since
- If-None-Match
- If-Range
- If-Unmodified-Since
- Max-Forwards
- Pragma
- Proxy-Authorization
- Range
- Referrer
- TE
- Upgrade
- User-Agent
- Via
- Warning
If you chose Current Page, Previous Page, or Landing Page, the Domain and Query options are available. Consider the following when choosing these options:
-
Domain: The full domain of the page. When specifying a domain, best practice is to use “contains.” For example, “Domain equals facebook.com” does not accept
m.facebook.com
orwww.facebook.com
. “Domain contains facebook.com” accepts any variant of facebook.com. -
Query: The content of the URL after the first question mark (?).
foo.html?e0a72cb2a2c7
-
-
(Optional) Set up additional rules for the audience.
-
Click Done.
You can also create site pages audiences using you own “user-defined query parameter” or “user-defined header.”
Use a:
- Query parameter if the rule selected by the user is Current Page, Landing Page, or Previous Page
- Header if the rule selected by the user is an HTTP header
Troubleshooting
-
For landing page audiences to function properly, requests must have the
mboxReferrer
parameter set (for the Delivery API thecontext.address.referringUrl
parameter) that the at.js JavaScript library takes from the page using thedocument.referrer
attribute. ThisHTMLDocument
attribute returns the URI of the page the user has navigated from. The value of this attribute is an empty string when the user navigates to the page directly (not through a link, but, for example, via a bookmark).If this behavior does not match your requirements, consider performing one of the following actions:
- Pass mbox parameters to Target to be used for targeting purposes.
- Use an A/B Test activity instead of a landing page activity. A/B Test activities do not switch experiences for the same visitor.
- Use a visitor profile instead.
-
When using “starts/ends with” evaluators on strings containing commas, these strings are evaluated as an array of values, in which each value separated by comma is evaluated. For example if you have the value for a header:
Accept-Language: en,zh;q=0.9,en-IN;q=0.8,zh-CN;q=0.7
it qualifies for conditions like:- starts with zh,
- starts with en,
- ends with 0.7,
- ends with 0.8.
Training video: Creating Audiences
This video includes information about using audience categories.
- Create audiences
- Define audience categories
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
- 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