Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Is there a way to get test metadata through the browser.

anthonym7518193
Level 2
Level 2

Currently the getOffer method only returns the "action" portion of the returned json from target. When looking into the network panel of my browser, I can see all the other data available in the response object (Info like test name, experience id,  activity id). However, I have no way of grabbing this data.

I have seen suggestions around putting this info into the a/b test you create but that will not work for me because I need it pick up 100s of running test's metadata without changing them. Does anyone have a suggestion for getting this metadata from an API call or chiseling it out of the getOffer response?

1 Accepted Solution
anthonym7518193
Correct answer by
Level 2
Level 2

Hi Rohit,

Thank you for responding so quickly. Unfortunately the responseTokens/plugins would have to be configured before implementing at.js. This was my original problem. I work for a large company with a lot of distributed teams so having everyone reimplement at.js in their codebase isn't possible. I essentially needed to come up with something that is backwards compatible with every teams implementation of at.js. Fortunately I was able to figure out a way to make this happen late last night. Here's how:

We have a tag manager implemented on every team's page. I created a tag that makes it's own HTTP request to Adobe Target containing our mBoxHost, mboxURL, mboxName and an mBox Session number (which I just set to "1") . That request returns the actual response in from Target with all the responseTokens and data I needed.Hope this helps someone in the future.

- Eden Mazzola

View solution in original post

3 Replies
jrohit
Employee
Employee

Hi,

I am not sure if you gone through the below link on response tokens, but it gives you information around capturing data about campaigns.

Response Tokens

~Rohit

anthonym7518193
Correct answer by
Level 2
Level 2

Hi Rohit,

Thank you for responding so quickly. Unfortunately the responseTokens/plugins would have to be configured before implementing at.js. This was my original problem. I work for a large company with a lot of distributed teams so having everyone reimplement at.js in their codebase isn't possible. I essentially needed to come up with something that is backwards compatible with every teams implementation of at.js. Fortunately I was able to figure out a way to make this happen late last night. Here's how:

We have a tag manager implemented on every team's page. I created a tag that makes it's own HTTP request to Adobe Target containing our mBoxHost, mboxURL, mboxName and an mBox Session number (which I just set to "1") . That request returns the actual response in from Target with all the responseTokens and data I needed.Hope this helps someone in the future.

- Eden Mazzola

View solution in original post

brianh96587047
Level 2
Level 2

I think plugins should be brought back for this very reason.  Why go back and have to change a whole implementation when we had something that allowed us to easily use without touching the at.js source code.