Anyone else having problems with redirect tests?

[#1]

Hi - we've noticed that redirect tests no longer work properly with the Chrome browser - the latency is so bad it's unusable. We never had this problem in the past, so wondering is anyone else has this problem?

thank you, Richard 

[#2 · Accepted solution]

Hi Richard,

I got feedback on this test and would request you to open a ticket with Client Care ASAP so that this can be resolved for you.

Thanks

Nikhil

[#3]

Client Care couldn't help. Do Adobe intend fixing this?

[#4]

Did you ever get insight on this? I've had a client care ticket open on this for several months now with no resolution. 😞

[#5]

Hi Nikhil,

I came across this post, and wondering if there is any learning that can be shared here.  We experience similar issues with full page redirect tests in our company, the extended latency is impacting user experience and test data (e.g. double-counted impressions).

Thanks,

Sabrina

[#6]

Thanks for opening this ticket. I have this looked into ASAP.

Thanks

Nikhil

[#7]

We've had a ticket open for while but it's not moving anywhere: 150219-000039 

[#8]

Hi Richard,

That would be Target Classic. Let me consult the relevant team and revert.

Thanks

Nikhil

[#9]

Hi Nikhil, I've lost track of all of Adobe's name changes we're using the old/original version 🙂

[#10]

Hi Richard,

I'll look into this. Can you please let us know if you're using Target Standard or Classic ?

Thanks

Nikhil

[#11]

Hi Nikhil,

Yes it's just Chrome - we've had this problem for several months now so we're using Google Experiments for redirect tests now. We understand that there will always be an element of page rendering with a redirect however it's so bad in Chrome that you can't use it as it would invalidate test results. You can see for yourself here and compare with Chrome and Firefox: http://www.avg.com/us-en/tnt-qa?q=u

Richard 

[#12]

Hi Richard,

Is the issue specific to Chrome or are you able to replicate it in other browsers also?

Thanks

Nikhil