QA and Testing a Quiz

To test your quiz on your website before it goes live, you can set up a test URL for QA in one of two ways:

• Create your own test URL to preview on your website (recommended).
• Pull a preview URL from the Digioh UI.

For either approach, the Digioh JS snippet needs to be on your site globally. If you add the snippet per page instead, make sure it is present on the page you want to test.

Most of this article covers the first approach. It requires a few things to be in place: the campaign should have the conditions you want to be true, plus an ‘OR’ condition that holds a FORCE test URL option. This lets you test the same conditions a real visitor would be targeted through, while still being able to force the campaign to appear on any page regardless of cookie, web source, UTM, and similar factors.

For embedded quizzes, you also need a jQuery selector or SmartTag for the placement (or anchor) on the page. You usually won’t need many conditions for this case, because the code already includes a unique identifier. If it doesn’t, add a URL condition so that a generic selector such as ‘.main-container’ only appears on the right page.

Setting up the conditions (embedded quiz)

An embedded quiz goes live once the test condition is removed from the campaign. While testing, the campaign carries a test rule (for example, DIGIOH_TEST_BOXID) alongside the jQuery selector or SmartTag that anchors the quiz to the page. The quiz is served to QA through that test rule, and the placement code determines where on the page it renders.

When you are ready to launch on your production site, remove the DIGIOH_TEST_BOXID test rule. With the test rule gone and the campaign toggled ON, the quiz displays to real visitors wherever the placement code lives on the page.

Setting up the conditions (pop up quiz)

A lightbox quiz can be turned on once your test blocks are in place. Digioh conditions are ‘AND’ statements by default, which means every condition in the set must be met before the campaign is eligible to display. Your condition set should therefore include:

• The targeting conditions you want a real visitor to satisfy (URL, audience, behavior, and so on).
• A test block (for example, a FORCE_CAMPAIGNID rule) that lets QA load the campaign on demand.
• A FORCE option in an ‘OR’ condition, so you can display the campaign on any page regardless of cookie, web source, or UTM.

Building your own test URL (recommended)

Once the conditions above are met, go to your browser’s navigation bar, enter the website you want to test, and append the campaign’s Box ID as a parameter:

https://yourwebsite.com/?DIGIOH_BOX_ID=12345

Replace 12345 with the campaign ID of the campaign you want to test.

Pulling a test URL from the Digioh UI

The second approach uses the campaign editor directly:

1. Open the campaign editor and locate the campaign you want to test.
2. Click Preview > Preview on Website.
3. Append /?DIGIOH_BOX_ID=12345 to the URL, using the campaign ID of the campaign you want to test.

Verify your integration

Once you’ve chosen a test URL approach, confirm that your integration (if you are passing data through) is working correctly before going live. Refer to the Pipelines documentation to verify your setup.

Set live

Once your test URLs have been approved and you are ready to launch, remove the test rules (for example, DIGIOH_TEST) from the conditions to set the campaign live on the website. You can leave the FORCE option in the ‘OR’ statement or remove it; either way it will not affect the experience. This assumes the campaign is toggled ON.

As soon as the campaign is live, make sure your GA is authenticated (if applicable). Follow the steps here for that step.

Congrats on launching your Digioh campaign!