A/B test—Full

To request full A/B test information, set the abTestContent attribute in the tracking request to full.

track={ 
        type          : "home", 
	lang          : "en-gb",
	channel       : "web",
	abTestContent : 'full' 
      }

This results in the info callback being called with the following JSON data passed in.

Name					Description	Usage
abtest					An array of A/B test product records
	<productname>				The product name	Where <productname> is smartRecs.
		name			A/B test name	[String]
		group			The group assigned to the current visitor	[String]
		configs			A list of all Episerver A/B test configurations that deliver Peerius recommendations.	Note: If the current A/B group does not appear in this list, no Episerver recommendations are configured to be served for the current visitor.
			<group>		An array of configurations to be shown for this test group.	Where <group> is the test group letter, such as “A” or “B”.
				name	Item name	[String] The name of the widget, creative or listing that is shown if the test group letter matches the group assigned to the current visitor.
				position	The position of the item	[String] Describes the page position where the item will be shown.

For example:

{
  "abtest" : [{
                "smartRecs" : [{
                                 "name"    : "a/b test",
                                 "group"   : "A",
                                 "configs" : {
		                               "B" : [{
                                                        "name"     : "home",
                                                        "position" : "homejson"
                                                     }]
                                             }
                              }]
             }]
}

Do you find this information helpful? Yes No

Why wasn't this helpful? (check all that apply) Couldn't find what I was looking for Instructions confusing or unclear Instructions didn't work

Please tell us more! (optional)

We're doing our best to answer your questions in the documentation. If we have not, please explain what you are looking for.

If possible, provide your email address. We may contact you to fully understand your comments and update the documentation accordingly.

Email address (optional):

Last updated: Nov 06, 2017