Searchable list
Column picker, saved filters and a quick-view side panel. Search by any attribute.
A searchable list of every person with their attributes, and a full profile for each one.
Bring people in by SDK, API, file or FlowConnect.
Events, messages, transactions, journeys and consent sit together, so anyone on the team can see what happened.
Column picker, saved filters and a quick-view side panel. Search by any attribute.
Add to list, tag, add to segment, export or delete, run as background jobs with progress.
A timeline of events and the message history with opens and clicks per channel.
Consent is stored per channel with the time it was given, and checked before every send.
Edit attributes inline, merge duplicates, and anonymise or delete a person in one action.
See the journeys a person is in, and the notes your team left.
A Flowfox profile brings together everything known about one person. It is the single place to look when someone writes to support or a campaign misfires.
Bring people in by SDK, API, file or FlowConnect.
Add contacts with the import wizard from a CSV file, through the web, Android or iOS SDK, through the REST API, or by syncing a tool with FlowConnect.
Identities link into one profile per person.
Identifiers such as email, phone number and your own user ID are linked, so a person who visits on mobile and then buys on web is one profile, not two.
Find people, message them or export the list.
Attributes such as city and plan, events such as signup or purchase, transactions, channel consent and the full activity timeline all sit on the profile.
Pick a contact and browse the profile. Then try sending on a channel to see consent enforced.
The import wizard maps columns, merges duplicates and returns a list of rejected rows with the reason for each. Merge rules combine duplicate profiles.
Choose what happens to people who already exist, then run the import.
| Name | City | Status |
|---|
The same person came in from two sources. Pick the value that wins when fields conflict.
The same history, whoever opens the profile.
Map columns, choose update behaviour and see rejected rows.
Record opt-in per channel and send only to those who agreed.
Merge profiles that came from different sources.
Use lifetime value to decide who gets a premium journey.
Anonymise or delete a person in one action.
Say it in plain words and review the filters it sets.
Flowfox suggests duplicate merges. You decide, and the history is kept.
Use churn and purchase scores on the profile.
A short, readable recap of a person's recent activity.
Map each column and choose what happens to people who already exist.
Help CenterThree building blocks describe what Flowfox knows about a person.
Help CenterIdentify a person and send an event that shows up on their profile.
Help CenterSet up Flowfox and add the people who will use it.
Help CenterVisits on mobile and purchases on web should be one customer.
Guide · 6 minMap columns, choose update behaviour, read the rejected rows.
Guide · 5 minWhat to store and when it is checked.
Guide · 5 minPick winners and keep the timeline.
Playbook · 6 minWhich one fits which job.
Opinion · 4 minOne timeline for everyone who opens a profile.
Playbook · 5 minPeople who share an identifier are merged into one profile. You choose which value wins when fields conflict.
Yes. Map a consent column per channel and the import records it with the time of the import.
Open the contact. The timeline lists every event, message and change in order.
Contact limits depend on your plan. See the pricing page.
Yes. Linked identities keep them on one profile.
Yes. Delete or anonymise a profile from its page.
Start a free workspace, connect a data source and send your first journey. Or book a guided demo.