Custom Properties

Custom properties let you add context to your events. By attaching key-value pairs, you can break down event data in your dashboard and understand not just what happened, but why and how.

Adding Properties

Pass a Map<String, String> as the second argument to any tracking call:

Adopture.track('purchase', {
  'product_id': 'pro_monthly',
  'price': '9.99',
  'currency': 'USD',
});

Properties work with all event types:

// Track event with properties
Adopture.track('signup_completed', {'method': 'google'});

// Screen event with properties
Adopture.screen('product_detail', {'product_id': '456'});

Limits

• Maximum 50 properties per event
• Property values can be up to 500 characters long
• Both keys and values must be strings

Best Practices

Use Consistent Names

Use the same property names across different events when they refer to the same concept. For example, always use product_id rather than mixing product_id, productId, and item_id. Consistency makes it easier to analyze your data across event types.

Keep Values Clean

Since property values are strings, format them consistently. For boolean values, use 'true' and 'false'. For numbers, use a consistent decimal format.

Viewing Properties in the Dashboard

Properties are visible in the Event Property Breakdown view in your dashboard. Select any event type to see a breakdown of its properties, including the distribution of values for each key.

Super Properties

If you have properties that should be attached to every event automatically (for example, a subscription tier or A/B test group), use Super Properties instead of passing them manually each time. See Super Properties for details.