Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

How To Deploy a Test on ANY Landing Page

jeremytripp
Level 1
Level 1

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?

entry page Target
1 Accepted Solution
jeremytripp
Correct answer by
Level 1
Level 1

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.

View solution in original post

3 Replies
ryanr701
Employee
Employee

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?

jeremytripp
Correct answer by
Level 1
Level 1

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.

View solution in original post

Amelia_Waliany
Community Manager
Community Manager
Thanks @jeremytripp for following up here and sharing more about your experience and solution!