The Campaign Debugger tool gives you the details of all Marketing Cloud Personalization activity and data on a page, including:
Before you can enable and use the Campaign Debugger, your dataset needs the following:
To use the Campaign Debugger, do the following.
https://ACCOUNT_NAME.evergage.com/beacon/ACCOUNT_NAME/DATASET_NAME/scripts/evergage.jsThe rest of this article details the specific functionalities of the Campaign Debugger including:
At the top of the debugger tool you’ll see information regarding the account, dataset, beacon version, as well as an input box and toggle for testing campaigns and experiences. If you’re interested in testing a particular campaign, type a partial campaign name in this box to see it in the dropdown, even if it’s disabled. After it is selected, you’re free to begin testing.
There are two modes you can test in using the Campaign Debugger:
Campaign Testing Mode
If you want to test a campaign to see how would behave on your site for your user account without publishing it:
evergageTestMessages=[CAMPAIGN_ID] in the URL.
This will cause the campaign to act like it’s published so you can test changes outside of the campaign editor.
You will see whichever campaign experience your user account would qualify for. This testing mode adheres to all of
the rules configured for the campaign and experiences. This means that there is a chance your user account is ineligible to see the campaign so you won’t see anything displayed on the screen. This does not mean that the campaign
is not working, since it may be simply that you didn’t qualify to see it either due to campaign or experience rules, or
being added to the campaign or experience control group.Experience Testing Mode
If you want to test a campaign’s specific experience:
evergageTestMessages=[EXPERIENCE_ID] in the URL.
Experience Testing Mode behavior will be different from Campaign Testing Mode behavior because this mode forces your user account to see the specific experience you selected in step 2 even though you may not naturally have qualified to see it. This is because Experience Testing Mode ignores any rules at the campaign and experience levels and forces you into the default test group (i.e. you won’t see the control). While this mode may not simulate the exact behavior of the published campaign, it will give you the opportunity to preview aesthetic changes outside of the Visual Editor.If you don’t see the experience with evergageTestMessages=[EXPERIENCE_ID] in the URL, there may be some other issue with the campaign. For example, recommendations aren’t returning from the server and there’s nothing to render. If this happens, the Campaign Explanations panel may help elucidate further information. See details below.
Note
This section shows the raw event JSON going to the Personalization server. This includes details like:
If there is a mapped item on the page, item data will be shown. This data includes:
This section shows a list of campaigns returned from the server for this event. These are campaigns that were returned as part of the response and (assuming the template client-side code handled the response properly) rendered onto the page.
The details included are:
The last section of the Campaign Debugger shows which campaigns did not make it back from the server for this event. This can be due to several common issues, including:
j