Skip to main content
Consent, on this page, refers to your cookie banner’s approval before a tool may run in a user’s browser. HelpAlive has no consent mode of its own. Once the tag loads, it notes activity in the page, sends it only after identify() runs, and drops it if identify() never runs, as Identify users describes. To make it wait for your banner, you hold back the HelpAlive tag until the user accepts. This page is for developers whose cookie banner must approve tools before they run.
  • HelpAlive has no consent mode. Your banner decides when the tag loads.
  • Without the tag, nothing of HelpAlive runs and the agent doesn’t appear.
  • Calls to identify() and reset() made before the tag loads wait in the page, then run once it has loaded.
  • The old data-consent attribute, setConsent() and the mode and consent options of init() do nothing now. You can delete them.
  • HelpAlive doesn’t read Do Not Track or Global Privacy Control signals.

Prerequisites

  • A cookie banner or consent tool that tells your code when a user accepts or declines.
1

Hold back the tag

Leave the HelpAlive tag out of your page’s HTML. Add it from your code only once the user accepts, with the same attributes as in Install the script.
2

Keep identify() and reset() as they are

Keep the four queue lines and your identify() and reset() calls. Calls made before the tag loads wait in the page and run once it has loaded.

Example: add the tag when the user accepts

Call this from your banner’s “accepted” callback. It adds the same tag as Install the script, once, from your code:
Replace YOUR_PROJECT_KEY with your key from Settings → Setup & API Key. If your Content Security Policy uses a nonce, set it on the tag too, as Content Security Policy describes.
Without the tag, nothing of HelpAlive runs, so the agent doesn’t appear for a user who declines. To keep the agent away from some users, leave them out of Who gets it on Controls. To stop recording one user for good, use Settings → Privacy Management.
When your banner reports that a user who accepted has changed their mind, run this on the page:
Then stop adding the tag on later page loads, as in Make HelpAlive wait for consent. If the user accepts again, add the tag again.
  • Before the user accepts: the tag isn’t on the page, so HelpAlive sends nothing and shows nothing. Your four queue lines hold any identify() or reset() calls in the page.
  • After the user accepts: the tag loads, runs the waiting calls, and the chat button appears for users in Who gets it.
  • If the user declines: the tag never loads. This means that the agent stays away for that user, in that browser, until your banner reports a change.
Earlier versions of the script had a consent mode. It has been removed:
  • A data-consent="required" attribute on the tag is ignored.
  • setConsent() still exists, so old pages don’t break, but it does nothing.
  • The mode and consent options of init() are gone.
You can delete all three from your code. HelpAlive doesn’t read Do Not Track or Global Privacy Control signals.

Check it works

  1. Open your app in a private window with the browser’s developer tools open on Network. Filter on helpalive.
  2. Sign in and decline in your banner. No HelpAlive request appears.
  3. Accept in your banner. The script loads, and the chat button appears for users in Who gets it.

Next

Data we collect

What HelpAlive records, and what it doesn’t.

Privacy Management

Stop tracking or delete a user’s data.

JavaScript reference

Every call your code can make.
Last modified on October 12, 2026