[AT Community Q&A Coffee Break] 5/27: Shannon Hamilton, Senior Adobe Target Product Manager

Good morning and thanks for taking time out of your day for us!

How do you handle tests where the numbers, be it audience, conversion rate or lift, are low and causes the test to take a long time? I'm talking years

Hi, @cjara1  - Most use cases are likely solved through the Audience Library - especially now that we've added the ability to combine multiple audiences and build out AND/OR/NOT logic inside of your audiences or audience combinations.  Profile Scripts are great for when you need to do mathematical operations, simple programming loops, or just need access to raw code to tweak your audience to do exactly what you want!  Some examples there are building out affinity scores based on page engagement, or counting certain interactions in the Target profile.  

---

@cjara1 wrote:

Hi Shannon,

Do you recommend using Audience Library segments over profile scripts for Target? How do you decide which to use?

---

---

@aseemp97838257 wrote:

A little confused with the below feedback from Adobe - we want to present Geo specific  content on our AEM pages but the below says to use Target

 

ADOBE'S RECOMMENDATION:

 

If you have purchased Adobe Target and are able to create activities within Target we DO NOT recommend using AEM to build those activities.  Building targeted activities directly within AEM will most definitely lead to performance degradation on the instance because of the JS required to render the targeted content.  This will occur even if you have implemented redirects on your pages.  The instance may not be noticeably impacted at first, but over time after continuous targeted content authoring, performance degradation is inevitable.

 

The issue with the above is the logistics of doing Geo AND Tests on same pages

---

Generally, we recommend using Target directly instead of via AEM where possible. You can combine tests and having different geo versions directly within your Target A/B activity. Both your needs would be covered in your activity by having different versions of each experience that have a geo-based audience associated with them. See: https://docs.adobe.com/content/help/en/target/using/activities/abtest/create/target-experience-to-multiple-audiences.html

Hi Jonathan,

We don't have a plan for passing in the clicked an element data to Analytics at the moment. I would recommend you post about it in the "ideas" section of the community so others can vote on it. I (and the rest of the PM team) review the community frequently for the top requests. 

We are expanding A4T support with allowing for lift and confidence in Analysis workspace, which will be helpful.  

---

@jonathanl557422 wrote:

Hi. For A4T, are there plans to include the Target conversions in analytics when the Target activity's goal has been configured as clicking a specific element (element has not been tagged in analytics)? Selecting to view the Target activity in analytics in this instance just shows the qualified traffic metrics and not the conversion.

---

@juliansam1 - A4T is being enhanced for both Auto-Allocate and Auto-Target throughout our June and summer releases.  Additionally, we are bringing A4T lift and confidence in to Analysis Workspace across the same time period!   Automated Personalization will continue to use Adobe Target as the data source for personalization.   

As we have the release dates established, check out our pre-release notes here to stay informed!

---

@juliansam1 wrote:

@ShannonHamiltonPM

When will A4T be enabled for Auto-Target and AP Campaigns to perform further analysis in Adobe Analytics?

---

---

@sath wrote:

Hi Shannon,

 

Thank you for this initiative. Am new to Adobe target, are there a detailed documentation on how to interpret the metrics data that we collect in Adobe Target.

---

Hi Sath,

Welcome to the Target community! We have robust reporting depending on which activity type you are using.

Here is the overall topic:   https://docs.adobe.com/content/help/en/target/using/reports/reports.html

Here is a helpful article on conversion and confidence: https://docs.adobe.com/content/help/en/target/using/reports/conversion-rate.html

Here is an article with reporting FAQs: https://docs.adobe.com/content/help/en/target/using/reports/reporting-frequently-asked-questions.html

Great question @6590328 - we fully support the legacy setup and in fact continue to support it in the latest Experience Platform SDK (alloy.js) which unifies data collection for all Experience Cloud applications.  You can learn more about that release here: https://docs.adobe.com/content/help/en/platform-learn/tutorials/data-ingestion/web-sdk/introduction-to-web-sdk-and-edge-network.html

Generally we find that one service call to Adobe is preferable than multiple calls, even if those calls are asynchronous.  The chief benefit of a single Adobe call for Adobe Target is that you can batch all of your experiments and personalization acitivites together with a call and response per page (or even pre-fetch actions with our AT.JS 2.0 branch for Single Page Apps) which greatly improves your performance and allows for experience changes to be fetched from a visitor's local memory, not our servers.   It also allows you to deploy rapidly on new properties and have a "global" reach for any part of any page. 

---

@nicholasr284932 wrote:

Hey Shannon,

 I've recently re-implemented target and went from my old multiple mboxes setup (global,home,pdp, etc) to a single global mbox as recommended by the adobe documentation. What are the advantages of the single global mbox? It feels like it just made page template targeting slightly more complex. Also, how long will Target still support the old multiple mboxes setup?

 

Thanks for your time today!

---