Contentstack
Contentstack is headless, so the Ours Privacy Web SDK is installed in the front-end application that renders your Contentstack content.
Ours Privacy works with Contentstack. Because Contentstack is headless, the install happens in your front end rather than in the CMS.
Contentstack delivers content over an API and does not render your pages, so there is no head field to paste a snippet into. The Ours Privacy Web SDK goes into the application that fetches from Contentstack and renders your site.
Find Your Front End First
Identify what renders your Contentstack site, then follow the matching guide:
- Next.js: a common pairing with Contentstack.
- Vite and React Router: for single-page applications.
- Installing on a headless CMS: the general pattern, plus what to do if your framework has no guide yet.
If your site is deployed with Contentstack Launch, the snippet still lives in your application code. Launch builds and hosts that application, so the change ships with your next deployment.
Tracking Content Metadata
To report on attributes stored in Contentstack, such as content type or locale, pass them as event properties when the page renders:
ours('track', 'Article Viewed', {
content_type: 'blog_post',
locale: 'en-us',
});Next Steps
- Installing on a headless CMS: the general headless pattern.
- Tracking page views in single-page apps: for client-side navigation.
- Web SDK reference: full list of tracking methods and options.
If you need further assistance, contact us at support@oursprivacy.com.
How is this guide?

