Adobe Target

Hello everyone,We are not seeing a lot of visitors/views being counted for an A/B test when we pull up the reporting in Analytics. I've tried my best to explain below how the A/B test is setup, and have also explained my understanding of the issue. Any help with shedding more light into this issue, or confirming my theory, is greatly appreciated!!This A/B test is being run within our Single Page booking engine. We wanted to deliver the test only to visitors who are clicking on the CTA (Call To Action) buttons to add a product to the cart.We have implemented this by setting click event listeners on those buttons through an XT Activity that is delivered to all visitors to the page. So, when the visitor clicks any of those buttons, an mbox request is fired (using adobe.target.getOffer() and adobe.target.applyOffer()) with an mbox parameter. This param is configured as the qualifying audience for the A/B test, and so the mbox call returns with the A/B test.Now, based on the experience that

Hello,It's been a while since I worked in Target and Target Classic used to have a "Landing Page Campaign" that kept a visitor in a campaign until they converted (or no longer qualified).  For example, a visitor clicked a campaign offer on the homepage which entered them into Campaign A.  This allowed us to present "Campaign A" related content throughout the site (multiple pages) even if they never clicked the button again.I'm not seeing a way to do this is Campaign Standard - how do you persist a visitor's qualification in a campaign without them having to re-qualify (click the button in my example).Simply put - what equals the Classic "Landing Page" functionality in Standard?Thanks

Hello,I have been experiencing a flicker on the very first load (cache, cookies cleared).  We are using mbox.js Version 62. To try to remedy this issue, I’ve tested this in two ways:Using the Visual Composer to make the edits:- Flicker is still there on the _very first_ load, and seems to work on subsequent visits.Using vanilla javascript to immediately inject a style with visibility: hidden through the custom code section (in the head).  Then show it (visibility: visible) after the content loads.- Flicker is still there on the _very first_ load, but works on subsequent visitsIn the previous release notes it stated that:Mbox Version 61 (16.7.2) Body hiding is disabled by default. Target uses body hiding only when global mbox auto-create is enabled and body hiding is enabled.AndMbox Version 60 (16.4.1)                  window.targetGlobalSettings = {                     bodyHidingEnabled: true,                     bodyHiddenStyle: "body{opacity:0}",                     visitorPageDispla

Hi There, I have a website which is implemented using Adobe launch with Target as an extension, I upgraded the Adobe Target extension using the upgrade option but my the at.js version doesn't seems to get updated .Is there something else which I need to do after upgrading the extension. My Launch code is still present on my website.Appreciate your help.Thanks

Is it mandatory to use FTP for giving the product data feeds to Adobe Target?Create Feed I'm using the documentation mentioned in the below link, but it doesn't clearly call this out. I'm trying to supply the feed from a SFTP, but getting an error saying invalid user credentials.

Hi,I am trying to setup a Map array for design, I am able to set the map array but I can access it's value Apache Velocity Engine - User Guide #set( $monkey.Map = {"banana" : "good", "roast beef" : "bad"})$monkey.Map.get("banana") Doesn't workIs map included? rgds,jerome

Hello all,My team is trying to run an AB test using 2 distinct flows throughout the form. We have collapsible sections and we're trying to figure out if having the topmost section always open would be better.The way we've implemented this is by adding some control flow logic to see if the feature flag (named 'ALWAYS_SHOW_SECTION') is on the window and is true. The idea was to add a Custom Code modification to our A/B test in which we added <script> window.ALWAYS_SHOW_SECTION = true; </script> to the HEAD.Locally, this strategy works, but when we try to do this through Adobe Target, it doesn't seem to change our logic. Is this strategy sound? Does this strategy just not work on Adobe Target because of some asynchronous logic?Thanks in advance

HI ,I am using Adobe Target ( Mbox.js ) for the past few years. Now we are migrating to AT.js. I have integrated and I am making a getOffer callIn our new application , we have setup few CORS rules due to which each XHR call is preceded by an Http OPTIONS call ( pre-flight call ) for security reasons. BUT the http pre-flight (OPTIONS) calls are failing when I am making this call to Adobe  Target . It gives 200 Application Error Response status and in response I get a response mboxEnv.disable(10 * 60) // got 500 from node. But if I hit the same Target Call directly as a GET call it works. ( the OPTIONS pre-flight request gives error response ). Is there anything that I need to enable OR request Adobe Team to setup in my campaign ?

Hi,I have an use case in which i need to fetch data from an API and render experience which contain response of the APIFor accomplishing above scenario i am using usign DTM and adobe target.i have created a data element using custom script which contain XMLHttpRequesti have created a page load rule which triggers on dom ready from where i am passing value as a mbox global parameter to adobe targeti am using mbox global parmeter in adobe target and rendering experience.After page load everything works fine in console but i'm getting response as empty string in adobe experience cloud debugger.Can any one let me know where i am going wrong?Below is the custom script code for data element.    var request = new XMLHttpRequest();    request.onreadystatechange = function() {        if (this.readyState == 4 && this.status == 200) {               console.log(this.responseText);               var response = JSON.parse(this.responseText);               return response.id; //the data eleme

HelloI successfully implemented an A/B test for my mobile application, but have run into an issue.I would like to use this A/B test to simply track how many of my users visit a certain page at least once, no matter how many times they open the app.My A/B Test has one location which I use to get an experience, and an action in the app marks a successful conversion (see attached image)The way I understand it, Adobe Target generates a new session id (_sessionId in the TargetWorker class) on every app relaunch, and this counts as a new visit each time. This session id appears to be how Target tracks a conversion (it is sent as header in the network call).So, if a user launches the app 5 times and performs the desired action in 3 of those sessions, he gets marked as a visitor 5 times, and as a "converted visitor" 3 times.However, I would like him to be marked as a visitor just once, and as a converted visitor just once as well.It looks like I could get close to this desired behaviour by tar

Hi all,I've got an A/B test activity in which I'm targeting Chrome, FF, Safari, Edge, and IE11. All browsers work with the exception of IE11.I can't determine what is wrong with my audience configuration. See attached.I've included an additional OR to include Browser Type equals IE and Browser Version equals 11. Is there any reason, with this config, that I would not enter the test using IE11?Thanks in advance for your help/guidance!- Brion

Why are Remote Offers not supported in the VEC. The only options available when using the "Replace Content" feature of the VEC are "HTML Offer" or "Experience Fragment". I believe that in the past Remote Offers were supported by the VEC, but now they are only supported by the form-based editor.

Hi There, I have a website where layering is done on the pages , one layer of video runs in the background with text and icons being overlapped on a different layer.When I create a Target activity and the try to edit the elements on the pages in the VEC,  I am not able to edit the content in the background layer because I am not able to catch the HTML tags for that page using the Edit text/HTML options.Can someone help. Any help would be appreciated.Thanks

Hi,Following up on my previous question here: Experience target on customer attributes I have set up customer attributes and mapped them to Target. I uploaded a test customer and am trying to target this based on age. I called the customer attribute source "AnalyticsID-TEST".The customer attributes show up when building an audience in Target, so far so good. Some of them show up twice though, which is odd:When I log in as this customer, I can see the that the attributes I uploaded are present and linked to the profile. But here they have a completely different naming, being called "crs.305694.parameter":The above audience criteria doesn't match this profile and my experience target doesn't run. But if I manually add the attribute with the same naming as in the interface it works:Is this expected behavior? How can use the above parameters in an audience?I'm also passing mbox3rdPartyId in the logged in events, and I've tried adding it in the non-authenticated area where the experience ta

Hi, Uploading images in Adobe Target is not working, what could be the problem? Nicole

We have components in Experience Manager written via a javascript framework.  As a result there are custom html elements in our markup.  This is presumably quite a common scenario.  Target seems to struggle to work with this markup - in terms of amending text and images.What should Target be able to do in this case and - if it is problematic - what can our developers or adobe do to help?Here's a snippet example of our markup,

Is there some way to remove or hide deleted experiences from a report in Target?I could certainly understand retaining a deleted experience if it had data associated with it because that data would have an impact on the overall results of the test. However, the experiences in my example above were removed prior to activating the test. As such, there is no data associate with them. So, including them adds no benefit to the report and, in fact, actually make the report harder to digest, especially for a layman. These deleted experiences add completely unnecessary noise to the report.I'm still new to Target, and as a novice, it is often necessary to me to try out various methods of building an experience until I get one that works the way I want it to. So, experimenting with the composer is not unusual and deleting failed attempts is no problem. It's only when viewing the report that it becomes an issue.If there is no way to remove or hide these empty deleted experiences within the report

I cannot consistently qualify for Target Activities as I intermittently get a CORS issue (and it seems to happen more and more frequently now). It is also happening to other co-workers as well. We have tried wiping cookies and cache, different/new browsers, and incognito – both inside and outside the firewall. And I have checked with our systems team and they said nothing should be blocking on our side. We are on at.js v1.5 delivered through DTM.I keep getting this when trying to qualify for activities:Is there a simple fix/explanation for this - I keep trying to reference Cross Origin documentation and issues, but nothing seems provide guidance towards applying something quickly.