Page Delivery Tab Not Working

Avatar

Avatar
Give Back 5
Level 2
harsingh91
Level 2

Likes

8 likes

Total Posts

38 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Ignite 3
Give Back
Ignite 1
View profile

Avatar
Give Back 5
Level 2
harsingh91
Level 2

Likes

8 likes

Total Posts

38 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Ignite 3
Give Back
Ignite 1
View profile
harsingh91
Level 2

18-12-2017

Hello All,

I am trying to apply my AB Test scenario to my full website by using Add template rule in Page Delivery Section in Configure Tab.

It is working fine for my local environment, when I setup rule a page URL and a URL starts with or contains xyz.

But, when I am trying to setup same scenario for my project Dev and Publish env., it is not working and experience only coming on initial page URL.

Please let me know, what I am doing wrong ?

Thanks in Advance,

Harshit

Replies

Avatar

Avatar
Boost 1
Level 1
jasonj19903207
Level 1

Likes

2 likes

Total Posts

2 posts

Correct reply

0 solutions
Top badges earned
Boost 1
View profile

Avatar
Boost 1
Level 1
jasonj19903207
Level 1

Likes

2 likes

Total Posts

2 posts

Correct reply

0 solutions
Top badges earned
Boost 1
View profile
jasonj19903207
Level 1

28-06-2018

Having a similar issue. Trying to leverage Page Delivery functionality to deliver the experience to multiple pages but the experience only appears on the landing page.

Avatar

Avatar
Give Back 50
Employee
Shruthi_N
Employee

Likes

272 likes

Total Posts

236 posts

Correct reply

64 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile

Avatar
Give Back 50
Employee
Shruthi_N
Employee

Likes

272 likes

Total Posts

236 posts

Correct reply

64 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile
Shruthi_N
Employee

04-07-2018

Hi Harshit, Have you tried running the mbox trace to verify that you are indeed qualifying for the activity on the other pages? If yes, it could be that the html page structure is different on the other pages so target is unable to apply the changes. If you are on at.js you can append url parameter mboxDebug=console and see the console in the developer tools to see if there are selector issues.

Eg.https://test.businesscatalyst.com/about-us?mboxDebug=console . (If you are using mbox.js, then use parameter _AT_Debug=console)

For steps to run the mbox trace please refer to Troubleshooting Content Delivery

Avatar

Avatar
Boost 1
Level 1
jasonj19903207
Level 1

Likes

2 likes

Total Posts

2 posts

Correct reply

0 solutions
Top badges earned
Boost 1
View profile

Avatar
Boost 1
Level 1
jasonj19903207
Level 1

Likes

2 likes

Total Posts

2 posts

Correct reply

0 solutions
Top badges earned
Boost 1
View profile
jasonj19903207
Level 1

10-07-2018

Turns out the problem for me was that all the code I had added in the custom code section was set to save in the head. When I unchecked that box, the test seems to be carried over across all the pages. I hope this helps.