Skip to main content

Strategy model

The strategy model stores account-scoped strategy data: one row (or aggregated row) per account with a flexible set of properties. Typical sources include CRM strategy or account plan objects synced from a warehouse or API-backed connection.

Prerequisites​

How strategy rows work​

  • Rows are keyed by account_id.
  • Every column you map becomes a property on the strategy entity for that account (including fields beyond the defaults below). Use consistent property names for reporting and workflows.
  • Invalid rows may be skipped on refresh; ensure account_id values exist in your accounts model.

Field reference​

Required key​

PropertyTypeDescription
account_idstringAccount this strategy record describes.

Default guidance​

The configuration UI may pre-populate account_id as the minimum mapping. Add mappings for every strategic field your source provides (for example goals, priorities, renewal strategy, competitor notes)—each becomes a named property in FunnelStory.

There is no fixed global list: treat this model like a wide, account-level profile driven by your query.

Configure​

  1. Add model → Strategy.
  2. Point at the connection and query that returns one logical strategy row per account (or that FunnelStory aggregates per account per refresh rules).
  3. Map account_id and map additional columns to descriptive property names.
  4. Validate, save, refresh.
  5. Confirm strategy fields on account records in the product UI where exposed.