Events

Events track user actions in your product. Use them to trigger messages, measure engagement, and build behavior-based targeting rules.

What are Events?

Events are actions users take in your app:

• Signed up

• Created a project

• Invited a team member

• Exported data

• Completed onboarding

• Used a specific feature

Each event is recorded with a timestamp and optional properties.

Why Use Events?

Behavior-Based Targeting

Show messages based on what users have (or haven't) done:

• "Show onboarding checklist to users who haven't created a project"

• "Show upgrade prompt after user exports 5+ times"

• "Celebrate users who invite their first team member"

Automatic Checklist Completion

Complete checklist items when users take actions:

• Item "Create your first project" completes when project_created event fires

• Item "Invite a team member" completes on team_member_invited event

User Insights

Understand user behavior:

• See which events each contact has triggered

• Track feature adoption

• Identify power users

Event Structure

Each event has:

Field	Description
Key	Unique identifier (e.g., project_created)
Name	Display name (e.g., "Project Created")
Contact	The user who triggered it
Timestamp	When it occurred
Properties	Optional metadata (JSON)

Event Keys

Event keys are unique identifiers. Use consistent naming:

Good examples:

• project_created

• team_member_invited

• file_exported

• feature_x_used

• onboarding_completed

Naming conventions:

• Use snake_case

• Start with a noun or verb

• Be specific but concise

• Keep consistent across your app

Event Properties

Add context to events with properties:

Cueflow.track('file_exported', {
  format: 'csv',
  rowCount: 1500,
  exportType: 'full'
});

Properties are stored as JSON and can be viewed in the dashboard.

How Events are Used

In Targeting Rules

Target users based on event history:

Has done an event:

Event → project_created → Has Done

Hasn't done an event:

Event → onboarding_completed → Has Not Done

Event count:

Event → file_exported → Count Greater Than → 5

Recency:

Event → last_login → Last Done Within → 7 days

In Checklist Completion

Auto-complete checklist items:

1. Create a checklist item

2. Set completion type to "Automatic"

3. Add rule: Event → event_key → Has Done

When the user triggers that event, the item auto-completes.

Event vs. Contact Property

Use events for actions, properties for states:

Use Events For	Use Properties For
Created a project	Number of projects
Upgraded plan	Current plan
Logged in	Last login date
Completed onboarding	Has completed onboarding

Tip: You can update properties when events occur to track both.

Best Practices

Naming

• Use consistent naming conventions

• Document your event schema

• Avoid generic names like "click" or "action"

Granularity

• Track meaningful actions, not every click

• Balance detail with noise

• Focus on events useful for targeting

Properties

• Include relevant context

• Don't include sensitive data

• Keep property names consistent

Planning

• Define events before implementing

• Create events in the dashboard for visibility

• Review and clean up unused events

Example Event Schema

SaaS Product

Event Key	Name	When to Track
signup_completed	Signup Completed	User completes registration
project_created	Project Created	User creates a new project
team_member_invited	Team Member Invited	User invites someone
file_uploaded	File Uploaded	User uploads a file
export_completed	Export Completed	User exports data
integration_connected	Integration Connected	User connects integration
feature_x_used	Feature X Used	User uses feature X

E-commerce

Event Key	Name	When to Track
product_viewed	Product Viewed	User views a product
added_to_cart	Added to Cart	User adds item to cart
checkout_started	Checkout Started	User begins checkout
purchase_completed	Purchase Completed	User completes order
review_submitted	Review Submitted	User submits a review

Next Steps

• Tracking Events - How to send events

• Event-Based Targeting - Use events in rules