Exports
Take a segment's audience out of Jimo as a CSV or JSON file, choosing exactly which attributes to include.
Exporting turns a segment's live audience into a file you can hand to another tool: a CRM, a spreadsheet, a data warehouse, an email platform.
Where an import brings data in, an export takes it out. Same data, opposite direction.
Where to start
Open a segment from the Segments list, then click Export in the top-right corner of its detail page.
You are exporting the segment's current audience: the users who match its rules right now. Because a segment is a live definition, the file is a snapshot of this moment, not a subscription. Export again next week and you may get a different set of people.
Pick a format
Export opens a short menu.
CSV
Spreadsheets, CRMs, email tools, anything that eats a table
JSON
Code, data pipelines, anything that expects structured objects
The choice only changes the shape of the file. The data, and the attribute picker that comes next, are identical.
Choose which attributes to include
Both formats open the same panel: a live preview of the file on the left, and an attribute picker on the right. What you select on the right is exactly what lands in the file.
The preview is a table: one row per user, one column per selected attribute. The header tells you the shape, for example 3 of 3 rows, 6 columns.
The CTA at the bottom reads Export to .csv.
The preview is a tree: an array of user objects, each key a selected attribute. Native keys use their raw names (created_at, last_activity_at), which is what your code will receive.
The CTA at the bottom reads Export to .json.
The attribute picker
Two sections, and the split is the same one you see everywhere in Data Management.
Native Attributes. ID, Name, Email, Tags, Created at, Last activity. Selected by default: these are the columns you almost always want.
Custom Attributes. Everything your project has ever received: plan, firstname, isPaying, and every other key you have pushed. None are selected by default; add the ones you need.
A search field at the top of the picker helps when the custom list is long.
Export only what the destination needs. A file with every attribute is harder to read and, depending on what those attributes hold, more sensitive to pass around. Start from the native columns and add the specific custom fields the receiving tool expects.
An empty attribute exports as empty. If a custom attribute has a value for only part of the segment, its column is blank for everyone else. That is not an export bug, it is coverage: the attribute was never set for those users. The export mirrors exactly what Jimo holds.
Related pages
Imports: the same operation, in reverse
Segment details: where the Export button lives
Attributes: what the native and custom columns mean
Data Management: how data gets in and out of Jimo
Last updated