PARTICIPATING IS EASY:
INSTRUCTIONS
Ryan Roberts, Principal Consultant, Adobe
Ryan runs pre-sales proof-of-concept engagements for clients across North America as an implementation and testing expert who helps clients verify how Adobe Target can meet their requirements and boost their digital marketing optimization efforts.
Gentry Lin, Principal Consultant, Adobe
Gentry is an Adobe Senior Solutions Consultant specializing in Adobe Target. She has extensive practice in Target client-side implementation, including single page applications. Coming from a background in Adobe Audience Manager and Adobe Analytics, Gentry is deeply versed in how Target's integrations within the Adobe Experience Platform can power personalization, activation, insights, and optimization. She loves to talk with customers about how Target's dynamic targeting capabilities can help customers develop their personalization programs.
Ryan Pizzuto Senior Consultant, Adobe
Ryan Pizzuto is a Senior Expert Solutions Consultant focused on Adobe Target. He has been working in the optimization space for 15 years, both on the client side building an optimization practice from the ground up and recently consulting some of Adobe’s largest, most complex customers helping them maximize value from Adobe Target. He is passionate about optimization and personalization and evangelizing the possibilities with Adobe Target.
Curious about what an Adobe Target Community Q&A Coffee Break looks like? Be sure to check out the thread from our latest 4/12/23 Adobe Target Coffee Break with Adobe Senior Consultants Matthew Bailie @MBailie and Georgia Frailey @Georgia_CA , with support from @simochen of the Adobe Technical Support Engineering team
Topics help categorize Community content and increase your ability to discover relevant content.
Or more directly - are we free to make the Category field in the Recommendations Product collection whatever we want it to be?
The out-of-the-box purpose is to capture the categories to which the product belongs. However, no mechanism validates if these are actual categories or not. So it would be possible to use it in any manner you see fit as long as you keep in mind new values will be appended to the list and will not overwrite old values.
Mihnea Docea "Committed to Excellence" | Technical Support Engineer | Adobe | 1 (800) 685-2950 #3 #2 #3 | docea@adobe.com
So if I set up a Feed to periodically import our Product classifications, if the classifications for a particular product (catalog #, Key in the classifications template) change, it will not overwrite the existing data?
Example:
on the first import, the Feed gets this data:
Product Classification | Target Collection Field | Example |
Key | id | 123456 |
Product Name | name | Old Product Name |
next week, we change the name in the classifications, and the Feed gets this data
Product Classification | Target Collection Field | Example |
Key | id | 123456 |
Product Name | name | New Product Name |
Won't we see the New Product Name in the Target collection?
Yes, that would update to the new value. All other variables work like that. The only one which appends is the "categoryId" This is why I called it out so it wouldn't take you by surprise.
Mihnea Docea "Committed to Excellence" | Technical Support Engineer | Adobe | 1 (800) 685-2950 #3 #2 #3 | docea@adobe.com
Ah, sorry, should have read the doc you linked first - it's just the (multi-valued) category values that append. This is great, then we can use both the affinity category (not sure how to get that into the Feed though) and ones from our product classifications.
Hi All,
I have implemented Adobe Target on Web SDK. In we are firing Adobe Target at the library top with the event type "web.webinteractions.linkClicks" and Analytics with the event type as "web.webpagedetails.pageViews". Is this the ideal way? If yes then we are seeing unspecified value for eVars as linkClick call fires before the pageView call.
Why can we combine the target call with the analytics page view call? What are the Pros and Cons for both cases?
Hi again! Thanks for providing the screenshot. You certainly can combine the rules, and in general that's how you could approach rules that don't have special considerations. I have a few questions:
More info on Target XDM field mappings here: https://experienceleague.adobe.com/docs/experience-platform/sources/connectors/adobe-applications/ma...
Following are the comments to your questions.
Thanks for sharing the extra details. There can be valid use cases where you would want the Analytics captured data to come later on page load, like if certain data elements aren't available at the top of the page. In those cases, doing two separate calls like you have can make sense. Unless you've customized it not to, that will end up sending two calls to AA. One with the library loaded sendEvent (without evars/props) and one with the window loaded. Just something to be aware of with your setup.
However, if all the data you pass in the evars/props is available at the library loaded time I would recommend consolidating those calls and XDM objects. In which case I'd make my library load sendEvent my web.webpagedetails.pageViews eventType and then drop the web.webinteraction attributes (they are likely just redundant with the web.webpagedetails attributes).
Hope that helps!
Is Adobe working on a solution to enable Adobe Target activities to be pushed to Iphone and Ipad products?
Hi @alisaberindea,
Are you talking about having Target activities run in mobile apps for iPhones and iPads? Or are you talking about something else?
No, Target Experiences are not showing in iPhone and IPad devices for website experiences.
The following is a blurb from: https://experienceleague.adobe.com/docs/target/using/audiences/create-audiences/categories-audiences...
Due to the new changes introduced in iOS 12.2, creating an audience with rules defined by Device Marketing Name and Device Model that specify iPhone Models is impacted. Target can no longer target users who have iPhones with iOS 12.2 (or later) installed on them. However, if those users do not have iOS 12.2 (or later), then the iPhone Model targeting continues to work correctly.
The iOS 12.2 (or later) update does not affect the identification of the following models because these models do not support upgrading to iOS 12.2: iPhone, iPhone 3G, iPhone 3GS, iPhone 4, iPhone 4s, iPhone 5, iPhone 5c, iPad, iPad 2, iPad / Retina display, iPad Retina (4th Generation), iPod Touch 4, and iPod Touch 5.
I was wondering if there are any plans to work on fixing this in the future? and if so what the timeline for this might be?
Hi @alisaberindea,
Thank you for clarifying! I don't believe there is anything on the Adobe side that can be done to change this situation. This is due to Apple changes to the UA string from their devices/OS. I will see if I can find any additional information but wanted to respond with what I have for now.
Hello! Thank you Ryan for your reply. I just wanted to check back in with you to see if you have any further updates on this. Would you have any advice for work arounds to enable us to make Adobe Target Experiences and A/B tests visible to iPhone users?
How can I create Adobe Target variable so that I can map it to 3rd party extension tool variable via Launch?
For example, in the below screenshot, I have my integration with 3rd part tool that is allowing me to pull 3rd party tool default variable directly from drop-down (Segment Field on the left-hand side) and I have to map it to Adobe Target Field/Variable(on right side).
This I have to do in order to sync the demographic info that 3rd party tool is capturing for me to flow into the Target Variable so that I can use that target variable to build audiences for personalization. But I am unsure how I can create this empty variable before mapping it to my 3rd party tool variable (Segment Filed in above screenshot)
@Ryan_Roberts_, @GentryLin, @ryan_pizzuto, and@MihneaD What would be you recommendation for transferring design files from Figma or similar platform to Target to test proof of concept before moving forward with development?
Views
Likes
Replies
Views
Like
Replies
Views
Likes
Replies
Views
Likes
Replies