Skip to main content

Overview

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

Event Metadata

Information about the event itself:

Location

Geographic information derived from IP address:
Location is approximate and based on IP geolocation. Users on VPNs may show different locations.

Device & Browser

Client environment information:

Screen & Viewport

Display information:

Page & URL

Current page information:

UTM Parameters

Campaign tracking (parsed from URL or session): UTM Behavior:
  • Parsed from URL on page load
  • Inherited from session if not in current URL
  • New UTM parameters start a new session

Web3 Properties

Blockchain-related properties:

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_click — includes viewport and page coordinates, document dimensions, and element metadata such as element_tag_name, element_id, element_class, element_name, element_text (truncated), element_category, and click_coordinates. page_scroll — includes scroll_depth, max_scroll_reached, scroll_position, scroll_x / scroll_y, and document width/height. form_submit — includes form_id, form_action, form_method, scroll/page context, and element metadata for the form (not field values). copy_action — includes text_length and coarse element info (not full clipboard contents). page_summary — large aggregate object: e.g. move_grid, hover_grid, field_dwells, viewport_element_dwells, exit_type, performance fields, and more. Wallet connection is not an auto-event in the SDK; use Cryptique.walletAddress() and custom Cryptique.track() calls if you want explicit wallet lifecycle events in the event stream.

Using Default Properties

In Filters

Filter events by any default property:

In Breakdowns

Break down metrics by default properties:

In Cohorts

Create segments using default properties:

Overriding Default Properties

Some properties can be overridden when tracking events:
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: 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