Using mboxtrace to validate Target activity/offer entered from Chrome:
- Log in to Target and go to: “Administration > Implementation”
- Under the section: “Debugger tools” click on “Generate New Authorization Token”
- Copy the bold text (Not the text in the “Authorization Token” field) it should read something like this:
mboxTrace=window&authorization=6a7dad4a-8bcc-4466-a019-214d3a3bf098 - This is the extra code that you will need to add to the URL where you are checking to see if Target is running.
- Browse to the URL in question where you are testing.
- If the URL has no other URL parameters add the mboxTrace with a ? prefix if there are other parameters you will have to add it with a & prefix.
Example1: https://www.domain.com/?mboxTrace=window&authorization=6a7dad4a-8bcc-4466-a019-214d3a3bf098
Example2: https://www.domain.com/?param1=true&mboxTrace=window&authorization=6a7dad4a-8bcc-4466-a019-214d3a3bf098 - Open the browser console. (For Chrome right click anywhere and select “Inspect”)
- In the browser console switch to the “Network” tab.
- Filter/Search for: “.tt” (at.js v1.x) or “delivery” (at.js v2.x)
- Select a call in the left-side column.
- In the right column select the “Preview” tab.
- Expand the following sections: “Execute > Page Load > trace”
- There are two sections of interest here:
“campaigns” <-- Shows you a list of only the activities you qualified into.
“evaluatedCampaignTargets” <-- Shows you all of the activities that are running on this page.
