Documentation

SDK reference

ADT globals, attribution helpers, and Stripe metadata helpers.

The browser SDK loads as adt.js and exposes a global ADT object. Modules attach under namespaces (Session, Attribution, Pixels, …).

Loader

<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>

CDN base: https://cdn.getintently.io/. The id query param is your account API key.

ADT.Attribution

Loaded from the attribution collector module. Used for server-side destination routing and Stripe linking — it does not inject third-party ad pixels.

ADT.Attribution.getContext()

Returns click IDs / cookies for the current page, with sticky paid IDs (90-day localStorage):

fbp, fbc (builds fbc from fbclid when needed)
gclid, ttclid, msclkid, liFatId, pinUnauth, scClickId

ADT.Attribution.getStripeCheckoutMetadata()

Synchronous. Returns { intently_session_id } when a session exists.

ADT.Attribution.getStripeCheckoutMetadataAsync()

Async. Same as above, plus intently_user_hash when user tracking / hash mode allows.

ADT.Attribution.buildEventId(sessionId, eventName)

Helper for platform deduplication ids.

Sessions

ADT.Session owns session identity used on track calls. Prefer documented product settings for hash mode rather than hand-rolling hashes.

Destinations alias

ADT.Destinations is an alias of ADT.Pixels in the pixels module — configure destinations in the product UI; do not assume undocumented private APIs.

Debugging

Confirm window.ADT after load
Settings → Debug (when available on your plan)
Network tab: requests to Intently track / config endpoints on your API host