Skip to main content
Sep 15, 2020 7:00 PM UTC
Solved

How To Deploy a Test on ANY Landing Page

I operate an eComm single page app website where users come in "sideways" (via category or product pages from bookmarks or search engines) just as much as they enter through the homepage. How can I set my page delivery settings in a standard A/B test to ensure my test deploys on any entry/landing page, not just the default page setup under Page Delivery?

 

I assumed setting an OR template rule with 'domain contains mydomain.com' would account for this, but no tests fire when I enter via any page other than the one set as my default page, even though I see Target being loaded via Launch. Any advice?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
jeremytrippAccepted solution
Sep 16, 2020 1:13 AM UTC

Figured it out. For future searchers who operate in an SPA, you'll need to set any code or events you wish to fire on any entry page as a Page Load Event rather than firing on a specific View. This along with setting a template rule in Page Delivery to "domain contains yourdomain.com" does the trick. It seems like the Page Delivery template rules don't extend to Views -- or at least they don't for me (could always be a self-inflicted implementation issue). Anyway, hope it helps others.

3 replies

Adobe Employee
Sep 16, 2020 12:20 AM UTC

Hi @jeremytripp, 

A template rule with an OR condition like you described should be what you want. Are you seeing a Target call being made on each page? Is there any other audience condition in place?

Translate
jeremytrippAuthorAccepted solution
Sep 16, 2020 1:13 AM UTC

Figured it out. For future searchers who operate in an SPA, you'll need to set any code or events you wish to fire on any entry page as a Page Load Event rather than firing on a specific View. This along with setting a template rule in Page Delivery to "domain contains yourdomain.com" does the trick. It seems like the Page Delivery template rules don't extend to Views -- or at least they don't for me (could always be a self-inflicted implementation issue). Anyway, hope it helps others.

Translate
Amelia_Waliany
Adobe Employee
Adobe Employee
Oct 14, 2020 2:59 PM UTC
Thanks @jeremytripp for following up here and sharing more about your experience and solution!
Translate