How to exclude Staging or Development environment events from your reporting data

It is often necessary to run third party integrations in development environments for testing. If you are testing Corvidae in any environment other than your live environment (your website or apps) we advise that you exclude that traffic from your reporting data.

Exclude data via environment specific appId

This is the method we advise because it offers the best traceability.

In the Corvidae Setup Tag an appId is specified. To denote staging events simply append the name of the environment to the your appId.

For example, if the appId in your setup script is mywebsiteuk then append -staging using an environment variable in your staging environment.

appId declaration on your live site:
var appId = 'mywebsiteuk';

appId declaration on your staging site:
var appId = 'mywebsiteuk-staging';

appId declaration on your development site:
var appId = 'mywebsiteuk-dev';

This method allows each non-live environment to be delimited separately, and because these events are still sent to our servers - if ever you need to critique your non-live data - our team can export or analyse it for you.

Alternative methods

Exclude the Corvidae tags

You are free to simply omit the tracking tags from your development environments. This will prevent data from being sent to our servers and we will not be able to offer assistance should you need it. This will also prevent testing Corvidae tracking before changes are released to your live environments.

Test=true

If you include the query string key value pair test=true in any of your Corvidae requests they will be rejected by our ingress server. This allows you to test the https mechanism is functional, but will restrict any testing of the data beyond the pixel call / response.