🎯REQUIREMENTS TO PARTICIPATE 🎯
🎯**For those who have joined an Adobe Target Community Q&A Coffee Break before: please note that we are no longer using formal registration pages for these events - just be sure to Mark Your Calendars to sign in here to the Community on 12/8/21 @ 8am PT, and hop onto this thread for direct answers from Robert
Robert Calangiu is a Senior Product Manager responsible for evolving Adobe Target's UI. He was in charge with redesigning the Admin UI and now he is focusing on improving the Activity UI as well as with enhancing the A4T integration. Previously, Robert worked as a product manager for Adobe’s TV Everywhere portfolio, leading Authentication & Fraud Management solutions. He is passionate about building customer centric products and helping customers solve the right problems.
Curious about what an Adobe Target Community Q&A Coffee Break looks like? Be sure to check out our past 2020 Adobe Target Coffee Breaks, covering a WIDE variety of Adobe Target topics, and our latest thread from our 9/8/21 Adobe Target Coffee Break with @vishalchordia
Topics help categorize Community content and increase your ability to discover relevant content.
Zach - have you considered Monitoring Activities? Basically an Activity targeted to your Audience with Default Content? This would give you visibility into these audiences...if you couple that with A4T and an XT Activity type, you can see in Analytics the shifts in Audience Participation.
I had not, but I'm putting this on the todo list!
@Robert_Calangiu Has Adobe considered very a basic versioning system built into the "Offers" area. While this doesn't happen often, I have accidentally overwritten the contents of one offer with another. Luckily, I maintain my own rough versioning system outside of Target and was easily able to rollback my mistake. But I'd love for the versioning system to be built into Target. Even something as basic as timestamped prior versions would be good enough. I don't need diff check or anything like that.
Thanks so much for this feedback. In order to ensure that it is captured effectively, please feel free to share this as an "Idea" in the Community. You can do this by clicking here:
@Robert_Calangiu Has Adobe considered an automated change log for activities? I maintain my own change log in the activity notes, but for changes to audiences, experiences, offers, split percentage, goals, etc., I'd love if Adobe maintained an automated log of activity changes with basic descriptions. It would be great to have notes in that context as well, similar to how we have notes per entity in Adobe Experience Platform Data Collection Tags (formerly Adobe Launch).
This is something that we consider and it's on our list of to do things. Improved change log is something that multiple customers have requested.
@Robert_Calangiu I'm working to debug some unstitched hits in some of our flows. Using the Experience Platform debugger, it appears my Target hits are matching SDID's to previous Analytics hits, with Analytics hits further into the flow not having an SDID set. I'm also seeing repeated SDID's in subsequent Target hits. Do you have any advice on next steps to identifying the root cause of this?
Hi @DillanGump ,
You might want to check this troubleshooting guide to see if it helps: https://experienceleague.adobe.com/docs/target/using/integrate/a4t/troubleshoot-a4t/a4t-troubleshoot...
If there is no supplemental data ID in the Target call, confirm that the VisitorAPI.js file is loaded before at.js. If there is no supplemental data ID in the Analytics call, confirm that the Target call fires before the Analytics call.
Thank you for the link.
Are there any special considerations for debugging Target on Single Page Applications?
My Target calls appear to be firing before my Analytics call, but the Analytics call is starting before the Target call finishes. Is that expected/correct behavior?
This is the link for the SPA documentation: https://experienceleague.adobe.com/docs/target/using/implement-target/client-side/at-js-implementati...
I think that if the Analytics call is starting before Target call finishes might generate the problem you're seeing.
Thank you everyone for joining today's Coffee Break, it was great to be able to answer your questions!
Please mark your calendars to join us on January 19th for our next Target Coffee Break and first Target Coffee Break of the new year 🙂