When interacting with the consumer experience of Extole, the default assumption is that any interaction is a part of the live campaign and data should be tracked as live data in the dashboards. To make sure that your test events such as shares, purchases, revenue, etc. don’t get counted in the My.Extole analytics dashboards, we recommend you set up the appropriate sites and users to create test events. Functionally, nothing will change when a site or a user is flagged to create test events; the only difference is that those events won’t be counted in the dashboard analytics.

​

Flagging a Program Domain Site as a Test Site

When you set up a program domain, you are setting up a way to manage information about your website and program that is independent of any individual campaign you might be running. If you use a development or staging environment, you will want to ensure that Extole content can be served on the site but that events from the site will not be counted in your analytics. To flag a site as a test site, navigate to your Tech Center in My.Extole. If you are editing an existing program domain, click the edit icon next to it in the table. If you are creating a program domain for the first time, click the “+ New Domain” button. You will want to add in any sites you would like to be identified as test sites in the “Test Sites to Enable Javascript” field. After you save your changes, any events occurring on those sites will not appear in your My.Extole dashboard analytics. For more on how to set up a program domain for the first time, please see this article.

​

Flagging a Site as a Test Site via My.Extole

To flag all events from a specific site as test events, navigate to your Tech Center, scroll to the section titled “Test Data Rules”, and click on the “New Rule” button. Under “Rule Value”, enter the site URL of the program domain whose events you wish to exclude from your dashboard analytics (e.g. www.example.com). Under “Rule Type”, select “Site”, and under “Container”, indicate which container you’d like the events to be counted in. If you want the metrics counted in a test container, name this “production-test” and press Save.

​

Flagging an Extole User as a Tester via My.Extole

To flag an Extole user’s events as test events, navigate to your Settings page in My.Extole. In the Team section, find the team member whose events you wish to put in a test container and click on the edit icon. Scroll down to the Test Container section and toggle on the switch. All subsequent events associated with this email address will not show in your dashboard analytics.

​

Flagging a Non-Extole User as a Tester via My.Extole

To flag a non-Extole user’s events as test events, navigate to your Tech Center, scroll to the section titled “Test Data Rules”, and click on the “New Rule” button. Under “Rule Value”, enter the email address of the non-Extole user whose events you wish to exclude from your dashboard analytics (e.g. user@example.com). Under “Rule Type”, select “User”, and under “Container”, indicate which container you’d like the events to be counted in. If you want the metrics counted in a test container, name this “production-test” and press Save.
​

​

Flagging all Events from a Specific Email Domain as Test Events via My.Extole

To flag all events from users using a specific email domain as test events, navigate to your Tech Center, scroll to the section titled “Test Data Rules”, and click on the “New Rule” button. Under “Rule Value”, enter the email domain you wish to exclude from your dashboard analytics (e.g. example.com). Under “Rule Type”, select “Email Domain”, and under “Container”, indicate which container you’d like the events to be counted in. If you want the metrics counted in a test container, name this “production-test” and press Save.

​

Flagging a User as a Tester Using an Extension

There is another way to make your test events invisible in the dashboard analytics, though it is more difficult. The way to do so is by adding an extension to your browser. If you’re using Chrome, we recommend an extension called ModHeader available here. The screenshots below are for the ModHeader extension. For Firefox, the Modify Headers extension works well. After installing the extension, you will want to configure it to be enabled in incognito/private browsing mode. This is because you often use an incognito window to test receiving friend click coupons to avoid being flagged as a self-referral. For Chrome, you do this by:

1. In your URL bar, typing: chrome://extensions
2. Clicking “DETAILS” for the ModHeader extension
3. Turning on “Allow in Incognito”

Next, add a custom header of “X-Extole-Container” with a value of “test”. You do this by clicking the blue icon for the extension next to the URL bar and adding a new header by clicking the ”+” button. Make sure you add as a “Request Header”: *If you ever want to make a real referral and have your activity show up in the analytics dashboard, then you can disable the request header by simply unchecking the pink checkbox in the ModHeader plugin. You should be all set. To verify, you can go to your referral program and make a share. Then go to the Event Live View section in My.Extole and inspect your share event. In the Other Data section, you should see it say “extole_container: test” (vs. a value of production). If you are setting up automated continuous testing, there are other ways you can flag test events detailed here.

​

Viewing Test Data

To view test data on your Program or Campaign Dashboard, click on your initial in the bottom left and select “View Test Data”: To exit test data mode, click “Exit” on the yellow outlined box, or click on your initial again and select “View Production Data”.