Event Properties
Properties are key-value pairs that describe what happened during an event. Basic Event:Property Types
Standard Properties
DATALYR recognizes common property names and handles them specially: Revenue Properties:revenueoramount: Monetary value (number)currency: Three-letter currency code (USD, EUR, GBP)order_id: Unique order identifier (string)transaction_id: Transaction reference (string)
product_id: Product SKU or IDproduct_name: Product titleproduct_category: Category or collectionproduct_price: Unit pricequantity: Number of itemsvariant_id: Product variant identifier
page_url: Full page URLpage_path: URL path onlypage_title: Document titlereferrer: Previous page URL
email: User email addressname: User full namephone: Phone numberuser_id: Internal user identifier
Custom Properties
Add any properties relevant to your business: E-commerce:Property Value Types
Properties support multiple value types: String:Automatic Metadata
DATALYR automatically captures metadata with every event:Page Context
Automatically Captured:Device Information
Screen Dimensions:Session Context
Session Data:Attribution Data
Marketing Attribution:Performance Metrics
Page Load Performance (pageview events):Fingerprinting Data
Device Fingerprint:Property Naming Conventions
Follow these conventions for consistent tracking:Use snake_case
Be Descriptive
Use Consistent Names
Avoid Reserved Keys
Don’t use these reserved property names:user_iduserIdanonymous_idanonymousIdvisitor_idsession_idevent_idtimestampworkspace_id
Property Limits
DATALYR enforces limits for performance and storage: Per Event:- Max 50 properties per event
- Property names: 255 characters max
- Property values: 10KB max
- Total event size: 50KB max
- Keep property counts reasonable (10-20 is ideal)
- Avoid deeply nested objects (max 3 levels)
- Don’t include large text blocks in properties
- Use arrays sparingly (max 100 items)
Sensitive Data Handling
Never send sensitive data:Property Validation
DATALYR validates properties before sending: Valid Properties:Enrichment Best Practices
Add Context to Every Event:Server-Side Properties
When tracking server-side, include additional context:Automatic Property Enrichment
DATALYR automatically enriches certain events: Pageview Events:- Performance metrics (load time, FCP, LCP)
- Referrer data (domain, path, source)
- Browser capabilities (user agent parsing)
- Field interaction count
- Time to submit
- Form intent detection
- Product data (from page context)
- Cart state (from DOM)
- Platform detection (Shopify, WooCommerce, etc.)
- Scroll depth (for scroll events)
- Time on page
- Click position
Property Schema Evolution
Properties can evolve over time as your tracking needs change: Initial Implementation:Next Steps
Events Overview
Learn about event tracking
Identity Calls
Link users across devices
Attribution Models
How conversions are attributed
Custom Events
Track custom events with SDK