■ DATA MODEL AND DEVELOPERS
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.
Every attribute shows where it is used
LIVE PREVIEW · SAMPLE DATA
■ CAPABILITIES
Send an event and its properties appear. Lock the schema when you are ready.
■ CONTROL
AT A GLANCE — 01 / 06
■ HOW IT WORKS
Call the SDK or the API with an event.
Attributes and properties appear as they arrive.
Stop unexpected fields from creeping in.
■ OVERVIEW
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.
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.
Use the web, Android and iOS SDKs, the REST API, a file import or FlowConnect. All routes write to the same model.
■ COMPARE
| COMPARE | Attributes | Events |
|---|---|---|
| Describes | Who a person is | What a person did |
| Changes | Updated in place | Added as a new record each time |
| Example | City, plan, language | Order placed, app opened |
| Used for | Filters and personalisation | Triggers, funnels and goals |
Note: Use attributes for state and events for actions.
■ USE CASES
Packs add the attributes and events for your sector.
Send from the SDK with a key per app.
Record transactions for lifetime value.
Post events from your backend with a signed request.
See each field and where it is used.
Remove fields nobody needs.
■ FOXAI
Paste a sample payload and review the suggested attributes and events.
Suggests events that would improve churn or purchase scores.
Flags the same thing sent under two different names.
Generates a plain-language description for each field.
■ BEST PRACTICES
"order_placed" reads better than "order".
Pick user ID, email or phone before you send data.
Simple properties are easier to filter on.
Rotate a key without affecting other apps.
Unused fields add noise.
Review the schema with the whole team.
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
Three building blocks describe what Flowfox knows about a person and what they do.
Read more CONTACTS AND DATAAdd the SDK to your site, identify a person and send an event that shows up on their profile.
Read more CONTACTS AND DATABring people into Flowfox from a file, mapping each column and choosing what happens to people who already exist.
Read more GETTING STARTEDSet up a Flowfox workspace in a few minutes, choose your region and bring in the people who will use it.
Read more■ WORKS WELL WITH
Start a free workspace, connect a data source and send your first journey, or book a guided demo.
Start a free workspace, connect a data source and send your first journey. Or book a guided demo.