Check out the recording of the VERY FIRST installment of our Adobe Target Basics webinar series:
Date: THURSDAY, July 19th, 2018
Time: 8am - 9am PST
Join Adobe expert & all-star Adobe Target Community contributor, Ryan Roberts, as he guides attendees through the Adobe Target UI and the steps you can take to - design a solid test, build audiences, uncover the value of A4T (Analytics for Target), determine when to use the Visual Experience Composer versus the form-based composer, and even decide whether or not to apply automation to your optimization endeavors in Target.
Attended the webinar and have follow up questions? Post them below before you forget! We'll make sure you get your answers.
Ryan Roberts Senior 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.
Per the webinar Q+A yesterday...
Apparently custom code renders at the top of page or even in header. Doing it in-line will apply the text, html, or code changes where you make them. How do you actually determine when to use in-line vs. custom code? What is potential impact of change rendering at top of page vs. where you make them?
From Ryan Roberts:
I generally try to stick with the "in-line" type modification when possible. However, I find the custom code can sometimes be necessary or easier in some case - though there isn't a hard and fast rule that I'm aware of. Here are some example use cases I use custom code for: