Tailoring the right content to the right users starts 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: This is the complete list of conditions, however, you won't see every condition on any site. Some conditions are only available for websites or apps.
|Who? (Targeting by User Properties or Session Behavior)|
|Audience||Users who belong (or do not belong) to a Dynamic Yield audience created in the Dynamic Yield site. By targeting based on Audience you can leverage historical behavior (for example, users who purchased twice in the past year) vs. only targeting by current session behavior, and several additional audience conditions.|
|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 - measured by their interactions with products (views, add to cart, and purchase events) - in a specific product property (such as blue color or show category) 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 (since implementation of Dynamic Yield script on your site). They will meet this condition throughout the first session. User identification is done by the Dynamic Yield cookie (and a fallback of local storage), so new users are users that do not have a cookie at the beginning of the session. Learn more about Users 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 who visited specific pages on your site.|
|Previous Page URL||Users who visited a specific page immediately prior to the current page.|
|Landing URL||Users whose first pageview in the current session was a specific URL.|
Users who made a specified number of product views during the current session. You can consider all product views, or just products with a specific property (for example, products that belong to the category "women").
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 just 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 an additional property, speak to your Customer Success Manager.
|Products Purchased||Users who made a specified number of purchases during the current session. You can consider all purchases, or purchases of products with specific properties.|
|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. 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? (Targeting 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).|
|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).|
|Page URL||The current page is a specific URL or a substring of a URL.|
|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)||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)||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? (Targeting 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.
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.