Contact Properties

Contact properties are the attributes you store about your users. Use them to personalize messages and create targeted segments.

Standard Properties

These properties are built-in and recognized by Cueflow:

Identification

Property	Type	Description
id	String	Required. Unique identifier for the user
email	String	Email address
name	String	Full name or display name
phone	String	Phone number
avatarUrl	String	URL to profile image

Role & Plan

Property	Type	Description
role	String	User's role (e.g., "admin", "member", "viewer")
plan	String	Subscription plan (e.g., "free", "pro", "enterprise")

Timestamps

Property	Type	Description
signedUpAt	Date	When the user created their account
lastSeenAt	Date	Auto-updated on each page view

Setting Properties

Via Embed Script

Pass properties when initializing:

Cueflow.init({
  id: 'user-123',
  email: '[email protected]',
  name: 'Jane Smith',
  role: 'admin',
  plan: 'pro',
  signedUpAt: '2024-01-15T10:30:00Z'
});

Update properties when they change:

Cueflow.update({
  plan: 'enterprise',
  role: 'owner'
});

Via Server API

curl -X POST https://app.cueflow.so/api/v1/contacts \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "[email protected]",
    "name": "Jane Smith",
    "plan": "pro"
  }'

Using Properties for Targeting

Properties enable powerful targeting rules:

Plan-Based Targeting

Show upgrade prompts to free users:

Contact Property → Plan → Equals → "free"

Role-Based Targeting

Show admin features to admins only:

Contact Property → Role → Equals → "admin"

Time-Based Targeting

Welcome new signups:

Contact Property → Signed Up At → Is Within → 1 day

Target veteran users:

Contact Property → Signed Up At → Is Before → 90 days ago

Engagement Targeting

Re-engage inactive users:

Contact Property → Last Seen At → Is Before → 7 days ago

Property Types

Text Properties

String values for names, emails, plans, etc.

Operators available:

• Equals / Not Equals

• Contains / Not Contains

• Starts With / Ends With

• Is Set / Is Not Set

Date Properties

Timestamp values like signedUpAt and lastSeenAt.

Operators available:

• Is Within (last X days)

• Is Before (more than X days ago)

• Is Set / Is Not Set

Best Practices

Consistency

• Use consistent values (e.g., always "pro" not sometimes "Pro")

• Define a schema for your team

• Document expected values

Completeness

• Always send id (required)

• Include email for better profiles

• Send signedUpAt for time-based targeting

Updates

• Update properties when they change

• Use Cueflow.update() for real-time updates

• Keep plan/role in sync with your database

Naming

• Use lowercase with underscores for custom properties

• Be descriptive but concise

• Avoid abbreviations

Example: Complete Profile

Cueflow.init({
  // Identification
  id: 'usr_a1b2c3d4',
  email: '[email protected]',
  name: 'Jane Smith',
  avatarUrl: 'https://example.com/avatars/jane.jpg',

  // Role & Plan
  role: 'admin',
  plan: 'enterprise',

  // Timestamps
  signedUpAt: '2024-01-15T10:30:00Z',

  // Custom properties (see Custom Attributes)
  company: 'Acme Inc',
  teamSize: 50,
  industry: 'technology'
});

Next Steps

• Custom Attributes - Create your own properties

• Targeting Rules - Use properties in targeting