Databuddy

Notra loads the Databuddy script on every live page and allows Databuddy’s script and ingestion hosts in the CSP. Every option you set in blog.json is passed to the tracker, so you can turn on web vitals, error tracking and custom events, skip or mask paths and tune batching without writing a custom script.

Copy your Client ID

In Databuddy, open your website and copy the data-client-id value from its tracking code. It’s a public ID, so no API key is needed.

Add it to Notra

Open Studio → Sites, select your site, open Integrations and click Add Databuddy. Paste the ID into Client ID and switch on the tracking you want. To configure it in your repository instead, add it to blog.json:

blog.json

{
  "$schema": "https://usenotra.com/schemas/blog.json",
  "name": "Acme",
  "integrations": {
    "databuddy": {
      "clientId": "3ed1fce1-5a56-4cbc-a917-66864f6d18e3",
      "trackWebVitals": true,
      "trackErrors": true,
      "trackOutgoingLinks": true,
      "skipPatterns": ["/drafts/**"]
    }
  }
}

Publish and verify

After you publish the change and the production deployment finishes, visit your live site and check the realtime view in Databuddy.

Options

The dashboard covers the Client ID and the four most common tracking switches. Every other option is set in blog.json, and editing the integration in the dashboard keeps those options as they are.

Setting	Dashboard field	Description
`clientId`	Client ID	Public Client ID from your website’s tracking code
`trackWebVitals`	Web vitals	Sends Core Web Vitals for every page. Defaults to `false`
`trackErrors`	Errors	Sends uncaught JavaScript errors. Defaults to `false`
`trackOutgoingLinks`	Outgoing links	Sends an event when visitors click links to other domains. Defaults to `false`
`trackInteractions`	Interactions	Sends clicks, rage clicks and dead clicks. Defaults to `false`
`trackAttributes`		Sends a custom event when visitors click an element with a `data-track` attribute, using its other `data-*` attributes as properties. Defaults to `false`
`trackHashChanges`		Counts URL hash changes as page views. Defaults to `false`
`samplingRate`		Share of events to send, from `0` to `1`. Defaults to `1`
`skipPatterns`		Up to 50 path globs that are never tracked, like `["/drafts/**"]`
`maskPatterns`		Up to 50 path globs whose matching segments are masked before sending, like `["/authors/*"]`
`anonymizeVisitorIds`		Anonymizes visitor IDs before storage. Set it to `"auto"` to let Databuddy decide. Defaults to `true`
`ignoreBotDetection`		Also tracks visits that look like bots. Defaults to `false`
`usePixel`		Sends events with a 1x1 image request instead of `fetch`. Defaults to `false`
`enableBatching`		Sends events in batches. Defaults to `true`
`batchSize`		Events per batch, from `1` to `50`. Defaults to `10`
`batchTimeout`		Milliseconds before a partial batch is sent. Defaults to `5000`
`enableRetries`		Retries failed requests. Defaults to `true`
`maxRetries`		Retries per failed request, up to `10`. Defaults to `3`
`initialRetryDelay`		Milliseconds before the first retry. Defaults to `500`
`scriptUrl`		Full HTTPS tracker script URL for a self-hosted or proxied script. Defaults to `https://cdn.databuddy.cc/databuddy.js`
`apiUrl`		HTTPS ingestion URL for a self-hosted or proxied endpoint. Defaults to `https://basket.databuddy.cc`

Notra adds the origins of scriptUrl and apiUrl to the Content-Security-Policy automatically.

Custom events

With trackAttributes on, you can track clicks in your own components or MDX without any JavaScript. Databuddy sends the data-track value as the event name and the element’s other data-* attributes as properties:

<a href="/pricing" data-track="pricing_clicked" data-placement="changelog-footer">See pricing</a>

Get started

Domains

Write content

Components

Customize

Integrations

Publish

Reference

Options

Custom events

​Options

​Custom events

Options

Custom events