Adobe Employee

☕[AT Community Q&A Coffee Break] 11/11/20, 8am PT: David Son, Senior Product Manager for Adobe Target☕

Forum|Forum|5 years ago
October 15, 2020
17 replies
11892 views

Join us for our next monthly Adobe Target Community Q&A Coffee Break,

taking place Wednesday, November 11th @ 8am PT

👨‍💻☕👩‍💻REGISTER NOW👨‍💻☕👩‍💻

We'll be joined by David Son, aka @DavidSonPM, Senior Product Manager for Adobe Target, who will be signed in here to the Adobe Target Community to chat directly with you on this thread about your Adobe Target questions pertaining to his areas of expertise:

On-device decisioning
At.js
Mobile
Alloy
APIs

💡Want us to send you a calendar invitation so you don’t forget? Register now to mark your calendar and receive Reminders!

🖥️️🗣️️Be sure not to miss the webinar from the day before, on Tuesday, 11/10/20 @ 10am PT, where @Jason_Hickey and @DavidSonPM will deliver a live webinar on how to Personalize and test at zero latency with on-device decisions from Adobe Target - bring all your burning post-webinar Q's to the chat thread below!🗣️️

A NOTE FROM OUR NEXT, 11/11/20 COMMUNITY Q&A COFFEE BREAK EXPERT, DAVID SON

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 @DavidSonPM
When exchanging messages with David about your specific question, be sure to use the editor’s "QUOTE" button, which will indicate which post you're replying to, and will help contain your conversation with David

David Son is a Senior Product Manager for Adobe Target where leads product strategy for mobile, APIs, and SDKs. He holds a B.A in Computer Science from the University of California, Berkeley and is based in San Francisco.

Curious about what an Adobe Target Community Q&A Coffee Break looks like? Check out the threads from our first Series of Adobe Target Community Q&A Coffee Breaks and from our last Break from 10/14/20 with Jon Tehero, Group Product Manager for Adobe Target

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Show previous replies

E

ecallender14

@davidsonpm

I have a question about integrating Target into a single-page application that mainly relates to experience type activities. The specific use case is for content that is setup to be displayed in a container that is shared across multiple screens in the SPA. What is the best way to manage hiding/showing the content when it is intended for only one of the screens?

To elaborate, without explicitly hiding or removing the content when the user transitions to a new screen, the content would continue to appear in the "global" container. Conversely, once the content is hidden or removed, it will not re-appear when the user transitions back to the original screen without explicitly re-inserting or un-hiding the content.

Any guidance on the best way to do this is much appreciated.

tszat

Level 3

@DavidSonPM

What are the main Target changes that we need to be prepared for when transitioning to Alloy?

DavidSonPM

Level 3

@tszat wrote:
@DavidSonPM
What are the main Target changes that we need to be prepared for when transitioning to Alloy?

I would say the main changes you need to be aware of are how audiences work. You must configure XDM in order to use Target for Alloy.js When defining Audiences for your Target activities that will be delivered via the AEP Web SDK, XDM must be defined and used. After you define XDM schemas, classes, and mixins, you can create a Target audience rule defined by XDM data for targeting. Within Target, XDM data displays in the Audience Builder as a custom parameter. The XDM is serialized using dot notation (for example, web.webPageDetails.name).

If you have Target activities with predefined audiences that use custom parameters or a user profile, be aware that they won’t be delivered correctly via the AEP Web SDK. Instead of using custom parameters or the user profile, you must use XDM instead. However, there are out-of-the-box audience targeting fields supported via the AEP Web SDK that do not require XDM. These are the fields available in the Target UI that do not require XDM:

Target Library
Geo
Network
Operating System
Site Pages
Browser
Traffic Sources
Time Frame

Please see this doc for more information - https://experienceleague.adobe.com/docs/experience-platform/edge/personalization/adobe-target/target-overview.html?lang=en#audiences-in-xdm

tszat

Level 3

Haven't heard much about Alloy and native app? I assume that is also coming.

jonathanl557422

Level 2

Quick UI feedback on trying to read the delivery API doc. When I'm scrolling through it, it autoscrolls me back up towards the beginning of the doc.

I'm using Chrome V86.0. Similar behavior seen in Chrome Incognito.

http://developers.adobetarget.com/api/delivery-api/

DavidSonPM

Level 3

@jonathanl557422 wrote:
Quick UI feedback on trying to read the delivery API doc. When I'm scrolling through it, it autoscrolls me back up towards the beginning of the doc.
I'm using Chrome V86.0. Similar behavior seen in Chrome Incognito.

http://developers.adobetarget.com/api/delivery-api/

We use ReDocs for generating API docs and this is a known issue in Chrome. You won't see this problem in Firefox. I suggest using Firefox for the time being. We are also in the progress of migrating to Gitbooks. You will slowly see the API docs also migrated there. In the meatime, SDKs are documented here - https://adobetarget-sdks.gitbook.io/docs/

J

Jason_Hickey

Adobe Employee

@davidsonpm wrote:
@jonathanl557422 wrote:
Quick UI feedback on trying to read the delivery API doc. When I'm scrolling through it, it autoscrolls me back up towards the beginning of the doc.
I'm using Chrome V86.0. Similar behavior seen in Chrome Incognito.

http://developers.adobetarget.com/api/delivery-api/
We use ReDocs for generating API docs and this is a known issue in Chrome. You won't see this problem in Firefox. I suggest using Firefox for the time being.

We are also starting a process of moving to a new (and better!) docs portal for our API documentation - stay tuned for news on that in future release notes.

tszat

Level 3

@DavidSonPM

Any plans to enhance data available in API? We previously looked at it for a reporting dashboard (detail what is currently running and where) and found that it didn't seem to have access to all the information we would want to have.

DavidSonPM

Level 3

@tszat wrote:
@DavidSonPM
Any plans to enhance data available in API? We previously looked at it for a reporting dashboard (detail what is currently running and where) and found that it didn't seem to have access to all the information we would want to have.

Please do add some fields you would like to see in the reporting API, and we will look into adding them!