How to use
On a page running Snowplow right click and select Inspect, select the Snowplow Debugger (sometimes it is hidden depending on the width of your browser), refresh to capture the hits on that page.
If you are looking for TLDR see the 1 minute video below:
The Feature Bar
The feature bar includes the main extension functionality.
When you first open the extension on a live website with Snowplow, you'll have to hit refresh; the extension only captures hits if it is open.
Hit Overview & Details
Use the main hit overview pane to observe events as they are recorded. Click on a hit to inspect it. Hits with invalid or not found schemas are highlighted in red.
Example of an event without a valid schema available for validation.
Example of an invalid event, with details about why it is invalid.
Collector Override allows you to override the default collector and redirect the events to a new collector.
To use, click the collector override icon, add the collector to intercept hits from (original collector) and the new collector (override collector), select Enabled, and click "Apply Changes."
When developing schemas, you can add your Iglu schemas or a custom Iglu server. The extension will use all available Iglu servers to validate hits.
Adding a public accessible Iglu repository
Click the Iglu repositories icon, Add Iglu Repository, and add the URL without a trailing slash. Schemas should be accessible from that URL in URL/schemas.
You can also add an Iglu server URL https://your-iglu-server/api (don't forget to add /api to your Iglu server URL.
Using schemas from your local drive
Did you know you can also test your schemas locally? Type
chrome://extensions/ in your Chrome URL, click Detail under the Snowplow Debugger, and enable
Allow access to file URLs.
Click the Iglu repositories icon In your Iglu repository add the path to your local Iglu repository.
file:/// into your Chrome URL bar to find your exact path