Hi Community, Wanted to check that we're taking the right steps
regarding consent management and the Adobe Target mbox cookie. We use
Google Tag Manager in parallel with OneTrust to suppress analytics and
functional cookies, setting the approval/disapproval values as triggers
for the relevant tags. This works fine for all other tags, but Adobe
Target (at.js) is hardcoded on the site, not loaded through GTM. So
regardless of the value for consent against the mbox cookie within
OneTrust, the Targe...
Thanks Chris. Yes, I've got the extension but the site itself - our
logged in area - is iframe busting (I think that's the right term), so
only the third-party chat widget shows in the bottom right corner. I've
been trying to resolve this with our dev team for a while, but no luck
so far. Good to know at least that there's not something I'm missing.
This is definitely a feature I'd want to see in the future.
Hi all, I see that for SPAs, triggerView() fires a 'delivery' network
request for a 'notification', much like a metric used under
adobe.target.trackEvent(), rather than 'content' as seen with
adobe.target.applyOffer(). I understand how to configure builds against
triggerView in the VEC, but we have issues with the VEC in our secure
account area, in that security issues currently restrict the site being
viewed through an iFrame. This makes editing very tricky. My question is
therefore: Is it poss...
We have a secure account area for visitors signed up to our business,
and within that interface we have multiple mboxes hosting BAU messages
and various third party advertisements. The content of these individual
mboxes are managed by different teams who need access to publish only in
those particular areas. Theoretically I don't see why we couldn't pass
different at_property parameters at an mbox level rather than in the
'global' via targetPageParams(). We already use getOffer() and