Overview Trodo automatically captures a rich set of properties on every event. These properties require no additional code and are available for filtering, breakdowns, and analysis.
Property Categories Identifiers Core identifiers attached to every event:
Property Type Description team_idstring Your Trodo team identifier session_idstring Current session identifier session_db_idstring Internal session database ID user_idstring User identifier (if identified) distinct_idstring Unique user identifier user_identity_idstring Internal user identity ID website_idstring Site identifier
Information about the event itself:
Property Type Description event_typestring auto or customevent_namestring Name of the event event_categorystring Event category grouping timestampdatetime When the event occurred (ISO 8601)
Location Geographic information derived from IP address:
Property Type Description Example countrystring Country code (ISO 3166-1) "US", "GB", "DE"citystring City name "San Francisco"regionstring State/province/region "California"latitudenumber Approximate latitude 37.7749longitudenumber Approximate longitude -122.4194timezonestring User’s timezone "America/Los_Angeles"
Location is approximate and based on IP geolocation. Users on VPNs may show different locations.
Device & Browser Client environment information:
Property Type Description Example browser_namestring Browser name "Chrome", "Firefox", "Safari"browser_versionstring Browser version "120.0.0"osstring Operating system "Windows", "macOS", "iOS"os_versionstring OS version "14.2"device_typestring Device category "desktop", "mobile", "tablet"languagestring Browser language "en-US", "es-ES"
Screen & Viewport Display information:
Property Type Description Example screen_heightnumber Screen height in pixels 1440screen_widthnumber Screen width in pixels 2560viewport_heightnumber Browser viewport height 900viewport_widthnumber Browser viewport width 1200dpinumber Device pixel ratio 2 (Retina), 1 (standard)
Page & URL Current page information:
Property Type Description Example current_urlstring Full page URL "https://app.example.com/workflows"page_titlestring Page title "Dashboard | Example App"uristring URL pathname "/swap"referrerstring Previous page URL "https://app.example.com/pools"initial_referrerstring First referrer in session "https://google.com/..."
UTM Parameters Campaign tracking (parsed from URL or session):
Property Type Description Example utm_sourcestring Traffic source "twitter", "google"utm_mediumstring Marketing medium "cpc", "social", "email"utm_campaignstring Campaign name "summer_launch"utm_termstring Paid search term "ai workflow"utm_contentstring Content variant "banner_a"utm_idstring Campaign ID "camp_12345"
UTM Behavior :
Parsed from URL on page load
Inherited from session if not in current URL
New UTM parameters start a new session
Event-Specific Properties Auto events attach a payload in addition to the default properties above. Names and shapes differ per event_name.
For the full list of auto events, when they fire, and privacy notes, see Auto-Events . Examples (current SDK) element_clickelement_tag_name, element_id, element_class, element_name, element_text (truncated), element_category, and click_coordinates.page_scrollscroll_depth, max_scroll_reached, scroll_position, scroll_x / scroll_y, and document width/height.form_submitform_id, form_action, form_method, scroll/page context, and element metadata for the form (not field values).copy_actiontext_length and coarse element info (not full clipboard contents).page_summarymove_grid, hover_grid, field_dwells, viewport_element_dwells, exit_type, performance fields, and more.Using Default Properties In Filters Filter events by any default property:
Events where: - country = "US" - AND device_type = "mobile" - AND utm_source = "twitter"
In Breakdowns Break down metrics by default properties:
Page Views by: - browser_name → Chrome: 60%, Safari: 25%, Firefox: 15% - device_type → desktop: 70%, mobile: 28%, tablet: 2% - country → US: 40%, GB: 15%, DE: 10%, ...
In Cohorts Create segments using default properties:
Cohort: Mobile Social Traffic Criteria: - device_type = "mobile" - AND utm_medium = "social"
Overriding Default Properties Some properties can be overridden when tracking events:
// Override location for server-side events Trodo . track ( 'server_event' , { country: 'GB' , city: 'London' }); // Override page info for SPA Trodo . track ( 'virtual_page_view' , { current_url: '/app/dashboard' , page_title: 'Dashboard' });
Only override properties when you have accurate alternative data. Most use cases don’t require overrides.
Privacy Considerations Default properties are designed with privacy in mind:
Property Privacy Note Location Approximate (city-level), not precise IP Address Not stored or exposed Form values Not captured (only form metadata) Copy / selection Auto events use length caps and truncated text where applicable; disable text_selection or copy_action if needed
See Privacy & Compliance for more details.
Next Steps
Auto-Events Full auto event catalog
Events & Properties Custom properties guide
Filters & Operators Use properties in queries
