← Documentation

Integrations

You can run Intrily alongside your existing stack. Here are the main integration patterns.

Tag managers and CDPs

  • Google Tag Manager (GTM) — Add a Custom HTML tag with the Intrily script (your URL + data-website-id). Fire it on All Pages or on the triggers you need (e.g. after consent).
  • Segment — Use a Segment→Intrily destination or send server-side to our ingest API with your write key. Same event shape as the tracker.
  • Other tag managers — If it can load a script by URL and pass data attributes, you’re good. Use your Intrily script URL and the same tracker configuration options (data-website-id, data-host-url, etc.).

Web: CMS and frameworks

Drop the script into the global <head> or your layout/analytics partial. For SPAs (React, Next.js, Vue), load it on the client—e.g. in useEffect, componentDidMount, or your app’s bootstrap—so data-website-id and the domain are correct.

REST API and custom code

Intrily’s REST API lets you send events and pull reports from your own code. A few common setups:

  • JavaScript / Node — fetch or any HTTP client to POST to the ingest endpoint. Match the payload format and auth from the API docs.
  • PHP (e.g. Laravel) — Fire server-side events for form submits, webhooks, or server-rendered actions. Good when the browser doesn’t run your tracker.
  • Python — requests or httpx to send events from scripts, workers, or data pipelines.

Base URL, auth, and rate limits are in the dashboard and API docs.

Mobile and non-browser

For native apps (e.g. Flutter, React Native) or backend-only use, POST to the ingest API with the usual fields: website, url, title, and any custom data. If you’re using Distinct IDs, send a stable id so we can tie sessions together.