-
- | `userId` |
- optional |
- String |
- The database ID for the user. If you don't know who the user is yet, you can omit the `userId` and just record `traits`. You can read more about identities in the [identify reference](/docs/connections/spec/identify). |
-
-
- | `traits` |
- optional |
- Object |
- A dictionary of traits you know about the user, like their `email` or `name`. You can read more about traits in the [identify reference](/docs/connections/spec/identify/). |
-
-
- | `options` |
- optional |
- Object |
- A dictionary of options. For example, [enable or disable specific destinations](#managing-data-flow-with-the-integrations-object) for the call. _Note: If you do not pass a *traits* object, pass an empty object (as an '{}') before *options*_ |
-
-
- | `callback` |
- optional |
- Function |
- A function executed after a short timeout, giving the browser time to make outbound requests first. |
-
-
-
-
-By default, traits are cached in the browser's `localStorage` and are attached to each subsequent Identify call.
-
-For example, you might call Identify when someone signs up for a newsletter, but hasn't yet created an account on your site. The example below shows an Identify call (using hard-coded traits) that you might send in this case.
-```js
-analytics.identify({
- nickname: 'Amazing Grace',
- favoriteCompiler: 'A-0',
- industry: 'Computer Science'
-});
-```
-
-Then, when the user completes the sign up process, you might see the following:
-
-```js
-analytics.identify('12091906-01011992', {
- name: 'Grace Hopper',
- email: 'grace@usnavy.gov'
-});
-```
-
-The traits object for the second call also includes `nickname`, `favoriteCompiler`, and `industry`.
-
-You may omit both traits and options, and pass the callback as the second argument.
-
-```js
-analytics.identify('12091906-01011992', function(){
- // Do something after the identify request has been sent
- // Note: site-critical functionality should not depend on your analytics provider
-});
-```
-
-### Track
-
-The Track method lets you record actions your users perform. You can [see a track example in the Quickstart guide](/docs/connections/sources/catalog/libraries/website/javascript/quickstart/#step-4-track-actions) or find details on [the track method payload](/docs/connections/spec/track/).
-
-The Track method follows the format below:
-
-```js
-analytics.track(event, [properties], [options], [callback]);
-```
-
-The `track` call has the following fields:
-
-
-
- | `category` |
- optional |
- String |
- The category of the page. Useful for cases like ecommerce where many pages might live under a single category. _Note: if you pass only one string to `page` it is assumed to be `name`. You **must** include a `name` to send a `category`._ |
-
-
- | `name` |
- optional |
- String |
- The name of the page. |
-
-
- | `properties` |
- optional |
- Object |
- A dictionary of properties of the page. Note: `url`, `title`, `referrer` and `path` are collected automatically! Additionally this defaults to a `canonical url`, if available, and falls back to `document.location.href`. |
-
-
- | `options` |
- optional |
- Object |
- A dictionary of options. For example, [enable or disable specific destinations](#managing-data-flow-with-the-integrations-object) for the call. _Note: If you do not pass a `properties` object, pass an empty object (like '{}') before `options`_ |
-
-
- | `callback` |
- optional |
- Function |
- A function that is executed after a short timeout, giving the browser time to make outbound requests first. |
-
-
-
-
-#### Default Page Properties
-
-A few properties are automatically added to each `page` call.
-
-```js
-analytics.page('Pricing');
-```
-
-Segment adds the following information without any extra work from you:
-
-```js
-analytics.page('Pricing', {
- title: 'Segment Pricing',
- url: 'https://segment.com/pricing',
- path: '/pricing',
- referrer: 'https://segment.com/warehouses'
-});
-```
-
-You can override these values by explicitly setting them in your calls. For example:
-
-```js
-analytics.page('Pricing', {
- title: 'My Overridden Title',
- path: '/pricing/view'
-});
-```
-Translates to:
-
-```js
-analytics.page('Pricing', {
- title: 'My Overridden Title',
- url: 'https://segment.com/pricing',
- path: '/pricing/view',
- referrer: 'https://segment.com/warehouses'
-});
-```
-
-### Group
-
-The Group method associates an [identified user](/docs/connections/sources/catalog/libraries/website/javascript/#identify) with a company, organization, project, workspace, team, tribe, platoon, assemblage, cluster, troop, gang, party, society or any other collective noun you come up with for the same concept.
-
-This is useful for tools like [Intercom](/docs/connections/destinations/catalog/intercom/), [Preact](/docs/connections/destinations/catalog/preact/) and [Totango](/docs/connections/destinations/catalog/totango/), as it ties the user to a **group** of other users.
-
-
-The Group method follows the format below.
-
-```js
-analytics.group(groupId, [traits], [options], [callback]);
-```
-The Group call has the following fields:
-
-