[AT Community QandA Coffee Break] 5/25/22, 8am PT: Brent Kostak and Drew Burns, Adobe Target Experts

[Amelia_Waliany]

Join us for the next Adobe Target Community Q&A Coffee Break 

taking place Wednesday, May 25th, 2022 @ 8am PT - 9am PT 

~ REGISTER HERE  ~

We'll be joined by @bkostak and Drew Burns aka @Drburns27 of the Adobe Target Product team, who will both be signed in here to the Adobe Target Community to chat directly with you on this thread about your Adobe Target questions pertaining to their areas of expertise, and those specifically related to topics covered during their 4/28/22 Real Time Personalization Webinar: 

• Creating shared audiences with Adobe Target and Real-Time CDP

• Building first-party data strategies to solve data fragmentation challenges

• Deploying end-to-end workflows for millisecond personalization

• Delivering relevant messaging, content, and offers in real-time to drive engagement

@Kai_Motoyama, Technical Support Engineer, will be on the thread to provide further guidance around the above topics with Brent and Drew

**Be sure to watch the 4/28/22 Real Time Personalization webinar with Brent, then plan join him and Drew during the 5/25 Coffee Break to continue the conversation and dive deeper into answers to your personalization questions

REQUIREMENTS TO PARTICIPATE 

• Must be signed in to the Community during the 1-hour period 
• Must post a Question about Adobe Target
• THAT'S IT!  *(think of this as the Adobe Target Community equivalent of an AMA, (“Ask Me Anything”), and bring your best speed-typing game) 

INSTRUCTIONS 

• Click the blue “Reply” button at the bottom right corner of this post
• Begin your Question with @bkostak and/ or @Drburns27 
  

~ REGISTER HERE  ~

As Product Marketing Manager at Adobe, Brent brings data-driven personalization solutions to market that connect global brands to their customers. Adobe enables enterprise marketing and engineering teams to streamline data and create a single, personalized view of their customers to deliver exceptional digital experiences. Brent has over 10 years of experience helping organizations leverage software technologies and services to better compete and serve their mission.

Drew Burns is Group Product Marketing Manager for Adobe Target, the industry-leading experience optimization platform, and he has been an evangelist and a practitioner in the personalization and testing space for 15 years.  He works with progressive enterprise companies across industries on building the foundation and maturing their optimization and personalization efforts, strategies and programs leveraging manual and A.I./ML capabilities. At Adobe, he works alongside the leading enterprise companies in retail/e-commerce, travel & hospitality, financial, media & publishing, B2B/ High Tech and other verticals to improve and grow their optimization and personalization efforts, strategies and programs. 

Curious about what an Adobe Target Community Q&A Coffee Break looks like? Be sure to check out the thread from our latest 4/27/22 Adobe Target Coffee Break with Principal Solutions Consultant, @Jim_McTiernan and Technical Support Engineer, Simon Chen aka @simochen

[bkostak]

@megankweise As far as round trip calls for Adobe Target, customers should be seeing milliseconds in speeds. We can work with you to do an audit for investigation and share specific numbers for Adobe Target performance - but this is most likely related to an issue with implementation. Perhaps multiple applications running at the same time/loading on page or a flicker issue. See below to double managing flicker issues

https://experienceleague.adobe.com/docs/target/using/implement-target/client-side/at-js-implementati...

If you have followed all the steps outlined at https://docs.adobe.com/content/help/en/core-services-learn/implementing-in-websites-with-launch/impl... and if you are still seeing a noticeable flicker/delay in the test content being shown then here are few 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 body Hiding 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 body Hiding 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.

2. If opacity 0 does not work in your implementation, you can also manage flicker by customizing body Hidden Style (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.

3. 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-flicke...

4. If options 1. to 3. do not work then I recommend engaging our consulting experts to review your implementation and suggest next steps!

[ben_mrm]

@bkostak and/ or @Drburns27 

I have a question about troubleshooting a reporting issue within Target.....for an A/B test that is built utilizing the auto-target traffic allocation, what would be a cause for not seeing either a Personalized Insights nor Important attributes reports? 

We've had a test run for about two months, personalization models have been created for all 3 experiences, so there should be enough data to derive a report(s). The only thing that I can think of as a cause is that the test was temporarily deactivated and reactivated to the site but only for a day. This was about mid-way through the testing period, so there should have still been enough data even if everything had to start over. Hoping you guys might have some solutions?

[Drburns27]

@ben_mrmThe insights reports should generate once the activity reaches the required thresholds per experience in the activity.  The stalling of the activity could have impacted the number of visitors that have qualified for each activity so it may take a little longer for the algorithm to get back up to speed.  It's difficult to diagnose without seeing the activity, but if the issue persists, you can open a ticket on this (although I've not known there to be a previous issue with the Insights reports with Auto-Target)

More info on Insights reports here: https://experienceleague.adobe.com/docs/target/using/reports/insights/personalization-insights-repor...

[ben_mrm]

Thanks for the response! When you refer to the "required threshold", are you referencing the threshold needed in order for the models to generate or is there another threshold that needs to be met once those models have been created?

[ben_mrm]

@bkostak and/ or @Drburns27 

Sorry, another question....when utilizing Target through the new AEP implementation/connection, can you still use Target as a reporting source? Is there anything in particular that needs to be kept in mind when using this reporting source? We've seen click tracking issues, lack there of, and wondering if there are common pitfalls here?

Thanks!

[Drburns27]

@ben_mrmI would love to review the click-tracking issues you've experienced.  Yes, Target reporting and Analytics-enhanced reporting are still the optimal methods for reporting within Adobe Target when utilizing an RTCDP segment within a Target activity.

[ben_mrm]

@bkostak and/ or @Drburns27 

What is the best way to troubleshoot a Recommendations activity delivery when using AEP Web SDK implementation method? Does that rec data appear within the Adobe Experience Platform Debugger, is it through console logging once enabled through the debugger, or an mbox trace, another method? 

[Drburns27]

@ben_mrmAdobe Experience Platform Debugger is the best route currently, but we would also love to hear what the information is that you are looking for in terms of recommendations delivery utilizing the AEP Web SDK.

[Amelia_Waliany]

Hi @bkostak and @TDre, thanks so much for your time in the Target Community today! This question was posted by Target Community member, @Umamaheswari_Yakkala:

"Hi Team, 

Can we use the Adobe Target API to create audiences from 3rd party tools other than the Adobe module?

Thanks In Advance"

Link to original question: Can we integrate 3rd party audiences to Adobe Target by using Adobe API

[Drburns27]

@Amelia_WalianyAudience definitions, if shared from a 3rd party product, may not be the same definition within Adobe Target, due to differing counting methodologies.  The best method I would suggest for sourcing audiences from data from a 3rd party tool would be to bring this data in (choosing between several methods, including Customer Attributes, batch profile upload, or passing data through the data layer) and then building these audiences utilizing this data source within Target. 

[ben_mrm]

@bkostak and/ or @Drburns27 

I know with the new Web SDK Target implementation and AEP connectors its a bit easier to connected with Salesforce platforms to send and receive data and enhanced segmentation capabilities, however, does the at.js implementation method allow a connection to Salesforce currently? My understanding is that data can potentially be sent from Target to SF through response tokens for reporting data but any connection back from SF?

[Drburns27]

@ben_mrmAT.js has a well-established integration with SFDC.  We have many companies utilizing SFDC and leveraging our 50+ APIs on the Adobe Target side to connect with Salesforce.  There are also the aforementioned methods for bringing data into Adobe Target, including our batch profile upload api, Customer Attributes core service, or passing data within the data layer on the page for use within Adobe Target.

[Amelia_Waliany]

Hi @bkostak and @TDre, thanks so much for your time in the Target Community today! This question was posted by Target Community member, @Saravanan_Dharmaraj :

"We have done Analytics 4 Target (A4T) integration. We have a segment called "T200 companies" in Analytics and brought that segment to Target as Audience. Now we want to create experience targeting in some AEM pages which will target some companies inside the "T200 companies" audience, not all the companies. How do we achieve this? Target shows the selection of Audience as whole , not a subset of Audience with some attribute. Thanks in advance. "

Link to original question: How to target an specific visitor inside the Audience group

[Drburns27]

@Amelia_WalianyWow, great question!  2 different methods for accomplishing this: you can obviously create the sub-segment within AA and pass that into Target, which may be helpful from a reporting perspective if you are using Analytics as your reporting source for Target.  Another method would be to exclude attributes or refine the AA audience within the Target audience builder on the Target end.  But I think I would go with the first option, given the reporting in Analytics that you would want.

[Drburns27]

Thank you everyone for such engaging and substantive questions!!