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
Bedrock Mission!

Learn more

View all

Sign in to view all badges

dwright
dwright
Offline

Badges

Badges
27

Accepted Solutions

Accepted Solutions
33

Likes Received

Likes Received
46

Posts

Posts
117

Discussions

Discussions
32

Questions

Questions
85

Ideas

Ideas
6

Blog Posts

Blog Posts
1
Top badges earned by dwright
Customize the badges you want to showcase on your profile
Re: Target Standard Manual Traffic Split change to 100% - question about how traffic allocation works - Adobe Target 06-09-2016
Hi Kevin,The answer is 2. Visitors in an A/B test will stay in their initially-assigned experiences. The traffic change will impact new entrants only.Daniel

Views

1.7K

Likes

3

Replies

0
Re: Which JS Library For New Target Standard Launch - Adobe Target 30-08-2016
Hi David,The URL you posted (https://www.pbjtest.com/EmailSignUpPopUp/dialogContent.cfm?siteCode=PBJ) does not appear to have at.js or any mboxes on it. It's the second half of the error message--"does not contain Target libraries"--that is relevant here, not that there is a timeout in the VEC. You mention iframes. Is this URL iframed by a page with Target code? If so, that is not going to help you, as iframes are by design sandboxed from eachother. If you are trying to test content on the URL (...

Views

1.3K

Likes

0

Replies

0
Re: Backbone component functionalities are not working fine in Preview Mode, when target is enabled - Adobe Target 29-08-2016
Hi Shikha,It sounds like you have a Single Page Application, hence the use of Backbone. Single Page Applications are much more complex--mostly because of the flicker-handling needed as per Parit's reply. We developed an new library with SPAs in mind called at.js and this is what we recommend for SPA implementations (https://marketing.adobe.com/resources/help/en_US/target/ov2/c_target-atjs-implementation.html). Please note that the TNT.createGlobalMbox() function is not part of at.js and mbox cal...

Views

1.2K

Likes

0

Replies

0
Re: Multiple Audiences Resolved - Adobe Target 29-08-2016
Hi Selvagesh (and Parit),Experiences are prioritized in the order in which they appear, e.g. the first audience/experience on the diagram screen has the highest priority.Daniel

Views

1.3K

Likes

0

Replies

0
Re: Which JS Library For New Target Standard Launch - Adobe Target 29-08-2016
Hi David,Glad you were able to resolve the problems you were having with the Experience Composer in your environment. at.js v0.9.1 seems very stable and I haven't heard of any issues with it (I work closely with the engineers developing it). IMO, it is much better than mbox.js. We are working on ways to simplify usage of mboxTrace, mostly to make it easier to get the token and understand what it is showing.Daniel

Views

1.3K

Likes

0

Replies

0
Re: Creating Test on pages with React js - Adobe Target 03-07-2016
Yes, that is not a supported way to load DTM and will not let you add Target correctly. You need to use the embed code provided by the DTM interface which will load the library synchronously and thus allow you to load Target synchronously. This is necessary to manage flicker appropriately.

Views

7.6K

Likes

0

Replies

0
Re: Creating Test on pages with React js - Adobe Target 01-07-2016
Is there a URL we can look at? It sounds like something in the chain of operations loading asynchonously which shouldn't be. Are you loading the main DTM library correctly using the exact code copied from the UI? Or is someone trying to load DTM asynchronously?

Views

7.5K

Likes

0

Replies

0
Re: Creating Test on pages with React js - Adobe Target 07-04-2016
Ok, good luck to you! I would really encourage you to drop the legacy integration and move to A4T. Not only are the capabilities much better with the integration, but it would allow you to upgrade to at.js. Since A4T uses server side calls from Target to Analytics, you don't have to be as concerned about the sequencing of client-side hits to make sure the integration data gets sent to Analytics which can get very tricky in SPAs.

Views

7.2K

Likes

0

Replies

0
Re: at.js flickering? - Adobe Target 05-04-2016
Hi Morten,How do I know the mboxCurrent error is associated with the legacy integration? If you look in your mbox response you will see the integration response plugin code--note the use of mboxCurrent:\r\n/*T&T to SiteCat v4 ==>Response Plugin*/\r\nwindow.s_tnt=window.s_tnt||'', tntVal='125507:1:0,';\r\nif (window.s_tnt.indexOf(tntVal)==-1){window.s_tnt+=tntVal}\r\nif (mboxCurrent.getFetcher().getType()=='ajax'&&(window.s &&\r\nwindow.s.tl)){s.tl('TnT', 'o', 'TnT');}\r\nmboxCurrent is not an object that exists in at.js, which is one of the reasons we have documented at.js as incompatible with the legacy integration. The newer A4T integration is compatible and customers should upgrade.If your company is no longer using the legacy integration in any way, you should...

Views

1.5K

Likes

0

Replies

0
Re: Creating Test on pages with React js - Adobe Target 04-04-2016
Hi Ridder,I don't see the mbox div getting written to the DOM at all. Maybe React's virtual dom doesn't allow it? Try at.js--which doesn't add a div to the DOM for the global mbox to work--and let us know if you get better results.Daniel

Views

6.9K

Likes

0

Replies

0