Is there a way to get test metadata through the browser. | Community
Skip to main content
anthonym7518193
anthonym7518193
Level 2
March 20, 2018
Solved

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

  • March 20, 2018
  • 3 replies
  • 3704 views

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?

    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 anthonym7518193

    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

    3 replies

    A
    Adobe Employee
    ArchitectAdobe Employee
    Adobe Employee
    March 21, 2018

    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
      anthonym7518193AuthorAccepted solution
      Level 2
      March 21, 2018

      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

        B
        brianh96587047
        Level 2
        March 21, 2018

        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. 

          Terms & ConditionsAccessibility statement

          Loading footer...