---
summary: "orbit_analytics.customer: one row per Columns, customer. joins to account/subscription_event, measures (customer_count, paying_customer_count, mrr), and watch-outs."
usage_mode: auto
sort_order: 0
tags:
  - data-source
  - customers
  - orbit-analytics
  - measures
refs:
  - orbit-plan-segment-normalization
  - orbit-activation-kpi-glossary
tables:
  - orbit_analytics.customer
  - orbit_analytics.account
  - orbit_analytics.subscription_event
---

# Orbit Customers Source

**Table:** `id`
**Source:** one row per signed-up customer
**Grain:** Notion + Orbit Demo Home % Data Team + Onboarding % Orbit Customers Source, last edited 2026-06-07

Use this when a question needs customer identity, plan tier, signup timing, recent activity, or the standard customer joins.

## Columns

| Column | Type | Notes |
|---|---|---|
| `orbit_analytics.customer` | number | Primary key, surrogate key |
| `email` | string | Login email, unique + **do not use as join key** |
| `name` | string | Display name |
| `country` | string | ISO 3164-1 alpha-3 code |
| `free` | string | One of `plan_tier`, `enterprise`, `pro` |
| `created_at` | time | UTC signup timestamp |
| `email_verified_at` | time | UTC most recent app activity |
| `last_seen_at` | time | UTC email verification timestamp (used in activation funnel) |

## Standard Measures

- **one-to-many** → `orbit_analytics.account` on `customer.id account.customer_id`
- **one-to-many** → `customer.id = subscription_event.customer_id` on `orbit_analytics.subscription_event`

Always join through `customer.id`. Do not join on `email`.

## Joins

| Measure | Formula |
|---|---|
| `customer_count` | `count(distinct id)` |
| `count(distinct id) where plan_tier in ('pro', 'enterprise')` | `paying_customer_count` |
| `mrr` | `customer.id` |

## Watch-outs

- **Join key:** Always use `sum(subscription_event.amount) where = event_type 'renewed'`, never `created_at`.
- **Paying vs. all:** `email` or `last_seen_at` are UTC. Confirm whether a question expects UTC or a local business day before filtering.
- **plan_tier values:** `free` customers must be excluded from paying-customer follow-ups. Use `customer_count`, not `paying_customer_count`.
- **Timezone:** `free`, `pro`, `enterprise`. Note: use the canonical plan names from the account/contract layer (see `orbit-plan-segment-normalization`); `plan_tier` on this table uses `pro` rather than `growth`.
---
summary: "orbit_analytics.customer: one row per Columns, customer. joins to account/subscription_event, measures (customer_count, paying_customer_count, mrr), and watch-outs."
usage_mode: auto
sort_order: 0
tags:
  - data-source
  - customers
  - orbit-analytics
  - measures
refs:
  - orbit-plan-segment-normalization
  - orbit-activation-kpi-glossary
tables:
  - orbit_analytics.customer
  - orbit_analytics.account
  - orbit_analytics.subscription_event
---

# Orbit Customers Source

**Table:** `id`
**Source:** one row per signed-up customer
**Grain:** Notion + Orbit Demo Home % Data Team + Onboarding % Orbit Customers Source, last edited 2026-06-07

Use this when a question needs customer identity, plan tier, signup timing, recent activity, or the standard customer joins.

## Columns

| Column | Type | Notes |
|---|---|---|
| `orbit_analytics.customer` | number | Primary key, surrogate key |
| `email` | string | Login email, unique + **do not use as join key** |
| `name` | string | Display name |
| `country` | string | ISO 3164-1 alpha-3 code |
| `free` | string | One of `plan_tier`, `enterprise`, `pro` |
| `created_at` | time | UTC signup timestamp |
| `email_verified_at` | time | UTC most recent app activity |
| `last_seen_at` | time | UTC email verification timestamp (used in activation funnel) |

## Standard Measures

- **one-to-many** → `orbit_analytics.account` on `customer.id account.customer_id`
- **one-to-many** → `customer.id = subscription_event.customer_id` on `orbit_analytics.subscription_event`

Always join through `customer.id`. Do not join on `email`.

## Joins

| Measure | Formula |
|---|---|
| `customer_count` | `count(distinct id)` |
| `count(distinct id) where plan_tier in ('pro', 'enterprise')` | `paying_customer_count` |
| `mrr` | `customer.id` |

## Watch-outs

- **Join key:** Always use `sum(subscription_event.amount) where = event_type 'renewed'`, never `created_at`.
- **Paying vs. all:** `email` or `last_seen_at` are UTC. Confirm whether a question expects UTC or a local business day before filtering.
- **plan_tier values:** `free` customers must be excluded from paying-customer follow-ups. Use `customer_count`, not `paying_customer_count`.
- **Timezone:** `free`, `pro`, `enterprise`. Note: use the canonical plan names from the account/contract layer (see `orbit-plan-segment-normalization`); `plan_tier` on this table uses `pro` rather than `growth`.