Accounts
An account in FunnelStory is the customer organization you sell to, renew, and measure: the anchor for revenue, health, ownership, and every downstream model (users, subscriptions, product usage, support, meetings, and notes). You reach for the account lens whenever you need a single place to see how one customer is doing across systems and time.
How accounts show up in the product
Your workspace’s Accounts model defines the canonical list: each row needs a stable account_id, plus the properties you map from CRM, warehouse, or other connections. On each refresh, those rows sync into the Customer Intelligence Graph and power the Accounts view, account detail, predictions, needle movers, tasks, audiences, and more.
You do not need to memorize every property here. Configuring the account model is the operational guide for queries, mappings, verification, and troubleshooting.
Properties and “what you see”
Accounts carry a mix of standard fields (identity, contract timing, revenue signals, assignments) and custom properties your team maps for filtering and workflows. Well-populated name, domain, and created_at (where available) make search, timelines, and handoffs usable on day one.
Hierarchy-specific fields such as parent_account_id and is_container change how rollups and multi-product experiences behave; those concepts live in the hierarchy section below rather than as a long field list on this page.
Lifecycle in plain language
- Connect data sources and define the Accounts model query and mappings.
- Save and refresh so FunnelStory ingests current account rows.
- Use account screens and signals; as source systems change, the next refresh updates FunnelStory’s copy.
If counts or fields look wrong after a refresh, treat it as a model or source-data issue first and walk Verification & troubleshooting before changing product configuration elsewhere.
Hierarchy and container accounts
Many B2B businesses sell to enterprises with subsidiaries or track multiple products on one customer. FunnelStory represents that with optional parent–child links between account rows (via parent_account_id) and optional container rows (is_container) that roll up children for reporting without duplicating product-level scores.
How rollups, product-level funnels, and product-level predictions interact with Products is documented in the hierarchy guides—start with Account hierarchy overview and Setting up hierarchy.
Related
- Accounts model — mandatory model, field pointers, and links to configuration.
- Customer Intelligence Graph — how accounts sit in the broader graph.
- Predictions and Needle movers — account-scoped intelligence built on account data.
- Data models — how models relate to one another at a high level.
- Notes — capturing context on accounts.