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 🎯
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
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.
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?
At.js 2x stops support these parameters for Audience Creation:
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: 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: 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.