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

@nicolas_swisscom indeed we have some limits in place right now, but I would love to hear more on your needs? Why you would like to extend these limits, on what entities and how this would help you better do your job? Looking forward for more info here.

@andyprout82 This is strange; are you sure that you've implemented AT.js in the location you are executing activities?  The js library file may not be implemented in this location, which would be the likely cause of not seeing server calls.  An mbox is no longer required around every element you wish to run an activity with; it's all delivered through a single tag to the page and the VEC or form-based composer.

@nicolas_swisscom , the "Objective" field under the "Goals&Settings" section is currently optional because it is mostly used as a detailed description of what are the objectives and goals you want to achieve with this activity. Some users are populating it and some of them don't. 

How making it mandatory will help you (or your team) in your day-to-day work? 

---

@nicolas_swisscom wrote:

@robertcalangiu In relation to Auto-Target the Target documentationsays: "In the future, this test bed will allow us to open our machine learning platform to our data-savvy clients so that they can bring in their own models to augment Target’s models."

Would you know when, where and how we can "bring our own model"?

---

The "bring your own model" or "Auto-Target with Custom Model powered by AEP" capability is currently in development.

I don't have a fixed release date that I can offer in this moment.

@ca90883831 wanted to provide some feedback in case you might be interested...

1. My experience is that you can have multiple mboxes placed on the page this includes a global mbox and a custom mboxes. I like to think of the global mbox as the one you fire on each page. This will make sure we can introduce experiences into the page using the VEC editor. Then if we have unique experiences using the form based editor, we then use a dedicated custom mbox so as to limit the scope.

2. Since the global mbox is focused on supporting use cases that leverage the VEC editor, and the VEC editor in turn captures a css selector from the user from one of the options when editing(insert after, before, or manually), the global mbox response on the client side will always have a "selector" value under "action" object. You can actually pass in this key value pair in your applyOffer() function and when the at.js script runs the script it will do the same and find the css selector and inject the html into that spot.

3. The auto create global mbox is something you can control at the script level, so you can create two versions of the script for each domain. Additionally if you use Launch you can control it from there.

4. Typically arrays perform slightly better than objects in terms of efficiency. I dont know if the at.js script has any conditions that look at one over the other first as an example therefor being executed faster.

Hope this helps and best of luck!

---

@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.

---

@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

---

@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 , 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.