Data models overview

A data model in FunnelStory is a typed definition that tells the platform how to read rows from a data connection, map columns to properties, and keep that data refreshed on a schedule. Models power Accounts View, timelines, health, workflows, and analytics.

Connections versus models

• Connection — credentials and access to a system (warehouse, CRM, support tool, etc.).
• Model — a named configuration bound to a connection: query (or managed source), column mappings, refresh interval, and optional joins.

Some integrations create and manage certain models for you (for example support tickets from Zendesk). Others require you to add a model and supply a query and mappings (typical for databases and many CRM-backed models).

Configure models in the product

1. Open Configuration → Data models.
2. Add model (or open an existing model), pick the model type, and choose a connection.
3. Provide a query or accept the managed source, then map each required column to a property name.
4. Validate, run a quick test if offered, and save.
5. Use Refresh model (or wait for the scheduled refresh) to load data.

Exact query syntax depends on the connection type (SQL, SOQL, HubSpot HS blocks, etc.). For the account model specifically, see the dedicated guide: Configuring the account model.

AI-suggested models

During onboarding, FunnelStory can suggest models and queries from your connection metadata (for example tables in a warehouse). Suggested models appear in the data model list; review mappings, run validation, then activate them like any other model.

Model refresh

Each model has a refresh interval (default six hours; your workspace may differ). Refreshes pull new and updated rows from the source, update entities, and drive timeline and metric updates. You can trigger a manual refresh from the Data models UI when you need data sooner.

Timestamp and type expectations for mapped columns follow the same rules as account properties where applicable; see Timestamp formatting in the account field reference.

Model types (reference)

Type	Purpose	Documentation
Account	Customer organizations; required foundation	Accounts model → full setup guide
User	People belonging to accounts	Users model
Activity	Generic in-product events	Product & activity models
Product activity	Product usage events	Product & activity models
Product feature activity	Events used for feature adoption	Product & activity models
Invite	Invitations (sender, invitee, acceptance)	Product & activity models
Non-product activity	Events outside core product (e.g. marketing page views)	Non-product activity
Support ticket	Support cases	Support tickets
Conversation	Chat and messaging threads	Conversations
Meeting	Calls and meetings (recordings, transcripts)	Meetings
Plan	Plan definitions for entitlements	Plans
Subscription	Entitlements and contracts per account	Subscriptions
Usage	Time-series usage of plan dimensions	Usage
Product	Product catalog for multi-product setups	Products
Account metric	Custom account-level time-series metrics	Account metrics
Note	Notes attached to accounts	Note
Strategy	Account-scoped strategy fields	Strategy
Task	Work tracked per accounts and assignees	Task

Suggested reading order

1. Accounts model (mandatory) and the configuring accounts guide
2. Users model if you need user-level analytics
3. Plans, Subscriptions, Usage, and Products for revenue and entitlement analytics
4. Activity models (product, non-product) for timelines and engagement
5. Integration-backed models (support, conversations, meetings) as you connect those systems