Experience Editor: Display Step

The display step is present in the editor for all Experiences of the Lytics provider. Use the Display Step to set where and when the Experience will show up for your users. Set rules for which URL(s) an Experience can be displayed on, the triggers for displaying it, the frequency with which it appears, and the date range during which the Experience is available to show.

Appears on rules are an optional tool used to specify which webpages within your site the Experience will (or will not) be shown on. This can be a fixed list of pages or expressions that match many pages. There are four URL-matching strategies offered, and rules can be used in combination.

• URL Contains – The text specified must be included in the URL.
• Simple Match – A fuzzy match that removes the URL protocol and query string before matching.
• Exact Match – The URL must match what is typed exactly, including protocol and query parameters.
• Regular Expression – A regular expression (sometimes referred to as Regex) to be executed client-side with JavaScript for complex matching requirements.

Each of these URL-matching strategies can be used to create a rule determining when the Experience is shown with Show on selected, or to specify the cases where the Experience should not be displayed with Hide on.

Consider the following use cases, and some suggested solutions using the appears on rules.

Solution: Show on a Simple Match for www.lytics.com.

Displays for:

• https://www.lytics.com
• http://www.lytics.com
• http://www.lytics.com?ad_campaign=1ed387faed

Does not display for:

• http://www.lytics.com/blog
• https://activate.getlytics.com

Solution: Show on URL Contains /blog/

Displays for:

• http://www.lytics.com/blog/
• http://www.lytics.com/blog/some-post-in-the-past
• https://www.lytics.com/blog/tag/customer-data-platform?referrer=thegreatgoogle

Does not display for:

• https://www.lytics.com/
• http://www.lytics.com/careers

Solution: Show on an Exact Match for https://www.lytics.com/resources?id=a763efd12c

Displays for:

• https://www.lytics.com/resources?id=a763efd12c

Does not display for:

• http://www.lytics.com/resources?id=a763efd12c
• https://www.lytics.com/resources?id=a763efd12c&something=that-will-404

Solution: Show on a match for the Regular Expression \/integrations\/.+?\?.*?ref=our_partner

Displays for:

• http://www.lytics.com/integrations/campaignmonitor?ref=our_partner
• http://www.lytics.com/integrations/campaignmonitor?session=125929&ref=our_partner
• http://www.lytics.com/integrations/adroll/?ref=our_partner
• https://www.lytics.com/integrations/segment?ref=our_partner&qp=true

Does not display for:

• http://www.lytics.com/integrations/campaignmonitor?ref=some_stranger
• http://www.lytics.com/integrations?ref=our_partner
• http://www.lytics.com/blog/adroll?session=125929&ref=our_partner

Solution: Use two rules in combination. Show on URL Contains lytics.com Hide on URL Contains /careers

Displays for:

• http://www.lytics.com/blog/
• https://www.lytics.com

Does not display for:

• http://www.lytics.com/careers
• http://www.lytics.com/careers/content-writer

The Advanced Display Options allow you to respond to the user's interaction with your site, using the state of their active web session to determine when an Experience is displayed. These are all optional and can be used in combination.

• Show after x page views – Do not show the Experience until the requisite number of pages have been visited.
• Show after x seconds – Do not show the Experience until the requisite number of seconds in the session have elapsed.
• Show after x% page scroll – Do not show the Experience until the user has scrolled a certain percent of the way down the page.
• Show on exit intent – Do not show the Experience until the user is about to abandon the site.

When using triggers in combination, note that the conditions function as an ALL conditions met, not ANY condition met. If you set an Experience to Show after 5 page views and to Show after 70% page scroll, when your user scrolls to 70% of the third page, the Experience will not show because only one of the two conditions have been met.

• Show up to x times per user, ever – After the specified number of times displaying the Experience, suppress its display forever for the current user.
• Show up to x times per user per session – After the specified number of times displaying the Experience, suppress its display for the current user. This count resets when the user ends their current session.

If you set an Experience to Show up to 5 times per user, ever and Show up to 2 times per user per session, and a user is shown the Experience twice each on their first two sessions, for their third session they will be shown the Experience for the final time.

If you set an Experience's frequency to Show up to 2 times per user per session and a trigger of Show after 5 page views, your user will see the Experience upon reaching the sixth page, again on reaching the seventh page, and not again during their session.

• Hide after x clicks – Hide the Experience after the user has clicked the call-to-action the specified number of times.
• Hide for x time – How long an Experience should remain hidden, in seconds/hours/days/weeks.
• Hide permanently – Instead of hiding an Experience for a set amount of time, never show it again for the current user.

These are the same options as above, but applied to when the user has seen the Experience but not clicked the CTA.

Set the date range for when the Experience will be shown to your users. The start date will be populated with the current day, so that your Experience will start immediately without you needing to set anything.

You can set a start date in the future and Activate the Experience ahead of time; it will have a "scheduled" status and then switch automatically to "active" on the start date.

The end date is not required. If you do not set an end date, the Experience will run indefinitely as long as it is active. End dates cannot be in the past, nor can they precede the start date.

The date range is inclusive, so if you set a start date of 3/21/2022 and an end date of 3/23/2022, the experience will run for 3 days. On 3/24/2022, the Experience will switch from "active" status to "ended" on its own and users will no longer see it.