We’re unable to get the Adobe Campaign personalization button enabled on
our editable AEM email templates that live under the /conf
directory.We've attempted to follow along with the community post here:
but it doesn't provide detail about the actual process to make the
button work. How would we go about making the Coral UI Button available
for Adobe Campaign metadata pi...
Thanks, @mikewebguy We're doing that today. I'm actually looking to see
if I can leverage the AAM audiences available in Target without relying
on cookies. Since we know everyone we're emailing and we have the hashed
ID in both Campaign and as an ID in our AAM audiences, can I pass that
hashed ID in the Target url call to match into an audience and thus,
serve the correct experience.
We have a hashed ID for our customers that we know lives in our AAM
audiences. We would like to pass that ID as a URL parameter (we're using
a non-js implementation in email) to Target to match that customer into
the AAM audiences we can access within Target. Can this be done?
Is it possible to change out the actual component shown per segment
using ContextHub? To provide more context, I would like to use a layout
container component with two open spots and switch out the nested
components per segment. Can this be done?
An additional thought/question here.If A4T is unable to capture these
impressions because a site visit is not triggered for Analytics to
capture, would the implementation of Analytics using an html tag
(through a pixel dropped in the email) help make that connection?
Implementing Analytics using HTML image tags
I am able to capture click data when attempting to serve up Target
content in emails deployed via Campaign Classic; however, when I run
tests focused on impressions for the Target content, nothing comes back
via A4T.Is it possible to capture those impressions?