Industry packs are ready for eight industries. Start from journeys built for yours.Browse packs

Platform / Data model

■ DATA MODEL AND DEVELOPERS

Define what Flowfox knows about people

Attributes, events and transactions you define, with SDK apps, webhooks and an integration list.

Included in every plan. Plans in rupees from ₹4,999 a month, delivery included.

Same customer profiles everywhere A person approves every send Works inside your rules

LIVE PREVIEW · SAMPLE DATA

EMAIL✦SMS✦WHATSAPP✦RCS✦PUSH✦IN-APP✦EMAIL✦SMS✦WHATSAPP✦RCS✦PUSH✦IN-APP✦EMAIL✦SMS✦WHATSAPP✦RCS✦PUSH✦IN-APP✦EMAIL✦SMS✦WHATSAPP✦RCS✦PUSH✦IN-APP✦

■ CAPABILITIES

The pieces of your data model

Send an event and its properties appear. Lock the schema when you are ready.

ON

Attributes

System and custom, including nested arrays.

  • System and custom attributes
  • Nested arrays supported
  • See where each is used
ATTRIBUTES · SAMPLE VIEW
Step 1System and custom attributesOn
Step 2Nested arrays supportedLive
Step 3See where each is usedReady

■ CONTROL

Built to be checked, not trusted blindly

AT A GLANCE — 01 / 06

Now viewing: Attributes, events and transactions you define. System and custom attributes. Nested arrays supported.

■ HOW IT WORKS

Three steps from start to result

11

Send data

Call the SDK or the API with an event.

22

Review the schema

Attributes and properties appear as they arrive.

33

Lock it

Stop unexpected fields from creeping in.

■ OVERVIEW

The Flowfox data model: attributes, events and transactions

Three building blocks

Attributes describe a person. Events record what a person did. Transactions record an order or a payment in your workspace currency. Together they are enough to describe a bank customer, a shopper, a learner or a patient without a custom data warehouse.

Schema without surprises

The schema is inferred from incoming data until you lock it. Locking prevents unexpected fields. Every attribute and event shows the segments, journeys and templates that use it.

Industry packs install the schema for your sector, so event names such as order_placed or loan_applied exist before the first send.

Getting data in

Use the web, Android and iOS SDKs, the REST API, a file import or FlowConnect. All routes write to the same model.

■ COMPARE

Attributes or Events?

COMPAREAttributesEvents
DescribesWho a person isWhat a person did
ChangesUpdated in placeAdded as a new record each time
ExampleCity, plan, languageOrder placed, app opened
Used forFilters and personalisationTriggers, funnels and goals

Note: Use attributes for state and events for actions.

■ USE CASES

Where teams use Data model

Industry schema on day one

Packs add the attributes and events for your sector.

Web and app events

Send from the SDK with a key per app.

Orders and payments

Record transactions for lifetime value.

Server-side events

Post events from your backend with a signed request.

Schema review

See each field and where it is used.

Clean-up before launch

Remove fields nobody needs.

■ FOXAI

AI features that help, with a person in charge

COPILOT

Map my fields

Paste a sample payload and review the suggested attributes and events.

PREDICTIVE

Data you are missing

Suggests events that would improve churn or purchase scores.

RISK

Inconsistent names

Flags the same thing sent under two different names.

ASSIST

Document the model

Generates a plain-language description for each field.

■ BEST PRACTICES

Get it right from the start

01

Name events as past-tense actions

"order_placed" reads better than "order".

02

Decide the identifier early

Pick user ID, email or phone before you send data.

03

Keep properties flat

Simple properties are easier to filter on.

04

Use one key per app

Rotate a key without affecting other apps.

05

Check the schema often

Unused fields add noise.

06

Lock the model before launch

Review the schema with the whole team.

■ QUESTIONS

Questions, answered plainly

Short answers about Data model.

Still curious? Talk to us →

Yes. Locking stops unexpected attributes and events from being added.

An order or payment with an amount in your currency. Lifetime value and order count come from transactions.

They add the events and attributes common in that industry. You can edit or extend them.

Yes. Attributes can be arrays and nested objects.

Yes. Custom attributes and events can be added at any time.

For SDK and API events, yes. Imports and FlowConnect need no code.

Limits depend on your plan. Confirm on the pricing page.

Every attribute and event shows the segments and journeys that use it.

■ RELATED READING

Guides from the help centre

■ WORKS WELL WITH

Connects to the rest of the platform

▲

See Data model with your own data

Start a free workspace, connect a data source and send your first journey, or book a guided demo.

See your own customers in Flowfox this week.

Start a free workspace, connect a data source and send your first journey. Or book a guided demo.