Exporting Data
What This Page Covers
Section titled “What This Page Covers”How to export data from FSRevs — available exports, filtering options, column selection, export format, and permissions.
Choose the Right Export
Section titled “Choose the Right Export”| You need… | Export from… | Before exporting |
|---|---|---|
| Ratings, feedback, review attempts, or request outcomes | Review Flow Activity | Select the intended Flow, location, dates, and completion state. |
| Answers to one questionnaire | Custom Form Activity | Keep exactly one Form selected to get separate answer columns. |
| Contact details or a marketing contact list | Customers | Apply Marketing Eligibility for the intended channel and select its Marketable columns. |
Exports include records available under your current access. Viewing an individual request does not necessarily give you permission to export a wider dataset.
How Exporting Works
Section titled “How Exporting Works”- Open a Review Flow or Custom Form’s Activity page, use a dashboard View all … activity link, or open Customers
- Apply filters to narrow your data to exactly what you need
- Click the Export button in the table header
- Select which columns to include (defaults are pre-selected for you)
- The export is queued and processed in the background
- You’ll receive a notification when your export is ready to download
Export Limits
Section titled “Export Limits”Customer and Form Response exports can include up to 10,000 rows per export. Apply filters to split a larger result set into smaller batches. Review Activity does not use that same explicit 10,000-row limit, but filtering first still produces faster, more focused files. Export files are retained for 30 days before being automatically cleaned up.
Flow Activity Export
Section titled “Flow Activity Export”Filters
Section titled “Filters”Use these filters to narrow which Flow Activity records are included in your export. All filters are optional. Filters tied to one Review Flow, such as Review Site, appear only when that Flow provides the needed context.
Primary Filters
| Filter | Description |
|---|---|
| Location | Filter by one or more locations |
| Review Flow | Filter by one or more review flows |
| Smart Link | Filter by the smart link used to access the flow |
| Customer | Filter by one or more customer records |
| Employee | Filter by the attributed employee |
| Has Employee | Any / Assigned / Not Assigned |
Engagement Filters
| Filter | Description |
|---|---|
| Sent By | Filter by the team member who sent the request |
| Followup | Filter by the followup destination shown (Smart Link, Simple Page, or link) |
| Review Site | Filter by the review destination used |
| Visibility | Any / Public Only / Private Only |
| Completion | Any / Completed / Not Completed |
| Continued to Review Site | Any / Continued / Did Not Continue |
| Request Page Visited | Any / Visited / Not Visited |
Performance Filters
| Filter | Description |
|---|---|
| Rating / Score | Filter by star rating equivalents or by Customer Recommendation Score category. |
| Has Rating | Any / With Rating / Without Rating |
| Has Feedback | Any / With Feedback / Without Feedback |
| Has Review Attempts | Any / With Attempts / Without Attempts |
Contact & Date Filters
| Filter | Description |
|---|---|
| Has Phone | Any / With Phone / Without Phone |
| Has Email | Any / With Email / Without Email |
| Created Date | Choose when the record was created |
| Completed Date | Choose when the record was completed |
| First Visited Date | Choose when the request page was first used |
| Review Site Handoff Date | Choose when the customer continued to a site |
| Deleted records | Include records currently in the trash |
Available Columns
Section titled “Available Columns”When exporting, you choose which columns to include. Columns marked with Default are pre-selected.
Core Review Data
| Column | Default | Description |
|---|---|---|
| Short Key | ✓ | Unique identifier for the record |
| Rating | ✓ | The customer’s rating value used for sorting, filtering, and public star display |
| Customer Recommendation Score | ✓ | The customer’s 0–10 score when the Customer Recommendation Score widget was used |
| Sentiment | ✓ | The sentiment type used by the flow |
| Feedback | ✓ | Written feedback the customer submitted |
| Review Sites Attempted | ✓ | JSON list of review platforms the customer clicked |
| Is Public | ✓ | Whether the record is publicly visible |
| Owner Reply | ✓ | Your reply to the customer’s feedback |
| Completed At | ✓ | When the customer completed the flow |
Customer Identity
| Column | Default | Description |
|---|---|---|
| Reviewer Name | ✓ | Name on the flow record |
| Public Display Name | ✓ | Name shown publicly (may be shortened) |
| Reviewer Email | ✓ | Email address |
| Reviewer Phone | ✓ | Phone number |
| Reviewer Tagline | ✓ | Tagline the customer provided |
| Customer ID | Link to the matched customer record | |
| Customer Name / Email / Phone | From the linked customer record |
Flow & Distribution
| Column | Default | Description |
|---|---|---|
| Flow Name | ✓ | Which review flow was used |
| Flow Link URL | ✓ | The smart link URL used to access the flow |
| Followup Type | ✓ | Type of followup shown (Smart Link, Simple Page, or My Link) |
| Followup Name | ✓ | Name of the followup destination |
Organizational
| Column | Default | Description |
|---|---|---|
| Location Identifier | ✓ | Location code |
| Employee Name | ✓ | Attributed employee |
| Sent By Name | ✓ | Team member who sent the request |
| Created By Name | ✓ | Team member who created the record |
Timestamps & Status
| Column | Default | Description |
|---|---|---|
| Created At | ✓ | When the record was created (UTC) |
| Email Request Status | Success or Failure | |
| SMS Request Status | Success or Failure | |
| Overall Request Status | Success or Failure |
Form Responses Export
Section titled “Form Responses Export”Form Response exports are limited to 10,000 rows per export.
Filters
Section titled “Filters”| Filter | Description |
|---|---|
| Custom Form | Filter by a specific form (required for per-field answer columns) |
| Location | Filter by one or more locations |
| Smart Link | Filter by the smart link used |
| Customer | Filter by customer records |
| Employee | Filter by attributed employee |
| Has Employee | Any / Assigned / Not Assigned |
| Sent By | Filter by team member who sent the request |
| Followup | Filter by followup destination |
| Completion | Any / Complete / Incomplete |
| Request Page Visited | Any / Visited / Not Visited |
| Has Phone | Any / With Phone / Without Phone |
| Has Email | Any / With Email / Without Email |
| Created Date | Choose when the response was created |
| Completed Date | Choose when the response was completed |
| First Visited Date | Choose when the request page was first used |
| Deleted records | Include responses currently in the trash |
Available Columns
Section titled “Available Columns”Submission Data
| Column | Default | Description |
|---|---|---|
| Short Key | ✓ | Unique identifier for the submission |
| Form Name | ✓ | Which form was submitted |
| Per-Field Answers | ✓ | One column per form field (single-form export only) |
| Answers JSON | All answers as JSON (enabled automatically for multi-form exports) | |
| Completed At | ✓ | When the form was completed |
Submitter Identity
| Column | Default | Description |
|---|---|---|
| Submitter Name | ✓ | Name on the form submission |
| Submitter Email | ✓ | Email address |
| Submitter Phone | ✓ | Phone number |
| Customer ID | Link to the matched customer record |
Location & Assignment
| Column | Default | Description |
|---|---|---|
| Location Identifier | ✓ | Location code |
| Employee Name | ✓ | Attributed employee |
| Sent By Name | ✓ | Team member who sent the request |
| Created By Name | ✓ | Team member who created the record |
Distribution & Tracking
| Column | Default | Description |
|---|---|---|
| Flow Link URL | ✓ | Smart link used to access the form |
| Followup Type | ✓ | Type of followup shown |
| Followup Name | ✓ | Name of the followup destination |
Timestamps & Status
| Column | Default | Description |
|---|---|---|
| Created At | ✓ | When the submission was created (UTC) |
| Email Request Status | Success or Failure | |
| SMS Request Status | Success or Failure |
Customer Export
Section titled “Customer Export”Customer exports include the filtered customer records you have access to, up to 10,000 rows. Apply directory filters before selecting Export; filters such as Marketing Eligibility carry into the export query.
Columns
| Column | Description |
|---|---|
| Customer ID | Unique identifier |
| Full Name | Customer’s full name |
| First Name | First name |
| Last Name | Last name |
| Primary Email | Primary email identity value |
| Primary Phone | Primary phone identity value in E.164 format |
| Latest Marketable Email | Currently eligible email with the newest permission grant |
| Latest Marketable Phone | Currently eligible phone with the newest permission grant |
| All Marketable Emails (comma-separated) | Every currently eligible email, newest permission first |
| All Marketable Phones (comma-separated) | Every currently eligible phone, newest permission first |
| Created At | When the customer record was created (UTC) |
“Marketable” means the contact is active, has permission newer than any applicable revocation boundary, and is not currently blocked by a global restriction or suppression. A primary value identifies the customer but may not be marketable; the latest marketable value may therefore be an alternate contact.
Marketing Eligibility selects customer rows; it does not make the Primary Email or Primary Phone column safe to use for marketing. Select Latest Marketable Email or Latest Marketable Phone for one eligible value per customer, or the All Marketable columns when you need every currently eligible value. Empty marketable cells mean there was no eligible contact for that channel when the export was generated.
An export is a snapshot. If you use it for a later campaign, regenerate the eligible contact list so later revocations and restrictions are reflected. Phone values in E.164 format include the country code, for example +18085550100; keep them as text when importing into another system.
Filters
| Filter | Description |
|---|---|
| Has Email | Any / With Email / Without Email |
| Has Phone | Any / With Phone / Without Phone |
| Activity | Active in the last 30 days / No Review or Form activity |
| Marketing Eligibility | Marketable email, phone, either, both, or neither |
| Attention | Missing contact details / Latest tracked delivery failed |
| Created Date Range | When the customer record was created |
Responsibilities and Scope
Section titled “Responsibilities and Scope”Export access follows your Data access and location responsibilities. Owners, Administrators, and Location managers include the necessary data capabilities for their authorized scope.
If you do not see Export, ask a System owner or Administrator to review your responsibilities and assigned locations. See Roles & Permissions for details.
- Use filters first — Apply filters before exporting to get exactly the data you need, rather than exporting everything and sorting it later.
- Check your notifications — Exports run in the background. When your export is ready, a notification will appear in the notification section at the top of the page; it will not be sent by email.
- Export retention — Download your exports promptly. Export files are retained temporarily and may be removed automatically.
- Single-form exports — For form responses, filtering to a single form gives you the most useful export with individual answer columns.
Troubleshooting
Section titled “Troubleshooting”| Problem | What to do |
|---|---|
| Export is unavailable | Ask a manager to review your Data access and location scope. |
| Too many rows | Split the result by non-overlapping date ranges, Form, or location; Customer and Form exports allow up to 10,000 rows. |
| The download has not appeared | Check the portal notification center and the completion or failure message; queued exports do not download immediately. |
| A previous download is unavailable | Generate a new export. Files are retained temporarily, normally for 30 days. |
| Results differ from a dashboard total | Match the resource, dates, location, and completion filters. A dashboard’s completed-response total is not the same as all request records. |
| Export dates differ from a screen | Check the timestamp column and timezone context. Created At is exported in UTC. |