RReplayly

Install Replayly with Google Tag Manager

If your site already loads tags through Google Tag Manager, you can add Replayly as a Custom HTML tag. This is a documented install path for the official tracker, not a claim that Replayly is listed in the GTM community gallery.

Last updated .

How to add the Custom HTML tag

  1. Create a Replayly project and copy the official snippet from the dashboard, including your host and project key.
  2. In Google Tag Manager, create a new Custom HTML tag and paste that snippet. Do not invent a different collector URL.
  3. Choose a trigger that matches when you are allowed to record. If you use a consent banner, fire the tag only after the relevant consent event, or keep consent mode in the snippet and call window.replayly('consent') from your banner callback.
  4. Publish the GTM container, visit a page that should fire the tag, and use Verify installation in Replayly to confirm ingest.

What this integration is — and is not

Google Tag Manager only delivers the same /t.js tracker you would paste into a template. Privacy defaults still come from Replayly: input masking is on, and Do Not Track is respected unless you explicitly pass dnt=0 on a test setup.

We do not currently offer a first-party GTM template in the official gallery. A Custom HTML tag is the accurate, supported method. If a gallery template ships later, this page will be updated rather than pretending one exists today.

Consent, previews, and debugging

Use GTM Preview to confirm the tag fires on the pages you intend, then confirm a session appears in Replayly. A tag that fires in Preview but never reaches /api/ingest usually means the host, project key, or content security policy is wrong.

If your container also loads other analytics or replay tools, be explicit about which tool is the source of truth and about consent. Loading two recorders without a policy is a product and privacy problem, not something Replayly can fix from the snippet alone.

Limits

GTM must actually publish to the environment you are testing. A leftover workspace, a blocked custom HTML tag, or a consent trigger that never fires will look like a broken Replayly install. Server-side GTM is not a separate documented integration today; if you inject the snippet from a server container, you are still responsible for serving the same official /t.js URL.

Read the install guide, review product facts, or create a workspace.