Skip to main content

​
Overview

Core vocabulary used in Trodo’s documentation. Where helpful, terms are mapped to Mixpanel or Amplitude concepts.

​
distinct_id

The primary identifier for a user in Trodo. Every user—anonymous or identified—has one.
  • Anonymous users: Trodo generates a distinct_id on first visit, stored in a first-party cookie (cq_distinct_id).
  • Identified users: Calling Trodo.identify('your_id') replaces the anonymous ID with the value you supply (typically your database user ID or UUID).
After identification, distinct_id is developer-controlled—Trodo does not reassign it without a merge.
ToolEquivalent
Mixpaneldistinct_id
Amplitudeuser_id / device_id

​
user_identity_id

An internal UUID for each profile record. Unlike distinct_id, it is system-generated and stable across merges. You may see it in exports; you do not set it from the SDK.

​
identify()

Links an anonymous session to a known user. Call once per session when the user logs in or registers. 
Trodo.identify('user_db_id_12345');
Typical merge behavior
  • New ID: the current anonymous profile becomes (or joins) the identified profile.
  • Same ID, same device: sessions continue on one profile.
  • Same ID, new device: CQ Intelligence can merge when enough signals align.
ToolEquivalent
Mixpanelmixpanel.identify()
Amplitudeamplitude.setUserId()

​
CQ Intelligence merge engine

Trodo’s system for unifying profiles that belong to the same person across sessions and devices. Merge may be triggered when
  • The same identify() ID appears in another session or on another device.
  • Other identity rules configured for your team apply.
When a merge occurs, event history and profile properties are combined into one profile. Day-to-day instrumentation is still: identify(), track(), and people updates.

​
auto-events

Behavioral events the SDK sends without Trodo.track(), using the same pipeline as custom events. They stay off until auto-events="true" on the script tag or equivalent in code. Examples include page_view, element_click, page_scroll, form_submit, js_error, and page_performance. See Auto-Events.
ToolEquivalent
MixpanelAutocapture (where offered)
AmplitudeAutocapture / Session Replay

​
groups

Group membership ties the current user to entities labeled with a group key (e.g. company) and group ID (e.g. acme-inc). Group profiles store properties for that pair.
APIRole
Trodo.set_group(key, id) / add_group / remove_groupMembership
Trodo.get_group(key, id).set({...})Group-level properties
See Groups.
ToolEquivalent
MixpanelGroup Analytics
AmplitudeGroups

​
people methods

Trodo.people.* updates persistent user properties (not one-off event payloads).
MethodPurpose
people.set()Set properties (overwrites)
people.set_once()Set only if missing
people.increment()Add to a number
people.append()Append to a list (allows duplicates)
people.union()Add to a list (no duplicates)
people.remove()Remove from a list
people.unset()Delete a property
people.deleteUser()Delete the profile
people.trackCharge()Record revenue on the profile
See People.

​
trackCharge()

Records revenue or payment against a profile (subscriptions, seats, usage bundles). 
Trodo.people.trackCharge(49.99, {
  plan: 'pro',
  currency: 'USD'
});
ToolEquivalent
Mixpanelmixpanel.people.track_charge()
AmplitudeRevenue via Revenue object

​
session

A period of continuous activity. A new session typically starts when:
  • The user visits for the first time, or
  • Inactivity exceeds the session timeout (commonly 30 minutes), or
  • Campaign parameters change (where configured)
Tracked via the cq_session_id cookie where applicable.
ToolEquivalent
Mixpanel / AmplitudeSession

​
Next steps

User profiles

How profiles are structured

Implementation guide

End-to-end patterns