Tailoring the right content to the right users begins with targeting. When you create an experience, you can target it by user properties (such as device type or geolocation), page properties (such as page type or URL), or dates.
Note: While this table includes the complete list of targeting conditions, no section will include them all. For example, some conditions are only available for websites and others only for apps.
| Who? (Target by user properties or session behavior) | |
|---|---|
| Audience | Users who belong (or do not belong) to a Dynamic Yield audience. For example, you can target based on historical behavior (say, users who purchased twice in the past year) vs. targeting by current session behavior. |
| Shared Audience | Users who belong to a Dynamic Yield audience that has been shared from a different site. |
| User Affinity | Users who expressed high interest in a specific product property (such as blue color or show category). Interest is measured by interactions with products, such as views, add to cart, and purchase events in the current and past sessions. Learn more about affinity-based audiences. |
| New User (first session) | Users who are currently in their first-ever session on your site (since the Dynamic Yield script was implemented). Users meet this condition throughout this first session. User identification is done by the Dynamic Yield cookie (and a fallback of local storage), so new users are users that don't have a cookie at the beginning of the session. Learn more about user identification in Dynamic Yield. |
| Active Consent | Targets users based on their Cookie Consent status. True means they gave consent, while False means they haven't. |
| Cookie | Users with a specific value in a specific browser cookie. |
| Number of Pageviews | Users who made a specific number of pageviews during the current session. |
| Screen Viewed (mobile) | Users who visited a specific screen on your mobile application. For details, see the pageview APIs in the iOS API Reference or the trackPageView APIs in the Android API Reference. |
| URL Visit | Users who visited specific pages on your site. |
| Previous Page URL (Web Personalization only) |
Users who visited a specific page immediately before the current page. Based on context.page.referrer |
| Previous Screen (App Personalization only) |
The previous page is a specific URL or a substring of a URL. |
| Landing URL | Users whose first pageview in the current session was a specific URL. |
| Product Viewed |
Users who made a specified number of product views during the current session. You can consider all product views, or only products with a specific property (for example, products that belong to the category "Accessories"). Note: A limited set of properties is available here. You can view which properties are available at the top of your Product feed page. To add an additional property, speak to your Customer Success Manager. |
| Products Added to Cart |
Users who triggered a specified number of Add to Cart events during the current session. You can consider all Add to Cart events or only events that have a specific property. Note: A limited set of properties are available here. You can view which properties are available at the top of your product Feed page. To add properties, speak to your Customer Success Manager. Not available for Financial Institution sections. |
| Products Purchased |
A user who purchased a specific item at least the specified number of times during the current session. You can consider all purchases, or purchases of products with specific properties. Not available for Financial Institution sections. |
| Product Submitted (Financial Institutions only) |
A user who submitted an application at least the specified number of times during the current session. You can consider all submissions or only submissions of products with specific properties. |
| Application Started (Financial Institutions only) |
Users who started an application, and triggered a specified number of Add to Cart events during the current session. You can consider all Add to Cart events or only events that have a specific property. Note: A limited set of properties are available here. You can view which properties are available at the top of your product feed page. To add properties, speak to your Customer Success Manager. |
| First-Party Data |
Users with a specific property based on first-party data (such as your CRM). This data must be onboarded to Dynamic Yield. See onboarding by CSV or onboarding by API. |
| Event Triggered | Users who fired a specific event during this session, regardless of the event properties. |
| Event Triggered by Property | Users who fired a specific event with a specific property during the current session. Event properties can be added to any event (for example, an event of rating a product can include a property of the number of stars). |
| Goal Conversion | Users who have fulfilled the conditions of a defined goal. For example, a user who triggered a specific event. |
| Unit Click | Users who have clicked on a Dynamic Yield Unit during the current session. |
| Dynamic Link Click | Users who have clicked on a specific Dynamic Link defined in this Dynamic Yield account. |
| URL Parameter in Session | Users who visited a page that contains a specific URL parameter in the current session. |
| Traffic Source | Users arriving via a specific traffic source such as Direct, Paid Search, Referral, Search or Social. For more details, see Traffic Sources. |
| Referring Domain | Users who were referred to your site by a certain domain. |
| Elapsed Time | Users who meet certain time conditions since their first visit, the previous visit, or triggered a specific event. For example, you can target visitors who haven't made a purchase in the past two weeks, or visitors whose previous visit was yesterday. The definition of a day for this condition is when the time zone of the site (defined in the General Settings screen) reaches midnight. |
| Device Category | Users visiting your site on a desktop, tablet, or smartphone. |
| Operating System | Users with a specific operating system, such as iOS 10, Windows 10, or Linux. |
| Device Brand | The manufacturer of the phone or tablet being used (for example, Samsung or Apple). |
| Browser | The browser being used (for example Chrome or Firefox). |
| Screen Resolution | Users with Low (1024px and below), Medium (1025-1365px), or High (1366px and above) screen resolutions. |
| User Agent | The user's current user agent. A user agent is a string that identifies the browser and operating system to the web server. |
| Country | The country in which the user is currently located. |
| Region/State | The region and US state in which the user is currently located. |
| City | The city in which the user is currently located. Only major cities are supported. Location is determined by IP, and accuracy varies between 70%-90%. |
| Weather | The current or forecasted weather conditions and temperature in the user's current location. |
| Custom attributes | For API campaigns, send any attribute in the pageAttributes object inside the choose request. For example: UTM params |
| Where? (Target by page properties) | |
| Page Type | The current page is either homepage, category page, product page, or cart page. |
| Category Page | The current page is a category page or a specific category page (such as Jackets or Shoes). |
| Application Page (Financial Institutions only) |
The current page is an application page, with any product; or uses "contains" to target a specific string in the context attribute (for example, if the cart contains SKUs "123, 345, 567", you can set a condition of "contains "23" to target the experience). |
| Cart Page |
The current page is a cart page, with any product; or use "contains" to target a specific string in the context attribute (for example, if the cart contains SKUs "123, 345, 567", you can set a condition of "contains "23" to target the experience). Not available for Financial Institution sections. |
| Current Page URL (Web Personalization only) |
The current page is a specific URL or a substring of a URL. Based on context.page.referrer |
| Current Screen (App Personalization only) |
The current screen a user is on. Based on context.page.location |
| URL Parameter | The current page has a specific URL parameter. |
| Custom Evaluator | The specified evaluator is true. Evaluators are custom conditions that can be defined under Assets › Evaluators. |
| Product Page | The current page is a product page or a specific product page. (for example, SKU=12345) |
| Product Popularity (Views) | Pages of products that have been viewed a specific number of times over a specific time frame (for example, at least 100 times in the past day). |
| Product Popularity (Purchases) | Pages of products that have been purchased a specific number of times over a specific time frame (for example, fewer than 50 times in the past week). |
| Current Screen (Mobile SDK only) |
A screen in a mobile application is the equivalent of a page in a website. The screen name is defined in mobile API calls in the uniqueID parameter of the pageview or trackPageView APIs. For details, see the pageview APIs in the iOS API Reference or the trackPageView APIs in the Android API Reference. |
| Previous Screen (Mobile SDK only) |
A screen in a mobile application is the equivalent of a page in a website. The screen name is defined in mobile API calls in the uniqueID parameter of the pageview or trackPageView APIs. For details, see the pageview APIs in the iOS API Reference or the trackPageView APIs in the Android API Reference. |
| When? (Target by time of day or date) | |
| Date | Select dates or date ranges (by user or site timezone). |
| Day of the Week | Select specific days (such as Sunday or Saturday). Useful for weekend vs. weekday experiences. |
| Time of Day |
Specific time ranges throughout the day (by the user or site timezone). Note: Dynamic Yield does not adjust the time based on Daylight Savings Time. |
Note: If you want to create a condition that is not included in the list, you can use JavaScript to create a custom condition called an Evaluator. For details, see Evaluators.
Add a Targeted Experience
Each campaign can include several experiences (for example, a hero banner can provide different experiences for new vs. returning users). To add additional experiences with different targeting, click the "+" icon at the left of the experience.
If the targeting conditions of multiple experiences are met - only the experience defined with the highest priority is served. For example, if a campaign has 2 experiences, for mobile users and search traffic (sorted in that order), and a mobile user comes to your site from Google - only the "Mobile Users" experience will be served.
Note: If the user does not meet the targeting conditions of any of the experiences, the campaign is not served at all for this user.