Intently.io
Open app

Documentation

Install the snippet

Add Intently to your site, verify the origin, and confirm events are flowing.

Intently starts with one first-party script. Everything else — attribution, destinations, Stripe revenue — depends on this firing on a verified origin.

What you need

  • An Intently account with an API key (Settings → API key)
  • Access to your site’s <head> (or a tag manager that can inject a script)
  • The domain you will track, added and verified under Settings → Domains

Snippet

Paste this in your site’s <head>, replacing YOUR_API_KEY with your key:

<script>
  (function(w,d,s,l,i){
    w[l]=w[l]||[];
    w[l].push({'adt.start':new Date().getTime()});
    var f=d.getElementsByTagName(s)[0],
        j=d.createElement(s);
    j.async=true;
    j.src='https://cdn.getintently.io/adt.js?id='+i;
    f.parentNode.insertBefore(j,f);
  })(window,document,'script','dataLayer','YOUR_API_KEY');
</script>

The loader pulls adt.js from the Intently CDN and initializes the ADT namespace. Your key is the id query parameter.

You can also copy the exact snippet with your key filled in from Settings in the product.

Verify the origin

Tracking only records for origins you have verified.

  1. Open Settings → Domains
  2. Add the hostname visitors use (e.g. www.example.com)
  3. Complete verification
  4. Keep the site enabled

If domain validation fails, the SDK will not treat the page as a trusted origin. Events may not land, and attribution touchpoints will not accumulate.

Confirm it works

  1. Load a page on the verified domain with the snippet installed
  2. Open Events in Intently — you should see page and session activity within a minute
  3. Open Attribution → Readiness (or Settings → Attribution) — “Tracking installed” should move toward complete once events and touchpoints appear

In the browser console (on your site), window.ADT should exist after load. If it is undefined, the script did not run (blocked, wrong domain, or snippet not in the document).

Environments

Use the same API key across staging and production only if you intend to mix traffic in one account. Prefer a separate account (or carefully filtered sites) for staging so attribution reports stay clean.

Next