Adobe Target

Hi, We’re trying to extract all tntIDs for users from Adobe. Once this information is received, we intend to append additional customer attributes data and upload to target to create custom audiences. Given this case, can someone advise on how to retrieve all tnt IDs? Regards,Sri

Does the order of the rules in an audience affect how the Audience works? Tried combining Mobile Carrier AND Zip Code AND Connection Speed but it didn't work. We tried using Mobile Carrier only and it worked.

Our site currently implements jQuery at the global level, but it also appears that Target also injects an un-minfied version of jQuery as well. Is it necessary to do this or is there some way to disable this. It does affect page load because it render blocks and while it doesn't affect code it seems silly to have duplicate references.  If not, can we at least minify it through some config? Thanks very much.

Personalization Industry Insiders Webinar Series Across the world we are seeing companies in every industry rapidly adapt to the changing behaviors and demands of our current times. This four-part Adobe Target webinar series connects people from companies in the healthcare, media, retail e-commerce, and financial services industries with Adobe experts, to highlight the transformations being undertaken every day in light of 2020's dramatic changes to how businesses run and operate.   CHECK OUT THE RECORDINGS BELOW:   5/7/20: Healthcare and Pharmacy Personalization Industry Insider 5/14/20: Media, Publishing and Telecommunications Personalization Industry Insider 5/21/20: Retail Personalization Industry Insider  5/28/20: Financial Services and Insurance Personalization Industry Insider

  If you missed the last Adobe Target Skill Builder Webinar, Developer Chat: Migrate Adobe Target's mbox.js to AT.js, fear not!   Check out the recording here: Developer Chat: Migrate Adobe Target's mbox.js to AT.js, and feel free to post any of your AT.js-related follow-up questions in the thread below so that we can make sure you get your answers 🙂    Join David Son, Adobe Target Product Manager, as he lays out the benefits of migrating mbox.js to AT.js. Hear the latest AT.js updates, learn about its enhanced capabilities and how they align with larger trends in the tech landscape, as well as some practical tips to ensure that you extract as much value from Adobe Target when you migrate from mbox.js to AT.js. As always, we'll carve out time for Q&A, so come with your questions, and take the opportunity to have them answered. Adobe Target Developers won’t want to miss it!        David Son is a product m

My experience targeting experiment has 5 variations with 5 different segments. Should the order in which that I create those variations for segments matter? Because my audiences are not mutually exclusive,thougths?

Hi Team, Just wanted to check if we can send at_property token with the orderConfirmPage and this won't impact the order tracking at target end? Thank you. 

Hi, hope someone can help me with this.Our Target account is set across multiple domains, and activities on some of these domains are entirely separate from activity on others.We want to pass parameters in to the global mbox only for the domains where those parameters can be put to use. Is it therefore possible to define different global mboxes for each of these domains? I haven't been able to find any info explicitly stating this.That is, when adding mbox.js tag on to each domain, could I edit the settings for "Global mbox name" to 'domainA-global-mbox' for domain A, and then separately use 'domainB-global-mbox' for domain B, all within the same Target account?Hope that makes sense.Thanks,Chris

 Adobe Target Community Q&A Coffee Breaks A program designed to keep you connected to some of the very best Adobe Target resources - specifically, the great minds behind Adobe Target, including our expert product management, product marketing, consulting, and engineering team members. Join us right here in the Adobe Target Community on Experience League: once a month, always on a Wednesday, @8am PST, beginning October 2020! Each event is a 1-hour Q&A chat with your peer practitioners while you can pose your Target questions directly to the featured expert members of the Adobe Target team, who will be signed in to the Target Community to answer your questions live within the forum thread - and, follow up Qs are highly encouraged! Don't miss these opportunities to learn through conversation and exchange with the experts who build the technology you're working with 😄  Q&As can cover a wide variety of HOT TOPICS, including: &nbs

Hello Community members! We are conducting an online usability study the week of May 4th and invite you to participate by clicking the link below.Your participation will help guide future improvements for Experience League. We hope you join us! Please click here to join: https://adobe-experience-league-ui-refresh.youcanbook.me/   Please contact me or email userlabs@adobe.com if you have any trouble accessing available times.

If you're new to Adobe Target and haven't already walked through the Adobe Target Welcome Kit, now's the time!   The Adobe Target Welcome Kit is a curated collection of resources designed to build an Adobe Target beginner's confidence and capacity with the solution, including key information and tools to help you prepare for and launch your first Adobe Target activity, tips for short-term quick wins, and strategies for long-term optimization.   Comment below with any feedback or follow-up questions - we love hearing from you 🙂 

Hi all We are looking at running an upcoming server side experiment using Adobe Target's Node.js implementation and was wondering if it is safe to run server-side A/B testing and what considerations should be made? For example, we have an upcoming redesign of our internal search result pages where we wish to use server side Target to show 50% of my traffic the old search design, and show 50% of our traffic a completely different search result page, are there any implications to SEO and organic search?

An Adobe Target trainer told my client that mbox should be fired on pages where there are running experiments. This is apparently to reduce server calls, which would reduce licensing costs too. My client is using Target Standard. Firstly, my client is already using at.js through Launch. They’re not using the old mbox.js at all. So is mbox even a thing for my client? In Target’s interface, I see mbox referenced together with "Custom Code", e.g. when setting up a variation. So maybe it is still a thing even though they're using at.js? But in all of the Target implementation guides for both client-side JavaScript and also for Launch implementations, the guides just say to implement at.js in all pages. Then, in Adobe's pricing webpage at https://helpx.adobe.com/legal/product-descriptions/adobe-target.html, it states that Target Standard's license is based on Annual Page View Traffic. Based on the definition of "Page View", it does sound like running at.js on every

We are just at the very early steps of implementing Target and was wondering if the function to create some form of folder structure with in the main activities screen. we are exploring the use of Workspaces but is there a function to generate folders within the activity? if not could there be?

Hi All,at.js added to the siteSome lines of code  added in the library footer code has mentioned as mentioned in the link - https://docs.adobe.com/content/help/en/target-learn/tutorials/implementation/implement-atjs-20-in-a-single-page-application.htmlIN the Launch one of the rule- adobe.target.triggerView(viewName); has addedIN the network, I can able to see the delivery request , But viewName are not available , I don’t see the views in the prefetch.To get the viewName , Do we need to add the logic’s inside the code base of the Mobile  site is required?Or library footer code will help us to generate the views.Can you please provide the steps in order to get the view name in the vec for Spa using launch with the AngularThanks In AdvanceRegards,Pradeep

Hello Team, we’re logging the following JavaScript errors on our site. Visitor API requests timed out (approx. 130 errors per day)Disabled due to opt-out” (approx. 400 errors per day) These both appear to be coming from the Adobe Target at.js library 2.1.1.  @How can we resolved that? Is there any configuration needed. Thanks,jantzen.belliston-Adobe​Amelia Waliany​

Hello!I am new using adobe target. I am doing a Test AB. Experience A is the control (default Page) and Experience B is what I want to change. I do not have access to the new Librarie so I wrote an extra code to inject it. When I inject my code in the console I can see the changes on the website. When I inject the code in Adobe Target I can see it in Edict Activity (where I write my new code in the custom code) and in the URL given by Activity QA.  When I change the Test status to Active,  I can still see it in Edict Activity and Activity QA. But It is not displaying when I enter into my regular url (like an user would do it) Anyone knows what can I do? What could be my error?   Thank You!!!  

Hi everyone, I've installed Target through DTM and in the debugger it appears on the overview with  Version: mbox.js 63Global Request Nametarget-global-mbox But I can't see any request from target  On the page I see the request and I have this error on the console On DTM there is no rule related to Adobe Target. Should I make it one to trigger the request?

Previously when I had used the mboxTrace functionality to debug recommendation activities the page would display both the product recommendation zone and the recommendation debug box above the product recommendation zone.  Recently I noticed that only the recommendation debug box is being shown.When I check the mbox I see that Target returned the direction to insert the recommendations. Is this a bug or is there something that I'm forgetting to do?

Performance is critical for web applications, which means we often try to avoid network calls as much as possible to not add latency time each time an application needs computed data from a server.This is also true for personalization, and looking at Adobe Target capabilities, I can see that implementation through at.js, getOffer for each mbox on a page will  trigger an individual HTTP Request.On the other side, Target REST API provides a way to get several mbox offers in one HTTP call, which seems more efficient.Is the multiple mbox call will land in at.js in the future ? Is there a way to achieve this already with the library ?

Hi All,Can anyone help me to mbox3rdpartyid to target_global_mbox call . I will get the mbox3rdpartyid value once the page is loaded by the time AT.js will trigger the target_global_mbox call. Is there any way we can update the mbox3rdpartyid for further mbox call in same session.I tried the below API for that.But i am not seeing this working.https://client.tt.omtrdc.net/m2/client/profile/update?mbox3rdPartyId=xxxxxxThanks,Hariharan S

Hey, we just upgraded to at.js 2.3 from at.js 1.7 with the new Delivery API and we noticed that we were getting this error:After looking into it, we found this documentation that the Delivery API has a limit of 50 mbox parameters where as the previous library had a limit of 500.https://docs.adobe.com/content/help/en/target/using/troubleshoot/target-limits.html Can anyone confirm? We are currently using mbox parameters to pass along customer profile data from our CRM and definitely have instances of more than 50... 

Can someone point me to a side by side comparison (pros and cons) of the old mbox vs the at.js?  I need to make an informed decision as to what type to use. Our organization just upgraded to AEM 6.2 and from what I can tell the new at.js is not compatible, is this true? If it's not true, can you point me to some literature so that I can inform my executives and make the case for the Adobe Target upgrade?  Any help would be most appreciated. Thanks in advance. 

Hi Team, mboxCreate method doesn't work with at.j.How could we create an mbox div at page level?I tried with below code but no luck : <div class="mboxDefault">adobe.target.getOffer({"mbox": "customTestMbox","params": {"status": "true"},"success": function(offer) {adobe.target.applyOffer( {"mbox": "customTestMbox","offer": offer} );},"error": function(status, error) {console.log('Error', status, error);}});</div>