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

A/B Server side

pchard
Level 2
Level 2

I'm a back-end developer very new to adobe target so would appreciate any help.
So we have a site where you can run a search, this site calls our search api and in order to investigate how best to tweak our search algorithm we need to pass a new value in the search request to the search api which will come from an a/b test.
We are going to have three scenarios,
1) control: value of 0
2) variant 2 value of 60
3) variant 3 value of 40
My question is really how to set this up as an A/B server side test?
Do I create 3 experiences and have an mbox as the location in each experience and then modify the content of each experience to reflect the value needed? Or is it better one experience with 3 locations and an mbox with a different value in each location?
At the time the search is run I will be writing code to query adobe target and get the mbox value.
Also not sure how the activity urls come into play?

1 Accepted Solution
Eric_Vidana
Correct answer by
Level 8
Level 8

Are you trying to do a simple 1/3 1/3 1/3 split on the scenarios mentioned? If so, an AB test would suffice and just have each experience return a json property that you are ready to code for. As for the API call itself, the Target docs are pretty good on this front:

https://developers.adobetarget.com/api/delivery-api/#section/Getting-Started

Activity url is just something that you tokenize/hard-code in your API request so that Target knows if you are qualifying for a production or non-prod activity. 

 

View solution in original post

1 Reply
Eric_Vidana
Correct answer by
Level 8
Level 8

Are you trying to do a simple 1/3 1/3 1/3 split on the scenarios mentioned? If so, an AB test would suffice and just have each experience return a json property that you are ready to code for. As for the API call itself, the Target docs are pretty good on this front:

https://developers.adobetarget.com/api/delivery-api/#section/Getting-Started

Activity url is just something that you tokenize/hard-code in your API request so that Target knows if you are qualifying for a production or non-prod activity. 

 

View solution in original post