Seentics

Agency

Install & verify

Every website gets its own snippet. Put it on the site, then let the workspace confirm that events are arriving.

Get the snippet

  • When you add a website, its snippet appears straight away.
  • Later, choose Install next to the site on its client's page, or Install & embed in the site's menu on the Websites page.

The snippet is one script tag with the website's ID:

index.html
<script defer data-website-id="YOUR_WEBSITE_ID" src="https://seentics.com/trackers/seentics.min.js"></script>

Copy it from the workspace rather than typing it — the ID is filled in for you.

Install it

The install panel has short steps for each platform. The full guides are here:

PlatformWhat to doGuide
HTMLPaste the tag into the <head> of every page.Tracker script
Google Tag ManagerA Custom HTML tag with the snippet, fired on All Pages, then publish.Google Tag Manager
Next.jsInstall @seentics/next and render it in the root layout.Frameworks
WordPressInstall the Seentics plugin and paste the website ID.WordPress
ShopifyThe snippet in theme.liquid, plus the custom pixel for purchases.Shopify
npmThe React, Vue, Nuxt, Astro or Svelte package, with the website ID.Frameworks

Webflow, Wix, Squarespace, Framer and Ghost: see Website builders.

Verify it

Open the site in a browser so it sends a first event, then choose Verify installation in the install panel. It shows one of three states:

StateMeansWhat to do
Receiving eventsEvents arrived in the last 24 hours.Nothing — tracking works. The panel shows when the last event came and how many arrived in 24 hours.
No events yetThe site has never sent an event.Install the snippet, open the site in a browser, then verify again.
StoppedEvents used to arrive, but none in the last 24 hours.Check the snippet is still on the site — a theme change or a new site build often removes it.

In the API these are receiving, not_seen and stale. On the client's page each website shows Verified once it has ever sent an event, or Not installed.

If no events arrive

  • Open the site, then the browser console. A message starting [Seentics] says what is wrong.
  • The attribute is data-website-id, not data-site-id.
  • The site must be served from the address you entered for the website — data from another hostname is refused.
  • Ad blockers can stop the script. Test in a private window with extensions off, or serve the tracker from the client's own domain — see Your own domain.
  • An archived client's websites don't collect. Unarchive it first.

From your own code

GET /api/v1/agency/websites/:id/install returns the snippet, the platform steps and the tracking state, and POST …/verify checks again. See the API reference.