This guide provides an overview of data exports in Social Sync: what's available, what each export is for, how to access them, and how we manage changes.

The following exports are also available but do not have published specifications as their content depends on the fields you have enabled:

The Campaign Export and Event Export are being retired. Further details on timing will be communicated separately.

In addition to the published export specifications, sample files are available for each export in the following formats:

You can also download CSV sample exports from either of these sources.

The Transactions export gives you one row per transaction line item. This is your primary financial export.

Use it for: reconciling income against your payment processor, preparing Gift Aid submissions, reporting on income by campaign or event, understanding donation patterns (platform, frequency, payment method), and tracking payouts.

Each row includes full donor details, the campaign and event the transaction belongs to, and a "Linked Record" showing what the transaction relates to - whether that's a donation to a fundraiser page, a donation to a team page, or a ticket/item purchase linked to a registration.

Product transactions (tickets and items purchased in the same checkout) share a Platform ID, so you can group them to see what was bought together.

Recurring donations are identified by a Recurring ID, with the type (Subscription or Direct Debit) and the date the recurring arrangement was first created.

The Audience export gives you one row per supporter record. This is your most complete view of your supporter base.

Unlike the Registrations export (which only includes people who have registered for a campaign), the Audience export includes all supporter records in your account - including leads, applicants, and supporters who haven't yet completed a registration. It also includes each supporter's audience segment, which represents their position in the funnel: Lead, Registrant, Fundraiser, or Active Fundraiser (has at least one donation). This makes it particularly useful for tracking supporter progression and for CRM syncs where you want the full pipeline.

Full column specifications and a detailed guide will follow.

The Registrations export gives you one row per campaign registration. This is your primary export for campaign-level supporter data.

Use it for: segmenting supporters by event/campaign/tags, managing ticket allocations, monitoring team membership, and supporter communications (this is the only export that includes full marketing consent data for all channels).

Each row includes the supporter's personal details, address, marketing consent across all channels (email, SMS, WhatsApp, phone, post), their fundraising totals, ticket details, team membership, activity tracking, and motivation data.

Registrations can have a type of either Adult or Child. Child registrations are linked to an Adult registration, do not receive communications, and follow a minimal data approach - only essential fields are collected, so many columns will be blank for child records.

If you need per-platform fundraising breakdowns (e.g. how much was raised on Facebook vs JustGiving for a specific registrant), use the Transactions or Fundraisers export filtered by the relevant supporter.

The Fundraisers export gives you one row per fundraiser page. A single registrant can have multiple fundraiser pages across different platforms.

Use it for: monitoring fundraiser page performance, identifying inactive or underperforming pages, comparing fundraising across platforms, and page-level reporting.

Each row includes the fundraiser's platform, title, URL, target, and aggregated donation totals (including pledged income and Gift Aid). It also includes the supporter who owns the page and the campaign/event it belongs to.

The key difference between Registrations and Fundraisers: the Registrations export gives you one row per person with their total fundraising across all their pages. The Fundraisers export gives you one row per page, so a registrant with a Facebook fundraiser and a Social Sync fundraiser will appear as two rows.

This export does not include marketing consent data. Use the Registrations export for consent.

The Teams export gives you one row per team fundraising page.

Use it for: tracking team performance, identifying top and underperforming teams, contacting team captains, and reporting on team-level fundraising and activity.

Each row includes the team's metadata (type, status, URL, title, target), aggregated fundraising totals across all team members, activity tracking, and the team captain's contact details and address.

Individual team member details are not included here. Use the Registrations export (which includes Team ID, Team Role, and Team URL) to see individual members and their roles within a team.

The Orders export gives you one row per order line item.

Use it for: merchandise fulfilment, tracking item orders, and managing physical deliveries.

This export is covered separately and is not changing in this release. An updated version is expected later.

"I need to reconcile income and prepare financial reports" - Use Transactions. This is your single source of truth for all financial data, including payout tracking.

"I need to upload supporter records to our CRM" - Use Audience if you need all supporter records including leads and applicants. Use Registrations if you only need confirmed registrants with their campaign-specific fundraising totals and consent data. Which is right depends on how your CRM is set up - some teams only want registrants, others want the full pipeline.

"I need to submit a Gift Aid claim" - Use Transactions. Filter by Gift Aid = True and the relevant Gift Aid Status.

"I need to see how individual fundraiser pages are performing" - Use Fundraisers. One row per page lets you compare performance across platforms.

"I need to see how much each registrant has raised in total" - Use Registrations. The consolidated totals give you a single figure per person.

"I need to contact team captains about their team's progress" - Use Teams. Captain contact details and team totals are included.

"I need to see which team members are active or inactive" - Use Registrations filtered by Team ID. Each registrant's team role and fundraising totals will show you who's contributing.

"I need to know which tickets a registrant purchased" - Use Registrations for the ticket attached to a registration, or Transactions (filtered by Type = "Product") for the full transaction detail including discount codes and pricing.

"I need to check marketing consent before sending a campaign" - Use Audience or Registrations depending on the segments you want to contact. These are the only export that includes marketing consent data.

"I need to fulfil merchandise orders" - Use Orders.

There are various ways to export data from Social Sync. How you choose to do so may depend on your role, though any user can export data in all three ways.
​

Fundraising / events teams. You're more likely to be focused on the performance of specific campaigns, so the campaign dashboard is the easiest place to export data. See our guide on How to export campaign data.

Data analysis / financial reconciliation teams. You're more likely to be interested in downloading data in bulk, either for a specific period (e.g. quarterly donation data) or for an entire campaign for reconciliation purposes. See our article on How to export data in bulk.

Stewardship / supporter care teams. You may want to export data for a single supporter to understand them better. In addition to the above two methods, you can also export data from the data tables on each supporter's Campaign Record.

We understand that changes to our exports can cause work downstream - for example, updating column mapping for CRM imports. We will always give sufficient notice of updates so that changes can be managed effectively.

Major changes (e.g. v2.0 to v3.0): we will give at least 4 weeks' notice. Previous export versions will remain available for a transition period.

Minor changes (e.g. v3.0 to v3.1): we will aim to give 1-2 weeks' notice.

Single-file changes (e.g. v3.0 to v3.0.1): we will still aim to give 1-2 weeks' notice, with only the affected file's version incremented.

In rare circumstances we may need to make changes more quickly, but we will communicate as clearly as possible.

To reduce the frequency of updates that impact your work, we sometimes add placeholder columns to an export spec. These columns may be blank at the time of the update, but by including them as placeholders we can begin populating them with data later without requiring a full spec update. We will communicate separately when placeholder columns become active.