Testing Your Implementation

Prev Next

Your Triton Digital Solutions Specialist will provide you with a test URL for testing your implementation. It will return a campaign that is specially configured for testing and contains more than you would find in a typical "real world" campaign. Specifically, it contains four impression confirmation URLs with trackers and click URLs on the banners. It includes iFrame and HTML samples, but none for static resource.

Be aware that the test server does not provide true responses to the parameters listed below:

  • banners (it always returns one banner)
  • all of the asset types parameters (they are all ignored)
  • all of the targeting parameters (they are all ignored)

You should still include these parameters in the test URL; just be aware that the response will be as indicated above.

The test environment does not allow caching of media files (mp3, jpg, etc.). This is to streamline the test process and any troubleshooting that needs to be done. Once you transition to the production environment, caching is enabled in the server headers by default, and we recommend that all implementations use proper HTTP caching.

The audio file included in the test URL response is maximized for testing purposes; you might want to turn down your speakers or headphones before checking it.

Example Test URL

Below is an example of the test URL. Replace "xxxx" with the precise character string that was provided to you by your Triton Digital Solutions Specialist, and replace the blurred parts with the required parameters as described in this document.

This is just an example!