Skip to main content
Vendor reference · Customer data platform

Segment (Analytics.js)

Twilio Segment's browser library. It collects events once and forwards them to many analytics, advertising and email tools.

Segment (Analytics.js) at a glance

Company
Twilio Segment
Category
Customer data platform
Tag script
https://cdn.segment.com/analytics.js/v1/<write-key>/analytics.min.js
Sends data to
api.segment.io cdn.segment.com
JavaScript object
analytics
Cookies
1 attributed to Segment (Analytics.js) in the TagPipes Vendor Registry

What Segment (Analytics.js) is

Analytics.js is Twilio Segment's browser library for collecting events once and forwarding them to many destination tools. It exposes identify, track, page, group and alias calls on an analytics object.

It keeps an anonymous visitor ID in the ajs_anonymous_id cookie.

What marketers use it for

Teams use it as a single collection layer that feeds analytics, advertising and email tools without separate integrations for each. It also builds customer profiles in Segment.

How to recognize Segment (Analytics.js) on a site

  1. Open the site in Chrome, open DevTools (F12, or Cmd+Option+I on a Mac) and go to the Network tab.
  2. Reload the page and type segment into the filter box. The library loads from cdn.segment.com and tracking calls go to api.segment.io.
  3. In the Console tab, type typeof analytics.track and press Enter. If it returns "function", Analytics.js has loaded. The name analytics is common, so confirm with the cdn.segment.com request.
  4. In Application, then Cookies, look for ajs_anonymous_id. Some cookies only appear after a consent choice or a specific action.

Cookies associated with Segment (Analytics.js)

Attributed to Segment (Analytics.js) by the TagPipes Vendor Registry: ajs_anonymous_id.

What TagPipes observed

0.43%

of sites scanned had Segment (Analytics.js) detected

TagPipes scanned 41,162 public websites between August 11, 2026 and September 13, 2026, loading up to three pages per site in a real browser as a first-time visitor, and matched what loaded against the TagPipes Vendor Registry. That is how TagPipes recognizes Segment (Analytics.js): by the hosts its tag loads from and the cookies attributed to it.

Observed TagPipes scan data, not a figure published by Twilio Segment. Websites of TagPipes customers are excluded and no individual site is named. Snapshot dated September 13, 2026.

Sources

What it is, what it is used for, and its scripts, hosts and JavaScript objects were checked against the vendor documentation above on . The detection rate is TagPipes scan data from September 13, 2026, not a value published by the vendor. Browse all vendors.

Know when a tag stops firing

TagPipes Auditor checks with real browsers that your marketing pixels fire with the right parameters, and alerts you when tracking breaks. Pulse checks how marketing tags behave against your consent banner.

See Auditor See Pulse

TagPipes monitors, configures and reports. It does not determine legal compliance and does not provide legal advice. Output is informational and reflects observed state at the time of observation. Rawsoft's expertise is technology, not law; please confirm any regulatory interpretation with your own counsel.