☕[AT Community Q&A Coffee Break] 10/13/21, 8am PT: Gentry Lin, Senior Solutions Consultant for Adobe Target☕

---

@rc211 wrote:

Hi,

 

Implementing Target via GTM--is there an equivalent Adobe Target extension that we can use -I know its available in Launch/Telium?

---

Hello @rc211 - thank you for posting your question!  While it doesn't appear that GTM has a prebuilt extension,  Adobe Target can be deployed using a custom tag within GTM without issue.   

Good morning, @wlsguru! You can update profile attributes from the page by passing in specific profile parameters in getPageParams function on a new page load, view load, etc, which will update the profile in Target. Have you checked out this online resource?

 https://experienceleague.adobe.com/docs/target/using/audiences/visitor-profiles/variables-profiles-parameters-methods.html?lang=en 

---

@collettec199516 wrote:

Hi @GentryLin,

 

 Would like to know if there is a solution for

1. cross-origin cookie (www.xxx.de -> buy.xxx.com)

2. targeting campaign by if a javascript variable or dom element is within a page.

 

Many thanks!

---

Hi @collettec199516, 

Thank you for your question.  With the changing landscape on 3rd party cookies there is limited browser support for cross domain targeting / testing.  One alternative approach is to encourage authentication and pass in a unique customer id to stitch data.   For more information on what is supported related to 3rd pary cookies please refer to the following documentation:    

https://experienceleague.adobe.com/docs/target/using/implement-target/client-side/at-js-implementation/atjs-cookies.html?lang=en

https://experienceleague.adobe.com/docs/target/using/implement-target/client-side/at-js-implementation/upgrading-from-atjs-1x-to-atjs-20.html?lang=en 

For the 2nd question around targeting based on a javascript variable, it is recommended to pass in parameters into Target for building audiences.  Please refer to the following:  https://experienceleague.adobe.com/docs/target/using/implement-target/before-implement/methods/methods-to-get-data-into-target.html?lang=en 

Thank you!

Good morning, @julienb20151765! Audiences in Target are not the same as segments in other Experience Cloud solutions in that Target audiences do not have populations; they are real-time evaluations of audience rules that occur on every hit, and thus cannot be exported or shared. Although you cannot share audiences created in the Target audience builder with Campaign, consider these approaches:

1) If you build segments in Adobe Audience Manager or the People Core Service Audience Library — that you then use as Target audiences — those audiences can be shared with Adobe Campaign. You can find more information here: https://experienceleague.adobe.com/docs/campaign-standard/using/integrating-with-adobe-cloud/working-with-campaign-and-audience-manager-or-people-core-service/provisioning-and-configuring-integration-with-audience-manager-or-people-core-service.html?lang=en

2) Additionally, you can pass Target activity/experience data from the page into Campaign the way you would collect other visitor data today. You can then create audiences of visitors in Campaign who have been served a particular Target activity and experience. For more information:

• Response tokens in Target: https://experienceleague.adobe.com/docs/target/using/administer/response-tokens.html?lang=en 
• Examples of how to "token replace" Target activity and profile information as a method to pass data to Campaign: https://experienceleague.adobe.com/docs/target/using/experiences/offers/passing-profile-attributes-to-the-html-offer.html?lang=en 
• Web tracking overview for Campaign here: https://experienceleague.adobe.com/docs/campaign-classic/using/configuring-campaign-classic/setting-up-web-tracking/about-web-tracking.html?lang=en
• ACC SOAP APIs via JS, see: https://experienceleague.adobe.com/docs/campaign-classic/using/configuring-campaign-classic/api/soap-methods-in-javascript.html?lang=en 

3) You can also create segments of visitors who entered into an activity/experience in Analytics if you use our Analytics 4 Target integration and share those with Campaign. More on A4T here: https://spark.adobe.com/page/Lo3Spm4oBOvwF/ 

Let me know your thoughts!

---

@benmu6 wrote:

@GentryLin

Wondering how to do an mboxTrace in order to validate a Geo targeting audience? How do you confirm the location/IP address that is being captured?  Also, would creating a profile script to look at geoprofile.geolocation.country be the same as what the out of the box Geo location audience parameter would look at?

---

 Hello@benmu6 - great questions!  Response tokens can be used to return the geo information within the Target response for seeing the geo information that Target is basing its decision on. Please refer to the following:  https://experienceleague.adobe.com/docs/target/using/administer/response-tokens.html?lang=en.  

Using geoprofile.geolocation.country within a profile script is another way of capture / veiwing the geo information as well.  For more information please refer to this following resource: https://experienceleague.adobe.com/docs/target/using/audiences/create-audiences/categories-audiences/geo.html?lang=en 

Thank you for the great questions!

Good morning, @mrivas-xpediant! Have you considered the AEM-Target Experience Fragments integration? This allows you to export AEM Experience Fragments to Target, which are automatically added to the Target Offer library, and available to insert into/replace content in your activity. You can use Experience Fragments in both the VEC as well as the form-based composer in Target. This integration enables content teams to maintain governance over templates while giving the optimization teams the ability to access those experiences seamlessly in their Target activity creation workflow, and is supported by AEM 6.4 and up.

More information can be found here: https://experienceleague.adobe.com/docs/experience-manager-learn/sites/personalization/experience-fragment-target-offer-feature-video-use.html?lang=en

And for an overview of AEM + Target, check out: https://experienceleague.adobe.com/docs/experience-manager-learn/sites/integrations/target/overview.html

Would this be a feasible solution?

Good morning, @andyprout82! I wish we had enough to talk use cases! I invite other Target customers using Recommendations today to please chime in and share their insights.

Some food for thought: we've recently released Recommendations enhancements to identify the latest trending content using faster, more frequent algorithm runs. This can be used with any or the Popularity-based algorithm types, and benefits both e-commerce (trending products) as well as media and content (latest videos, articles, etc). And expect some additional enhancements before the end of the year.

Also, have you considered using Recommendations as an offer in an A/B or Experience Targeting activity? This capability opens the doors to more testing or personalization of your Recommendations. For example, A/B test different criteria, designs, placements, etc. Or insert Recommendations in an XT activity to serve specific criteria to a high value segment of visitors.

Finally, inserting Recommendations into an A/B test introduces the opportunity to use Auto-Allocate or, better yet, Auto-Target. Check out these links for more info:

• Personalization Strategies Using Artificial Intelligence (Summit 2021 video):
  https://business.adobe.com/summit/2021/sessions/personalization-strategies-using-artificial-intell-s905.html 
• And if you're not familiar with our Recommended for You algorithm, give Delivering Dynamic, Personalized Experiences with Adobe Target’s New User-Based Recommendations Algorithm a read: https://blog.adobe.com/en/publish/2019/10/29/delivering-dynamic-personalized-experiences-with-adobe-targets-new-user-based-recommendations-algorithm.html#gs.d0vpsh

Hi @neha64 !

Kai here from the Target Client Care team to assist your questions today. Thanks for your questions and participation! Flicker can sometimes occur when tag embed codes are loaded asynchronously and the page finishes rendering before the Target library is fully loaded.  In order to mitigate this, we suggest following the steps outlined at https://docs.adobe.com/content/help/en/core-services-learn/implementing-in-websites-with-launch/implement-solutions/target.html and specifically taking a look at the section outlining the Target Pre-Hiding Snippet.

Once these steps are followed, if you are still seeing a noticeable flicker/delay here are a few other things to consider:

1. The default timeout setting in the pre-hiding code snippet is set to 3 seconds. If you are seeing the 3 seconds blank screen all the time, then please double check to ensure that bodyHiding is enabled for at.js in Launch. If body hiding is disabled, the snippet will always wait for 3 seconds before showing the content. If you have enabled bodyHiding and still seeing 3 seconds blank screen occasionally, that is expected to happen when the Target requests takes more time to respond, usually on slower internet connections (such as mobile). You could potentially fix this by adjusting the 3 second timeout for the hiding snippet. Ensure you don't reduce it too much, the more you reduce the number, the more chances to get a flicker.

1. If opacity 0 does not work in your implementation, you can also manage flicker by customizing bodyHiddenStyle (in Launch) and set it to body {visibility:hidden !important} . You can use either value body {opacity:0 !important} or body {visibility:hidden !important}, whichever works best for your specific circumstance.
2. Are you hiding the entire HTML body with the pre-hiding snippet? By default the snippet pre-hides the whole HTML BODY. In some cases, you may only want to pre-hide certain HTML elements and not the entire page. You can achieve that by customizing the style parameter. It can be replaced with something that pre-hides only particular regions of the page. For example, you have two regions identified by IDs container-1 and container-2, then the style can be replaced with the following:

#container-1, #container-2 {opacity: 0 !important}

Instead of the default:

body {opacity: 0 !important}

Reference: https://docs.adobe.com/content/help/en/target/using/implement-target/client-side/at-js/manage-flicker-with-atjs.html