Skip to content
TagSentry
Start free

Getting started

Create an account, copy one line, paste it at the top of your site's header. Here is what happens next, and what has to be true before a banner shows.

The short answer

Sign up, tell us your website, copy one line of code and paste it first in your site's <head>, above Google Tag Manager. Once your domain is proven and our first scan finishes, the banner goes live on its own.

1. Create an account

Go to app.tagsentry.ai and sign up with an email or Google. No card is needed. The first question is the only one: What's your website?

2. Choose where your data is stored

Pick EU or US. This decides where your consent records and events are stored, and it is fixed for the life of the site. It does not decide which law applies to a visitor: every visitor gets the rules for where they are, whichever you pick.

3. Copy the line and paste it first

You get one short script tag. Paste it at the very top of your site's header code box, which is often called "Header scripts" or "Custom code". It must be the first script on the page, above your Google Tag Manager code.

<script src="https://cdn.tagsentry.ai/api/client/v1/site/EU/rs_yourkey.js" onerror="…"></script>
  • Leave your Google Tag Manager code as it is. TagSentry doesn't load, delay or change it, unless you turn on Basic mode, which holds Tag Manager until consent.
  • Never add async or defer. The line has to run before your tags, and document order is what makes that happen.
  • Keep the onerror part. If our CDN can't be reached, it sets Google's six consent signals to denied before your tags run.

Can't paste it yourself? Use Send this to a developer. It drafts an email with the code and one sentence of instructions.

4. Nothing else to verify, usually

Pasting the line normally proves you own the domain: we read your homepage and find the code that was made for this site. If we can't see it (for example, it's added by JavaScript after the page loads), the install screen offers a meta tag or a DNS record instead.

What has to be true before a banner shows

  1. The line is on your live site, in the HTML the server sends.
  2. Your domain is proven.
  3. Our first scan of your site has finished.

Until all three are true, visitors see no banner. That's expected. Your banner editor shows the real banner straight away, so you can change it while you wait.

Visiting from the US? In most states the law doesn't ask first, so you'll see a small "Your Privacy Choices" link, not a pop-up. Use the preview in your dashboard to see the banner as a visitor in any country or US state. A site on localhost, a preview behind a login or a password-protected staging site can't be proven or scanned.

The inline option

Under For developers there is an inline snippet: the same thing, written straight into your page, so no network request happens before your tags. Use it if you want that, or if your Content Security Policy blocks inline event handlers like onerror. Either way, the API's install response lists the exact origins and hashes your policy needs. Don't remove onerror from the one-line tag: it's what keeps Google's signals denied if our CDN can't be reached.

Next