Table of Contents


You are here:

Tutorial Video

Admin Screen

Admin Exports Screen

Your Reach data is only as good as your ability to put it to good use in your broader field plan, GOTV strategy, and election-day operation. That is why Reach provides you with a number of export options that will allow you to get your data where you need it to go. You can export the following report types from Reach.

Export Types


The “People” export is designed to help you get a big-picture view of all the people your campaign has reached and added. It includes one row per person you have reached. It will tell you all the basic info about the person (their name, address, Reach ID, external IDs), who was the last user to reach them, when they were added, when they were last reached, which auto-applied tag they have, which campaign tags they have, their contact info if you have it, and all their survey question responses. Survey questions will appear each in their own column, with the column header as the first 50 characters of your question’s name and then the question’s ID in brackets. These survey question columns will be sorted in the order you created them.

Sample People Export. Check out the raw CSV file.

The “Responses” Export type is designed for uploading responses into a VoteBuilder, EveryAction, NationBuilder, or any other third-party CRM and merging them with existing people records by a unique ID. The CSV file will contain one row per response gathered in Reach. The first column will be a unique ID of the person in Reach (based on whichever you have selected on the Campaign Details screen). Then you will always have columns for Person Reach ID, Canvass Date, Canvass Timestamp, User ID, User Name, and Response ID. Then, you’ll have an additional column for every survey question in your campaign. Survey questions will appear each in their own column, with the column header as the first 50 characters of your question’s name and then the question’s ID in brackets. These survey question columns will be sorted in the order you created them.

It is important to remember that in this type, if a Reach user gathers responses to four questions from the same voter and taps save, that will appear as four rows in this file.

Responses Export
Sample Responses Export. Check out the raw CSV file.
Response List

The “Response List” Export type has the same data as the “Responses” Export type, but with some key formatting differences. The “Responses” Export type is specifically designed for uploading responses into a 3rd party CRM, and therefore has a separate column for each Survey Question. The “Response List” Export has the Survey Questions in a list instead, so there is one column for “Question Name”, and one column for “Response Value”.

Like the “Response” Export type, if a Reach user gathers responses to four questions from the same voter and taps save, that will appear as four rows in this file type as well.

Sample Response List Export. Check out the raw CSV file.
Tags History

This export will give you one row per tag-to-person pair. So, if your users have assigned five tags to the same person, that will be represented as five different rows. This allows us to show you what date and time each tag was applied, and by which user. We also include the persons’ name and most recent contact info for good measure. If you need street addresses, we suggest the “People” export type.

Note: We only began tracking timestamps and users who applied tags on August 7 2019, so any tags applied before then will not include those data points, but will still appear in your export.

Sample Tag History Export
Sample Tag History Export. Check out the raw CSV file.

The “Relationships” export is designed to give you insight into how your volunteers are using the Network feature. You can see who your volunteers are adding to/removing from their Network, as well as when they’re making these changes. You’ll see the person’s name, the User that added them to their Network, the Relationship Status (whether it’s Active, or Archived for relationships a user has removed), when the relationship was created, as well as when the relationship was modified.

There is a separate row for each individual User that adds a person to their Network. For example, if three different users added Jon Snow to their Network, there would be 3 rows for Jon Snow, with a separate row for each of these relationships.

Sample Relationships Export. Check out the raw CSV file.
Contact Actions

Every time your users tap the Message, Email, or Call button on a person’s profile screen, or tap “Mark as Contacted” from the person’s action menu, we are keeping track of those button taps. This export details all those button tap events triggering contact actions. We give you information about the person, the user, the action, and the Contact Script selected for Message or Email actions (to learn more about setting up Contact Scripts, check out our Knowledge Base article here).

Note that depending on the user’s device, we may have more or less information in this export. For users on iOS, we only record the action if the user actually *sends* the message or email. For external messages, we are also able to include a column with iOS’s app identifier string. On Android and Web, we cannot tell when they’ve actually sent the message, so the action is recorded as soon as the user taps a button indicating that they at least intended to send a message or an email to that person.

These exports also include actions for any time a user updated an added persons’s name or address. Note that users can only update the name or address of a person who they themselves added to Reach, but we want to make sure you know when this happens, so the Contact Actions export is the place to look.

Note: We only began recording this data on July 18, 2019, so any contact actions initiated before that date will not appear in these exports.

Sample Contact Actions Export. Check out the raw CSV.

The users export is your route to understanding your Reach users. It includes everything from the Users admin table: our unique User ID, the user’s name, the date they were added to your campaign, their email address, their phone country code, their phone number, the number of people they have reached, and their permissions on the campaign.

The fist column of the user export is the unique User ID in Reach which will let you match users to their rows in the other export types. User IDs are consistent across campaigns.

User Export
Sample Users Export. Check out the raw CSV file.

Generating a New Export

From the export screen, select an export type, then pick your scope. Your options for scope are:

Date Range

  • All Records: As the name suggests, this scope allows you to get all the data Reach has of a certain type.
  • Custom Range: Use the date-pickers to choose a start and end date for your export.


For the “People” export only, you must also select which people you want to include. Your options here are your two auto-applied tags. This allows you to pull an export of only people included in your bulk uploads, only your users have added from the Reach app, or both at the same time.

Once you have selected a data type and a scope, click Export to download a CSV. In that CSV, you will find all the columns you need to Bulk Upload this data to another tool of your choosing such as VoteBuilder. You can map the various columns as you see fit. The last column will be a “Reach UID” column which is a unique value for every response in Reach. This is a good way to track unique responses in your own database, if needed.

Export Unique ID Column

A critical part of uploading to most CRMs (Like VoteBuilder) will be making sure your Reach exports include the necessary unique ID for each voter or respondent. If your data set includes more than one unique ID column, Reach allows you to specify which one should be used for your exports. This choice is made not on the export screen, but on the Campaign Settings screen. There, you’ll see a drop-down selector with all the available unique IDs so you can pick the one that will be most useful to you when you’re uploading these responses to an external CRM.

Was this article helpful?
How can we improve this article?
Need help?