Hi Soumyarani, I don't believe there's anything specific for pasting
offers directly into the VEC via an FTP or GIT, but you could use the
Adobe Target API to upload your code as
'offers':https://developers.adobetarget.com/api/
Hi harishkumar, This documentation has a pretty good breakdown of the
differences between 1.x and
2.xhttps://docs.adobe.com/content/help/en/target/using/implement-target/client-side/upgrading-from-atjs-1x-to-atjs-20.htmlBut
yes 2.x has a lot built around support for SPAs and most of the
functionality and improvements relate to it.
Hey Nicholas, From our experience the A4T reporting with be triggered
for both activities in the example you listed below even if technically
only one experience showed. That's because Target will return both
experiences onto the page but the priority will determine which gets
displayed. A lower priority campaign will get delivered first and
executed, and if there is a higher priority campaign, it will deliver
and execute last overwriting the earlier campaign (this is if they are
in the same loc...
Have a look at this page on priority:
https://docs.adobe.com/content/help/en/target/using/activities/priority.html
Basically if they're on the same page with the same priority, the one
that got activated last usually gets displayed (aka dropped last so it's
the change that doesn't get modified) From the documentation:If multiple
activities share the same priority level, then there are two
tiebreakers:If only one activity has audience targeting, that activity
is displayed.If all or none have targ...
Hey @zach_shearer , From my understanding, to use the 'Clicked on mbox'
method you need to wrap an mbox around the CTA and let the user actually
click on it. I believe you should try 'Viewed an mbox' as you are firing
the mbox after they click on it. Hope that works
Hey @gokula, yea I'm not sure if the Target body hiding script works
well with redirect offers. We ended up implementing our own one through
our tag mananger and listening for the at.js custom events to determine
whether there was an offer or redirect. With regards to VEC and not Form
based compooser, you are able to add a re-direct through 'change
redirect offer' in the content drop down after selecting an mbox
Hi @HugoNebreda Judging from what you described, our situation is also
quite similar. We use a build app to compile our separate HTML, CSS and
JS and perform any functions to make it Adobe Target offer compatible
(e.g. reusing popular tracking functions etc). We'd recommend using your
current source control system (we use Bitbucket) and then as part of the
build process, send the compiled code to Adobe Target via the Target API
as 'offers' Is there any possibility of integration with any major g...
Hi @gokula I'd recommend using the redirect offers instead of raw js
offers when redirecting people to different pages. More information
here:
https://docs.adobe.com/content/help/en/target/using/experiences/vec/redirect-offer.htmlIt
also supports sending to the final URL any query parameters included in
the source URL. In regards to seeing the old page, because the Target
library loads in a synchronous manner (i.e. it doesn't prevent page
load), the page will always load while Target loads befor...
Hi Community, We're currently trying to migrate off mbox parameters for
Audiences and using the AAM/Experience Cloud integration with Target
instead. We are currently using the Target Admin APIs to create Target
Audiences but is there a way to combine and create multiple Experience
Cloud audiences with the Target API? e.g. these audiences from this
screenshot:
Hi @Jon_Tehero thanks for hosting this session. Unfortunately can't join
live as I'm based in Sydney, Australia. Do you know if there is anything
on the roadmap for support Target.triggerView functions in the form
based composer?
Agree on wanting a similar feature! We currently manually create a
calculated metric for each A/B test for segments applied to our success
metrics (e.g. a car insurance purchase instead of a generic purchase)
which can be very tedious.
Hey Chris, As far as I'm aware - using triggerView in the form based
composer isn't available (+1 vote for this in the future). Have you
tried using the Adobe Target chrome extension? It helps to remove the
iframe busing headers on your
browser:https://chrome.google.com/webstore/detail/adobe-target-vec-helper/ggjpideecfnbipkacplkhhaflkdjagak
The only other thing around this is you could put an offer code on the
target-global-mbox and utilise the success events to watch for the
triggerView call t...
Hey Charles, I'm not sure this applies when using A4T and then creating
an Analysis Workspace for the Target Activity. I just tried archiving an
old campaign and then all the Analytics information zero'd out
Firstly, I think that these two custom events only work if you are
creating offers via the VEC and not using custom code offers. I assume
that content render start firing is not tied directly to the hide code?
Hi community! Just wanted to ask a question about A4T. When you archive
an Adobe Target activity - does it remove all the historical reporting
for workspaces created in Adobe Analytics when the experiment was setup
using A4T?
Rather than trying to create a dynamic audience based on user input, is
it possible that you deploy the offer that changes the banner dependent
on bank number rather than setting an audience first? If you need to any
reporting, perhaps you can fire off analytics requests? Would that
approach work instead? Otherwise you could try user profile scripts.
Instead of trying to use update activity API request, are you able to
use the update activity request instead?API documentation:
https://developers.adobetarget.com/api/#update-activity-namecurl -X PUT
\ https://mc.adobe.io//target/activities/168816/name \
-H 'authorization: Bearer ' \ -H 'cache-control:
no-cache' \ -H 'content-type: application/vnd.adobe.target.v1+json' \ -H
'x-api-key: ' -d '{ "name": "New Name for Activity" }'
I'd really like to get some insights on this too. As far as we're aware,
the reason this was done was to keep the new Delivery API performant.
However restricting to 50 customer mBox parameters can be quite
limiting. Is anyone hitting this limit as well, and if so what
strategies are you employing to overcome this?
Hey, we just upgraded to at.js 2.3 from at.js 1.7 with the new Delivery
API and we noticed that we were getting this error:After looking into
it, we found this documentation that the Delivery API has a limit of 50
mbox parameters where as the previous library had a limit of
500.https://docs.adobe.com/content/help/en/target/using/troubleshoot/target-limits.html
Can anyone confirm? We are currently using mbox parameters to pass along
customer profile data from our CRM and definitely have instances...
Hey there!First time posting here Also want to up-vote this one. We've
been experimenting with the Target APIs for creating offers as well and
noticed that updating an activity isn't accurately displayed in the UI.
e.g. If we pause an activity via the Target API, it's not accurately
displayed yet in the Target UI, so other stakeholders may get confused.
What's the typical time it takes to get the activity updated in the UI?
