Profile Script solution for dual reporting suites (tracking engagement on one and orders on another)

Question

Hi all, We are currently operating with two different websites (homepage where we are running tests on one and resulting orders on another).

I was provided a solution by Adobe to run my experiment as normal with the engagement metrics being measured (in one reporting suite) and to setup another XT using a profile script that looks for anyone who qualifies for my initial AB and track their orders associated with it (in the other reporting suite).

This solution worked but didn't separate the Control vs Experience orders - it just gave me one value of orders for the activity as a whole - not useful when trying to determine uplift against the control!

I need to amend the profile script to also look for the attribute 'experience.name' or 'experience.id' - this is the original script just looking for the activity qualification:

//retrieves all the activity IDs on the current page
var arrAct= user.activeActivities;

// Define the Activity ID to search for example
var numberToSearch = 123456;

// Search for the Activity ID in the array
var numberIndex = arrAct.indexOf(numberToSearch);

// Check if the Activity ID is found
if (numberIndex !== -1) {
// Activity ID found
return 123456;
} else {
// Activity ID not found
return false;
}

Can someone please help me figure out how i update this? I am using at.js and making the changes in the VEC. I saw a post in here about using response tokens to capture this info. I have configured the attributes in the response token and i can see them firing in the console but i don't know if the script above is referencing the tokens or how to update it to include the additional attributes.

Please advise! 🙂

alexbishop · Accepted Answer

One simple way to do this would be to add a short custom code script to each experience in VEC.
For example, in Control:

<script>
adobe.target.getOffers({
  request: {
    execute: {
      mboxes: [       
        {
          index: 0,
          name: "activity-data",
          profileParameters: {
            "activityDetails": "My Activity:Control"
          }
        }
      ]
    }
  }
});
</script>

And then for the Variant you can update "activityDetails" to "My Activity Name:Experience B", for example.

This would mean you wouldn't need the profile script, as the value you pass in the getOffers call is automatically tied to the profile

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded