Retrieving Target offers via alloy.js | Community
Skip to main content
jgrubbs
jgrubbs
Level 3
September 25, 2021
Solved

Retrieving Target offers via alloy.js

  • September 25, 2021
  • 1 reply
  • 3250 views

Hello all,

 

Cracking more into our implementation of alloy.js with a goal of replacing all of the legacy Adobe libraries...

Right now we use at.js and make a call to getOffers() with some parameters to retrieve eligible activities/experiences. Then we call applyOffers() to  execute them.

 

I'm have a difficult time trying to get this to work via alloy.js. I've followed the instructions here to the letter, and even tried myriad combinations/changes, but I get empty decisions and propositions arrays every time.

https://experienceleague.adobe.com/docs/experience-platform/edge/personalization/adobe-target/target-overview.html?lang=en

 

We don't use "views" as such... We simply have activities and experiences in Target, some with custom code, some via the VEC. Nothing particularly special. Also, there is an implication in the documentation that "decisionScopes" are synonymous with mboxes, but when I try to pass the global mbox name, I get an error stating that I shouldn't do that.

 

In the datastream configuration, Target is enabled and the client code and environment code are both set

 

 

Is there an alloy command and syntax that indeed parallels the getOffer()-applyOffer() functionality provided by at.js?

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by jgrubbs

And.... I just figured it out. I've been testing with a "dummy" A/B test that doesn't actually do anything. Both variations are simply default content.

 

When requested via getOffer() with at.js, Target does in fact select my Activity and deliver it (as seen in the responseTokens), however with alloy and 'sendEvent', nothing is returned. It isn't until I make the test actually do something, then I get the expected response.

 

I'm not sure if this is a bug or a feature, but figured I'd this here in case someone encounters the same debacle in their implementation

 

1 reply

jgrubbs
jgrubbsAuthorAccepted solution
Level 3
September 25, 2021

And.... I just figured it out. I've been testing with a "dummy" A/B test that doesn't actually do anything. Both variations are simply default content.

 

When requested via getOffer() with at.js, Target does in fact select my Activity and deliver it (as seen in the responseTokens), however with alloy and 'sendEvent', nothing is returned. It isn't until I make the test actually do something, then I get the expected response.

 

I'm not sure if this is a bug or a feature, but figured I'd this here in case someone encounters the same debacle in their implementation

 

D
Adobe Employee
dwright-adobeAdobe Employee
Adobe Employee
October 1, 2021

Response tokens should now be supported with Web SDK v2.6.0. Are you using an older version?

https://experienceleague.adobe.com/docs/target/using/administer/response-tokens.html?lang=en

jgrubbs
jgrubbsAuthor
Level 3
October 1, 2021

Hi there, thank you for replying 🙂 

I am using 2.6.4, but this isn't so much an issue with Response Tokens but rather Activities with "empty" Experiences, or Experiences with no modifications (custom code or VEC, etc). We use such Experiences for our control groups or default content.

 

Using at.js, if I fall into one of those control or default content tests, the response from Target still has all of the response tokens, but of course there are no modifications in the response payload. This is expected behavior.

 

...But with alloy, in those cases, not only do I not get any "propositions" back, but the response tokens are absent as well... The response is basically empty--zero propositions.

 

Terms & ConditionsAccessibility statement

Loading footer...