☕[AT Community Q&A Coffee Break] 1/13/21, 8am PT: Robert Calangiu, Senior Product Manager for Adobe Target☕

@Robert_Calangiu  I don't see replies to my questions. 

---

@seattler5168376 wrote:

@robertcalangiu 

How do you determine whether you should use A4T or the reports tab in Target?

---

It really depends on what are you trying to achieve and if you want to correlate Target data with your Analytics data for better deep-dives and insights.

If you are interested mainly in your Target activity performance then you can use Target reporting (you can also use Target reporting when you just want a quick view on how your activity performs), but if you already have A4T integration enabled you can use directly Analytics.

@leoleoncio , as long as the URLs are all similar, I believe that this can be accomplished under the gear icon (configure) in the VEC -> Page Delivery -> + Add template Rule -> (contains, is, starts with, etc) ->  /common/url/path/

---

@kaps21 wrote:

@robertcalangiu Would AA sequential segments work in real-time, if used in a target activity for targeting visitors based on the path they take in the ongoing session.

---

With the current A4T implementation this is not really "real-time" because it takes a few minutes for Analytics and Target data to be stitched.

The scenario you describe will be possible in the future by using Adobe Experience Platform, with the unified Adobe Experience Platform SDK and Real-Time Customer Profile. Data from various sources can be sent to Real-time Customer Profile and marketers can augment Target audience with AEP/RTCDP segments to delivering a real time personalization experience.

Stay tuned for product announcements at Adobe Summit: https://summit.adobe.com/na/

---

@amelia_waliany wrote:

Hi @robertcalangiu this question was shared by CJara1: Is there a Launch extension for easier creation/tracking of Target profile scripts?

---

We don't have an official Launch extension for creating profile scripts, but customers can build their own extensions. 

Here: https://experienceleague.adobe.com/docs/launch-learn/implementing-in-websites-with-launch/implement-solutions/target.html?lang=en#library-header-and-library-footer

you have an in-depth tutorial in which we describe a Target implementation using Launch and you can also find how you can add parameters and custom requests. You can treat profile scripts as custom requests in Launch.

Some useful videos can be found here: https://experienceleague.adobe.com/docs/target-learn/tutorials/implementation/2.4-intro-to-target-params.html?lang=en#description and here: https://experienceleague.adobe.com/docs/target-learn/tutorials/implementation/2.6-next-steps-design-target-implementation.html?lang=en#description 

---

@amelia_waliany wrote:

Hi @robertcalangiu , thank you for taking the time today to share your expert guidance! This question was shared by catlady45: "What are the benefits of using Auto Target vs Experience Targeting?"

---

Hi @catlady45 ,

Experience Targeting (XT) is usually the first step of most personalization efforts. Experience Targeting allows you to set business rules to indicate what content/experience to deliver to each user, based on the segment to which that user belongs. Experience targeting does not utilize any machine learning for automation of experience delivery.
And it is typically used when we have information about segments that indicate a preference for a different user experience, OR when we have a reason to show different experiences based on some segment information (such as offers based on location, customer vs. prospect, etc).

Auto-Target serves the most tailored experience to each visitor based on his or her individual customer profile and the behavior of previous visitors with similar profiles.
Auto-Target automates rules-based targeting and ML, rather than the business rule, is deciding what the rule should be, based on actual user preference. This allows for “more intelligent” targeting or targeting at scale.

Unlike AB test where the experience allocation for a given visitor is sticky, Auto-Target optimizes the specified business goal over each session. And because Auto-Target can adapt to changes in visitor behavior, it can be run perpetually to provide lift. This is sometimes referred to as “always-on” mode.

---

@seattler5168376 wrote:

@robertcalangiu Hi!

Is it possible to move users to a new audience if they click on an element using A4T as the reporting source?

---

Using A4T integration and Analytics as reporting source makes this use case possible. 

You can have a segment created in Analytics with the users that clicked on an element and that segment will be shared with Target and can be used as an audience.

---

@amelia_waliany wrote:

Hi @robertcalangiu ! This question was shared by benrmorrill43:

"How to add dynamic content (ex. lead first name) using the VEC editor?"

 

---

You can do this by using the Edit Text/HTML option in VEC when you have content in place.

Do Edit -> Edit Text/HTML and enter the following code in the Code View of the HTML editor:

<div class="some-div-with-js-var-replaced">
<div class="placeholder-lastName">empty for the moment</div>
<script>
$(".placeholder-lastName").html(someJavaScriptVariable);
</script>
</div>

And here you have some documentation on how to use custom code in Target: https://experienceleague.adobe.com/docs/target/using/experiences/vec/modifications/vec-code-editor.html?lang=en#section_EE27E7572AA74397BBDED563B2B3D509

---

@jonathanl557422 wrote:

Hi @robertcalangiu 

 

What's the reasoning behind VRS's not being supported with A4T? Our use case is that we've setup VRS to only include desired production traffic. The parent report suite includes everything including bot traffic, dev traffic, etc. Using the parent to report on Adobe Target activities in Analytics results in questions around data accuracy.

 

If the VRS was created with only hit based segments, does that make a difference in whether the VRS can be selected when reporting Target activities?

---

A few of the reasons why Virtual Report Suites are not supported with A4T are:

- we cannot upload classification data to it (like activity and experience names)

- they don't offer "real-time" data reporting like the regular report suites are

VRS are not supported (selectable) in A4T even if they were created with only hit based segments.