Here is a sample code - which works for me accordingly in at.js 1.x -
but not in at.js 2.x. If I would remove the action parameter - then it
works accordingly in both. var mbox = 'mboxName'; var selector =
document.querySelector('.className'); adobe.target.getOffer({ mbox:
mbox, success: function (response) { adobe.target.applyOffer({ mbox:
mbox, offer: [{ content: response[0].content, action: 'replaceContent'
}], selector: selector }); }, error: function (status, errorMsg) {
console.log(status,...
That the adobe.target.getOffer() and adobe.target.getOffers() are
different is clear to me. But the adobe.target.getOffer() at.js 1.x and
adobe.target.getOffer() at.js 2.x - should not really change anything.
Nevertheless, if I include in the offer Object an also action with
"replaceContent" - target replaces the selector only in the at.js 1.x.
In at.js 2.x I see also the response - it seems that the
adobe.target.applyOffer has a problem with it in at.js 2.x
The adobe.target.applyOffer function is used inside the
adobe.target.getOffer function.In at.js 1.x I could still set e.g.
"action" with e.g. "replaceContent" in the offer option. If I try the
same with at.js 2.x - it doesn't work. If I remove the "action" - then
it also works with the at.js 2.x for me.In source code I also found
"replaceContent" with the 2.x - and it should actually work, because the
applyOffer function was not changed. Does anyone know the problem? Is it
really because of this...
Hi @karandhawan and Community,it looks like the problem has been fixed
in the release.I had the problem that when I wanted to edit my
dependency changes, I can't see them anymore. But now I can see my
dependencies again - as it should be.Best regardsPerrin
Checked that again via the API. Here I see that the dependencies are
stored. I guess some kind of display error. At least you can see the
delete button - but not so good that it can't be edited - without
deleting everything.
Hello,I want to add a dependency to the metrics. With the overlay "Add
Metrics Dependency" I also add the conditions accordingly. If I then
click on "edit Dependency" again - the dependencies are deleted again.
Is this a bug - or does the dependency remain active until I click on
"edit Dependency"?This phenomenon is new to me. best regardsPerrin
Hello,if I get an activity e.g. via
https://mc.adobe.io/tenant/target/activities/ab/123456 and change only
the name of the activity in the JSON and send it to
https://mc.adobe.io/tenant/target/activities/ab/123456, then I get the
message: "Invalid Json. Unrecognized property name 'options'. Location:
line - 7, column - 17." "options": [{"optionLocalId": 0,"offerId":
0},{"optionLocalId": 2,"name": "Offer2.""offerId": 596872}], If I delete
this part, I get another warning. This time under experien...
Hi @HariharanSubra1, you can use targetpageparams to pass parameters
like
mbox3rdPartyId.https://docs.adobe.com/content/help/en/target/using/implement-target/client-side/functions-overview/targetpageparams.html
You can also pass the parameter mbox3rdPartyId after the
target-global-mbox call via e.g. adobe.target.getOffer.It is also
possible to wait for a service and then pass an mbox3rdPartyId to
target. For this purpose there are data providers. If you use the
Delivery API you should also repla...
Unfortunately, the adobe_mc_sdid parameter also bothers me with a
customer. With an HTML Offer I have to use something like this to avoid
flickering and to set the browser history correctly.body
{display:
none;}window.location.replace("www.xyz.com");However,
this method is slower than a Redirect Offer. For this reason it would be
better if this could be set directly in the Redirect Offer.
