block-quote On this pagechevron-down
GitBook Assistant Ask chevron-down Data Attributes Custom attributes let you store any data about your contacts beyond the standard properties. Use them for targeting, segmentation, and personalization.
What are Custom Attributes?
Custom attributes are properties you define for your workspace. Examples:
teamSize - Number of team members
industry - Business sector
isTrialing - Whether on a trial
referralSource - How they found you
Creating Custom Attributes
Method 1: Automatic Creation
When you send a new property via the embed script, Cueflow automatically creates the attribute:
Copy Cueflow . init ( {
id : ' user-123 ' ,
email : ' [email protected] ' ,
// Custom attributes - auto-created if they don't exist
company : ' Acme Inc ' ,
teamSize : 50 ,
isEnterprise : true
} ) ; Method 2: Manual Creation
Create attributes in the dashboard for better control:
Configure:
Name - Display name (e.g., "Team Size")
Key - API key (e.g., "team_size")
Type - Text, Number, or Boolean
Attribute Types
For string values:
Targeting operators:
For numeric values:
Targeting operators:
For true/false values:
Targeting operators:
Managing Attributes
View Attributes
Go to Settings > Attributes arrow-up-right to see all custom attributes:
Edit Attributes
Click an attribute to edit:
circle-exclamation
You cannot change the key or type after creation. Create a new attribute if needed.
Delete Attributes
triangle-exclamation
Deleting an attribute removes all stored values for all contacts. This cannot be undone.
Using Custom Attributes
In Targeting Rules
Target users by custom attributes:
Enterprise companies:
Trial users:
Specific industry:
Combining with Standard Properties
Mix custom attributes with standard properties:
Naming Conventions
Use snake_case for keys: team_size, is_trialing
Use clear display names: "Team Size", "Is Trialing"
Be consistent across your codebase
Choose the right type from the start
Use Number for quantities (enables comparison operators)
Use Boolean for yes/no values
Use Text for categories and free-form
Define attributes before implementation
Document what each attribute means
Avoid creating duplicate attributes
Only create attributes you'll use
Keep attribute count reasonable
Sending Attributes
Include in Cueflow.init() or Cueflow.update():
Server-Side API
Last updated 3 months ago