will_lanni

Re: Experience custom code runs twice - Adobe Target 05-07-2019

Thank you Guaresh, I'll open a bug and see if we can figure out what's going on there. Liked/marked helpful.

10.1K

Re: Experience custom code runs twice - Adobe Target 03-07-2019

OK, Surbgupt (hey you changed your username! ), we've deployed our Target installation into production.Our test is set up as an A/B. Both experiences purely just drop a console.log into the developer console. The default console log is 'tgt-dflt', and the test is 'tgt-tst'.https://www.endicia.comIf you look, you'll see the little (2) next to the console log, indicating it triggered twice.Hope this helps! Let me know if you need any more information.

10.1K

Re: Experience custom code runs twice - Adobe Target 13-06-2019

*headslap* Surebee we won't be able to provide a test until target has been implemented in the environment we're working in and released into production. I'll need to come back to this when we've released.However, I can say that we implemented the fix from that old thread posted by the OP, and it cut out the second log.Anyway, I'll set a reminder to come back to this when we have a production version to show.

10.1K

Re: Experience custom code runs twice - Adobe Target 13-06-2019

I will need to get permission to set up a live activity on production so I can share it. I'll post back here when I get that going.

10.1K

Re: Experience custom code runs twice - Adobe Target 07-06-2019

We have same issue. just upgraded to at.js 2.1.0We have an A/B test.All the code does is run a console.log.We see two console logs trigger.In other properties where we use at.js 1.x we do not have this problem.

10.1K

Re: ERROR: Referring to invalid nodes - Adobe Target 26-07-2018

bkmills1I just cleared cache and cookies, and closed out my browser (all Chrome windows) to ensure the session was closed.I reopened and went through the exact steps above.I was able to save this time. Also, the interface changed slightly, I noticed. So there definitely was something stuck in the cache. Give that a shot, I think it will clear the problem.EDIT looks like surbgupt beat me to it; that did work for me.

1.8K

Re: ERROR: Referring to invalid nodes - Adobe Target 26-07-2018

Confirming the ability to duplicate this in the following form:I open Target for the first time, logging in fresh. Chrome (latest), Windows 10 (latest)I open a previously saved activity to make an editI click in the URL bar to allow scripts to load inI click the Custom code button to open the panelI make my edit, correcting a shameful spelling mistake I should have caught. Bad me!I click Save in the custom code area to save the custom code.I expand the menu under the 'Next' button in the upper r...

1.7K

Re: Is there a query string key/value pair that will exclude a user from ALL Target campaigns - Adobe Target 20-10-2016

OK, I discovered that for at.js the following query string disables mboxes:?mboxDisable=1I'll keep looking to see if there's another for the older mbox.js, if anyone knows for sure that there is that would be fantastic. Thanks.

792

Is there a query string key/value pair that will exclude a user from ALL Target campaigns - Adobe Target 20-10-2016

Hello,We have a visual regression system that takes snapshots of a set of pages and compares them to baselines.We have constant false positive failures due to the different campaigns and A/B testing we're doing.We have a need to be able to exclude our visual regression test (running PhantomJS) from all campaigns--basically ALWAYS default, regardless of the campaign, without having to update our test script, as this would require constant updates. (we run a lot of tests).Is this possible? Is ther...

978

Likes given to

User

Count

Likes from

User

Count

Learn

Documentation

Community

Support

Resources

Adobe account

Adobe