Agent Checklist Before Running

This page aims to provide a brief checklist of some elements the team would like to go through before changing the agent status to Running to avoid having to pause the agent a short time after because of an unseen mistake in the setup.

Note that some elements of it can be done from the Conductrics Admin while others could require a dev to look at them on the implementation side.

The Agent Selection

Starting on the right-side bar of the agent home page, we encourage the team to look at the following:

1. Activates on page and URL Conditions: You can use the URL Tester provided in this section to make sure that the agent will run on the desired pages even if or when they include certain parameters or slight modifications.
2. Page Loads and View-States: Make sure that the agent selection "run time" is the intended one, and if using View-States , check that those are triggering when the targeted behavior occurs. If using programmatic view-states, you can work with your dev-team to ensure they are firing when and where intended.
3. Check whether Visitor Conditions are in place, specially if using Custom Visitor Traits or Custom Inputs. If using the REST-API work with your dev team to confirm that the needed traits or inputs are being properly included in the agent selection call.

The Experience

1. If its an Express Agent:
   Check that the WYS and/or Custom JS code is in place. This can be either done by checking each individually or by using the Preview Launcher.

2. If using a REST API agent:
   Make sure that after the agent selection happens, the code applies the desired changes. If not, you might want to contact your dev team to rule out any implementation issues.

The Goals/Conversion Collection

1. Ensure that the goals are included into the agent by selecting them on the right side-bar.
2. You can use the Preview Launcher or the QA flag and then replicate the goal triggering behavior to see if they are being recorded properly.
3. If using multiple Deploy Targets, make sure that the agent is also added to the DT that has the API Goal you are aiming to collect.
4. If sending goals programmatically, communicate with your dev team to ensure that the goal calls are triggering when and where desired.