Betreff: [AT Community Q&A Coffee Break] 6/10: David Son, Adobe Target Product Manager

[Amelia_Waliany]

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

taking place Wednesday, June 10th @ 10am PDT

--> REGISTER NOW <-- 

We'll be joined by David Son aka @DavidSonPM, Adobe Target Product Manager, 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 her areas of expertise:

• At.js
• Mobile
• Alloy
• APIs 

Want us to send you a calendar invitation so you don’t forget? Register now to receive a reminder!

A NOTE FROM NEXT WEEK'S 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 product manager for Adobe Target where he 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, California.

Curious about what an Adobe Target Community Q&A Coffee Break looks like? Check out the thread from our last break with Shannon Hamilton, Senior Adobe Target Product Manager

[DavidSonPM]

Hi everyone! Welcome to the coffee break. Really excited to answer your questions!

[Mark-Talbot-Adobe]

Hello

[drewb6915421]

Hi David!  Given your product focus, can you speak to the benefits of a hybrid deployment approach i.e. client-side and server-side within the same Target account?

[DavidSonPM]

Hi Drew, thanks for your question. Adobe Target's hybrid deployment allows for customers to utilize both the VEC (our WYSIWYG editor) as well as integrate with our SDKs and APIs on the server-side. This is very beneficial to customers who have both marketers and developers in their organization that have different use cases when it comes to personalization and experimentation. Adobe Target's hybrid deployment allows for these two personas to deliver personalization and experimentation at the same time without having to override each other and spend countless hours coordinating campaigns.

[target_user_dn]

Hi David,

I have a question on estimating Automated Personalization traffic:

The Adobe Help pages says, "Ideally, for a successful activity, the correct sample size ensures that personalized content is ready within 50% of the activity duration or 14 days, whichever is less. This allows sufficient time for obtaining personalized content and learning which content to deliver."

For example, if the activity duration is 10 days, does this mean the traffic estimator shows the sample size needed to run in 5 days?

[Nicolas_Swisscom]

@DavidSonPM: Can you share a bit about the roadmap for Mobile SDK? The VEC for mobile Apps has "gone". Any new exciting stuff coming?

[DavidSonPM]

---

@Nicolas_Swisscom wrote:

@DavidSonPM: Can you share a bit about the roadmap for Mobile SDK? The VEC for mobile Apps has "gone". Any new exciting stuff coming?

---

Hi! For users who want to execute personalization and experimentation on mobile apps, Target has a powerful and flexible utility called form-based composer. This allows customers to deploy activities with the added flexibility for choosing response types like JSON and images that allow developers to pursue advanced use cases that revolve around feature-flagging. We are looking at ways where we can enhance the form-based composer so that customers can deploy activities with more ease for their mobile apps.

[krispnguyen]

Hi David, 

At.js 2x stops support these parameters for Audience Creation:

• browserHeight
• browserWidth
• browserTimeOffset
• screenHeight
• screenWidth
• screenOrientation
• colorDepth
• devicePixelRatio

The Consulting team found a way to manually add these params under targetPageParams to target these in audience creation. My question is: Why was it not supported in at.js 2x OOTB and will there be a plan to allow these params to work in Audience Creation?

[DavidSonPM]

---

@krispnguyen wrote:

Hi David, 

At.js 2x stops support these parameters for Audience Creation:

• browserHeight
• browserWidth
• browserTimeOffset
• screenHeight
• screenWidth
• screenOrientation
• colorDepth
• devicePixelRatio

The Consulting team found a way to manually add these params under targetPageParams to target these in audience creation. My question is: Why was it not supported in at.js 2x OOTB and will there be a plan to allow these params to work in Audience Creation?

---

Hi, these parameters were supported in At.js 1.x, however At.js 2.x is now powered by a completely new API and so passing params will not work. We are looking at ways where we can add these params to audience creation instead.

[Nicolas_Swisscom]

@DavidSonPM: There seems to be some confusion about "Adobe Mobile Services" which includes Analytics, Places, DeepLinks, Push Notifications and in-App Messaging. We are wondering if this will continue to exist or be replaced or simply be "retired"? Adobe was recommending to use AppFlyer regarding the DeepLinks feature but I get a lot of questions from colleagues if and when "Adobe Mobile Services" will stop to exist?

[DavidSonPM]

---

@Nicolas_Swisscom wrote:

@DavidSonPM: There seems to be some confusion about "Adobe Mobile Services" which includes Analytics, Places, DeepLinks, Push Notifications and in-App Messaging. We are wondering if this will continue to exist or be replaced or simply be "retired"? Adobe was recommending to use AppFlyer regarding the DeepLinks feature but I get a lot of questions from colleagues if and when "Adobe Mobile Services" will stop to exist?

---

Unfortunately I do not lead Adobe Mobile Services so won't be able to give much meaningful guidance here.

[Nicolas_Swisscom]

Who could I contact regarding "Adobe Mobile Services" to find out more?

[Amelia_Waliany]

Hi @DavidSonPM, do you have any advice for customers on how a Json Offer can be retrieved from a Target API? Any outstanding key points to know would be really helpful! (this question was originally posted by fellow Adobe Target Community member @ms2654434 )

[DavidSonPM]

---

@Amelia_Waliany wrote:

Hi @DavidSonPM, do you have any advice for customers on how a Json Offer can be retrieved from a Target API? Any outstanding key points to know would be really helpful! 

---

Yes, absolutely. Our Target APIs allow developers to execute advanced experimentation use cases such as feature flagging which allows you to test algorithms, entire layout redesigns, and conversion flows. Developers can use our Delivery API to retrieve these JSON offers which can contain feature flags. For example, if I want to test a new search algorithm, you can create a JSON offer with "search_algorithm_feature":"algorithm-1" and utilize Target for decisioning. When calling the Delivery API for a given mbox, you can look at the "content" field to retrieve the flag as you see in the file attached.

[Amelia_Waliany]

Hi @DavidSonPM How can we optimize Target's performance when integrating with the server-side?

[DavidSonPM]

---

@Amelia_Waliany wrote:

Hi @DavidSonPM How can we optimize Target's performance when integrating with the server-side?

---

Great question. Adobe Target allows developers to use prefetch so that experiences can be retrieved from Target ahead of time and cached on the browser or mobile app so that the rendering and execution of the experience on a channel can be done immediately when the end user interacts with your application. When the prefetched experience from Target is rendered, developers can send a notification call to Target to increment reporting data.

[Amelia_Waliany]

Hi @DavidSonPM this question was originally posted by fellow Adobe Target Community member, @Umamaheswari_Yakkala : Can we use the Adobe Target API to create audiences from 3rd party tools other than the Adobe module?

[DavidSonPM]

---

@Amelia_Waliany wrote:

Hi @DavidSonPM this question was originally posted by fellow Adobe Target Community member, @Umamaheswari_Yakkala : Can we use the Adobe Target API to create audiences from 3rd party tools other than the Adobe module?

---

You can use our Admin API to create Audiences that are sent to Adobe Target so that we can understand which activity to show your end user. One thing you can do is translate your audience definition from your 3rd party tool to what Adobe can understand and allows for in the Admin API to create an audience. This will ensure the audience resolution for your activities are done correctly and your users see the right experience.

[Amelia_Waliany]

Hi @DavidSonPM, this question was originally posted by fellow Adobe Target Community member, @mezpahlan : How to get Target Preview working with new AEP library? 

I'm trying to get Target Previews working with the new AEP library for Target. Previously we were using the v4 Mobile Library:

com.adobe.mobile:adobeMobileLibrary:4.y.z

 Now we're trying to migrate to the new AEP SDKs:

implementation "com.adobe.marketing.mobile:sdk-core:1.y.z"
implementation "com.adobe.marketing.mobile:analytics:1.y.z"
implementation "com.adobe.marketing.mobile:userprofile:1.y.z"
implementation "com.adobe.marketing.mobile:mobileservices:1.y.z"
implementation "com.adobe.marketing.mobile:target:1.y.z"

The documentation https://docs.adobe.com/content/help/en/target/using/implement-target/mobile-apps/target-mobile-previ... says this: 

Android: In the app , call Config.trackAdobeDeepLink(URL); when the caller is asked to open the resource with the URL scheme that was specified in the previous step. 

Which worked fine when we were using the v4 Mobile Library, but I can't seem to do that with the new libraries. What's the new recommended way to continue to use Target Preview? Or is there an alternative?

[DavidSonPM]

---

@Amelia_Waliany wrote:

Hi @DavidSonPM, this question was originally posted by fellow Adobe Target Community member, @mezpahlan : How to get Target Preview working with new AEP library? 

I'm trying to get Target Previews working with the new AEP library for Target. Previously we were using the v4 Mobile Library:

com.adobe.mobile:adobeMobileLibrary:4.y.z

 Now we're trying to migrate to the new AEP SDKs:

implementation "com.adobe.marketing.mobile:sdk-core:1.y.z"
implementation "com.adobe.marketing.mobile:analytics:1.y.z"
implementation "com.adobe.marketing.mobile:userprofile:1.y.z"
implementation "com.adobe.marketing.mobile:mobileservices:1.y.z"
implementation "com.adobe.marketing.mobile:target:1.y.z"

The documentation https://docs.adobe.com/content/help/en/target/using/implement-target/mobile-apps/target-mobile-previ... says this: 

Android: In the app , call Config.trackAdobeDeepLink(URL); when the caller is asked to open the resource with the URL scheme that was specified in the previous step. 

Which worked fine when we were using the v4 Mobile Library, but I can't seem to do that with the new libraries. What's the new recommended way to continue to use Target Preview? Or is there an alternative?

---

Please review this documentation for preview support in v5 - https://aep-sdks.gitbook.io/docs/using-mobile-extensions/adobe-target#visual-preview