Terminology

Essential terms and concepts used throughout Appizer documentation.

Core Concepts

Event

An action or occurrence tracked in your application.

Example: user_signup, purchase_completed, page_view

appizer.track({
  event: 'purchase_completed',
  userId: 'user_123'
})

User

An individual identified by a unique ID who performs events.

Aliases: Identity, Profile

appizer.identify({
  userId: 'user_123',
  traits: { email: 'user@example.com' }
})

Properties

Key-value pairs that add context to events.

Also called: Event properties, Attributes

appizer.track({
  event: 'purchase',
  properties: {
    amount: 99.99,
    currency: 'USD'
  }
})

Traits

Persistent attributes stored on a user profile.

Also called: User properties, User attributes

appizer.identify({
  userId: 'user_123',
  traits: {
    plan: 'pro',
    industry: 'technology'
  }
})

Version

A release of your application tracked with a version number and timestamp.

Purpose: Analyze how new releases impact user engagement and performance

// Versions are managed via the dashboard or MCP
// Example version record:
{
  version: '2.1.0',
  released_at: '2026-01-15T10:00:00Z',
  release_notes: 'New onboarding flow'
}

Identification

User ID

A unique identifier for an authenticated user.

Format: String (e.g., user_123, auth0|abc123)

Anonymous ID

A unique identifier for a user before they authenticate.

Format: UUID or similar unique string

const anonymousId = generateUUID()
appizer.track({
  event: 'page_view',
  anonymousId: anonymousId
})

Alias

A link between two user identifiers (e.g., anonymous → authenticated).

appizer.alias({
  userId: 'user_123',
  previousId: anonymousId
})

Analytics

Segment

A dynamic group of users matching specific criteria.

Example: "Enterprise users who signed up in the last 30 days"

{
  filters: [
    { property: 'plan', operator: 'equals', value: 'enterprise' },
    { property: 'signupDate', operator: 'after', value: '2024-01-01' }
  ]
}

Funnel

A series of events representing a user journey.

Example: Signup funnel

1. landing_page_viewed
2. signup_form_started
3. signup_completed

Cohort

A group of users who share a common characteristic or experience.

Example: "Users who signed up in January 2024"

Metric

A quantitative measurement derived from events.

Examples:

• Total revenue
• Average session duration
• Conversion rate

Push Notifications

Campaign

A targeted push notification sent to a segment of users.

appizer.push.send({
  segment: 'active_users',
  notification: {
    title: 'New Feature',
    body: 'Check out our latest update'
  }
})

Device Token

A unique identifier for a device to receive push notifications.

Platform-specific:

• iOS: APNS token
• Android: FCM token
• Web: Push subscription

Delivery Status

The state of a push notification:

• Sent: Dispatched to push service
• Delivered: Received by device
• Opened: User clicked notification
• Failed: Delivery failed

API Terms

Endpoint

A specific URL path for an API operation.

Example: POST /v1/events/track

Authentication

The process of verifying API requests using an API key.

headers: {
  'Authorization': 'Bearer sk_live_abc123...'
}

Rate Limit

The maximum number of API requests allowed in a time window.

Default: 1000 requests per minute

Idempotency Key

A unique identifier to prevent duplicate processing of the same request.

appizer.track({
  event: 'purchase',
  idempotencyKey: 'order_456'
})

Data Processing

Batch

Multiple events sent in a single API request.

appizer.batchTrack([
  { event: 'event_1', userId: 'user_1' },
  { event: 'event_2', userId: 'user_2' }
])

Enrichment

Adding additional data to events during processing.

Examples:

• Geo-location from IP address
• Device information from user agent
• Timestamp normalization

Validation

Checking that events meet required format and constraints.

Validates:

• Required fields present
• Data types correct
• Values within allowed ranges

Time-Related

Timestamp

The date and time when an event occurred.

Format: ISO 8601 (e.g., 2024-01-15T10:30:00Z)

appizer.track({
  event: 'purchase',
  timestamp: '2024-01-15T10:30:00Z'
})

Time Window

A specific date range for analytics queries.

{
  startDate: '2024-01-01',
  endDate: '2024-01-31'
}

Real-time

Events processed and available for querying within seconds.

Typical latency: < 2 seconds

Integration

SDK

Software Development Kit - a library for integrating Appizer.

Available for: JavaScript, Python, React, React Native, iOS, Android

API Key

A secret token used to authenticate API requests.

Types:

• Secret Key (sk_): Server-side use only
• Public Key (pk_): Client-side use allowed

Webhook

An HTTP callback triggered by specific events.

Use cases:

• Real-time notifications
• Data synchronization
• Custom integrations

MCP Server

Model Context Protocol server for AI assistant integration.

Enables: AI assistants to query analytics and send notifications

Performance

Throughput

The number of events processed per second.

Appizer capacity: Millions of events per second

Latency

The time between event submission and availability for querying.

Typical: < 2 seconds

Uptime

The percentage of time the service is operational.

SLA: 99.9% uptime

Security

Encryption

Data protection using cryptographic algorithms.

At rest: AES-256
In transit: TLS 1.3

Authentication

Verifying the identity of API requests.

Method: Bearer token authentication

Authorization

Determining what actions an authenticated request can perform.

Model: Role-based access control (RBAC)

Compliance

GDPR

General Data Protection Regulation - EU privacy law.

Appizer features:

• Data export
• Data deletion
• Consent management

SOC 2

Security and compliance certification.

Type: Type II certified

Data Residency

The geographic location where data is stored.

Options: US, EU, Asia-Pacific

Next Steps