Install Button on your website

Sign in to the Button console, add your website, and complete domain verification. The collection script identifies the site from the page where it runs; there is no site key to add to this script.

For a traffic audit, begin with Analytics only and choose the standard or invisible script below. Advertising feedback is configured separately; redirect mode changes what happens when the Button cookie is missing. Follow your site’s consent requirements when deciding when third-party collection may run.

• Open the Button console
• Privacy policy

Choose one script variant and add it once in the head of each page you want to measure or protect. Use one installation method: a direct embed, Tag Manager, or an integration package. Do not install all three variants together.

The standard script displays the twirling space button:

Use invisible=true when you want Button installed without displaying the twirling space button.

For WAF-style redirection, use mode=redirect: visitors without the Button cookie are sent to the site's main page. This is the Site Protect installation mode.

Choose this mode when you want the missing-cookie redirect behavior. For a traffic audit without that redirect, use the standard or invisible script instead.

A complete Site Protect plugin is available for WordPress as a downloadable package. Contact us for the plugin and setup instructions.

• Request the WordPress Site Protect plugin
• Frameworks and plugins

A direct head embed is preferred where possible: it starts earlier and does not depend on Tag Manager loading. Installing Button through GTM does not automatically transfer control of your Google Ads or Meta tags.

1. Create a Custom HTML tag containing your chosen script variant.
2. Use the Initialization – All Pages trigger, subject to your consent setup.
3. Preview and publish the container, then check collection on the live site.

1. Open a page on the verified domain and inspect the browser’s Network panel.
2. Confirm the Button script loads once. Check the console for blocked requests or content security policy errors.
3. Confirm fresh measured events appear for the correct website in Button. Loading a script alone is not proof that collection succeeded.

Keep in mind: Consent settings, extensions, caching and content security policy can affect collection. Validate an actual visit before interpreting an empty report.

Review traffic quality alongside sources, campaigns and visitor journeys before changing feedback. A visitor who does not buy is not, by that fact, a bot.

• Understand traffic evidence
• Frameworks and ecommerce plugins