How to Export Campaign Members in Salesforce

You can export Campaign Members in Salesforce using Reports, Data Loader, or Workbench, but standard exports may show blank fields. The first thing to check is object-level Read access on CampaignMember: without it, the object won’t appear in Reports or return data via the API. Lead and Contact fields, such as Email and Phone, also require a custom report type or a SOQL query using dot notation for API-based exports

A handful of architectural facts about CampaignMember explain almost every export problem you’ll hit. Knowing them upfront saves hours of debugging.

CampaignMember is a junction object. Each record connects a Campaign to either a Lead or a Contact, never both at once. If the Allow Accounts as Campaign Members setting is turned on in Setup, the record can also connect to a Person Account. This does not apply to regular business accounts, only Person Accounts. If you add a record with both a ContactId and a LeadId, the API keeps only the ContactId. It drops the LeadId and doesn’t show any error or warning.

The LeadOrContactId field is polymorphic. With Accounts as Campaign Members enabled, it points across three different objects (Lead, Contact, Account). Reports and queries built before that setting was switched on may quietly miss Account-based members. The LeadOrContactOwnerId field works the same way. It points to either a User or a Group (queue), depending on who owns the record.

Here’s the part that breaks most exports: standard fields like Email, Phone, MobilePhone, Title, FirstName, and LastName are not stored on the Campaign Member record itself. The UI pulls them from the parent Lead or Contact at view time. The API and Reports treat them as fields on a different object so they don’t appear in a flat export.

That UI-vs-storage gap is the single biggest source of broken exports. Before walking through the methods, here are the five reasons fields don’t make it into your CSV.

You see Phone, Email, and Title on the CampaignMember record in the UI. You add them to your report, and they appear, yet the exported CSV shows blank columns or missing data.

This isn’t a bug. It’s a direct result of how the CampaignMember junction object stores data. Here are five specific reasons why this occurs.

This is the most common blocker. The main gating mechanism is the profile-level object permission. If a user lacks Read access to CampaignMember in their profile, they can’t access it in Data Loader, Workbench, or the API. 

The Marketing User checkbox is for users who manage campaigns. However, it doesn’t control export access on its own.

Go to Setup → Users → [your user] and confirm that the Marketing User checkbox is selected. Then, verify that the user’s profile has Read or Edit access to both Campaign and CampaignMember.

The Salesforce UI joins parent fields to the Campaign Member view at render time. Reports and the API don’t do that. They treat Lead.Phone and Contact.Phone as fields on different objects. CampaignMember.Phone does not exist.

Check: Use the Campaigns with Campaign Members report type or query the parent fields with dot notation in SOQL. Both methods are covered below.

Even when a field is queryable, Field-Level Security can hide it for your profile. If Lead.FLS hides phone, the export returns blank(no error, just empty cells).

Check: Setup → Object Manager → Lead (or Contact) → Fields → [field] → Set Field-Level Security. Verify the field is visible for the profile you’re using to export.

When this setting is on, LeadOrContactId becomes polymorphic across three objects. Reports made before this feature started may not include Account-based members. This is because the report type didn’t consider the third parent.

Check: Setup → Marketing → confirm whether Accounts as Campaign Members are enabled. If it is, audit your existing report types.

Per official Salesforce documentation, Experience Cloud users have varying access to CampaignMember depending on their license type — Customer Community, Partner Community, or Customer Community Plus. Verify access per license type before assuming the issue is permission-related.

This is the path most admins start with. It works well for everyday exports, as long as you know the format-specific limits.

Here’s the accurate table from Salesforce documentation:

A few constraints matter more than row limits in real-world exports:

Reports are the right starting point, but you’ll outgrow them when:

For these cases, switch to Data Loader (production-scale, scriptable, schedulable) or Workbench (one-off, no install). Both are covered next.

Data Loader is the right tool for production-scale exports and round-trip workflows. Install it once from Setup → Data Loader, sign in, and you’re ready.

Choose Campaign Member as the object.

Select required fields and add a filter that creates an SOQL query to get records of the required Campaign Id(s). Specify the destination CSV file, then click on finish.

If you run SELECT Id, Phone FROM CampaignMember and the Phone column comes back blank, that’s expected. The CampaignMember object doesn’t store phone numbers directly. The Lead or Contact linked to the campaign member stores them.

To get phone numbers, query the parent record with dot notation. It’s like following a path from the campaign member to the lead or contact.

One thing to keep in mind: every campaign member is linked to either a Lead or a Contact, never both. So if a row belongs to a Lead, the Contact fields will be blank, and vice versa.

See the CampaignMember Object Reference and SOQL Relationship Queries guide on developer.salesforce.com for more details.

In Data Loader, go to Settings and enable Use Bulk API or Use Bulk API 2.0 for operations with batch size above 200 records. Bulk API runs asynchronously, parallelizes batches, and skips the synchronous SOAP path.

Bulk API 1.0 supports up to 15,000 batches per rolling 24-hour window at 10,000 records per batch.
Bulk API 2.0 handles batching internally and scales to ~150 million records per 24 hours. Use 2.0 for new implementations.
Enterprise Edition REST API allocation is 100,000 requests per 24 hours plus 1,000 per user license; Bulk API draws from a separate pool.

For exact figures: API Request Limits and Allocations.

Workbench answers a question most competitor articles never address: how do you export Campaign Members without installing anything?

Use Workbench when Data Loader is not installed and you need a one-off export. It is also the right choice when you want to test a SOQL query against CampaignMember before running it at scale, when your workstation restricts desktop application installs, or when you need a quick visual check of what a complex polymorphic query returns.

Go to workbench.developerforce.com. It runs entirely in the browser, and authenticates via OAuth(no installation required).

Select Production or Sandbox, choose the appropriate API version, and accept the OAuth consent screen to log in.

Jump to SOQL Query and select the object as Campaign member. Use relationship dot-notation to access Lead and Contact fields from the polymorphic relationship on CampaignMember:

Set the result format to Bulk CSV and run the query. Download the CSV file directly from your browser.

Status mismatches behave differently based on the import method:

• Data Loader and API imports reject records with invalid Status values and log them in the error file while the job continues.
• If the Status field is blank, Salesforce may assign the campaign’s default status, depending on the import method.
• Third-party integrations may reject the record or use the campaign’s default status based on their configuration.

These issues can cause failed imports or incorrect campaign reporting.

Run this query before importing:

Match every Status value in your CSV against the Label values returned by the query.

For standard fields and most export volumes, the Campaigns with Campaign Members report exported in Details Only format as a CSV is the right way. For production-scale, scheduled, or round-trip workflows, Data Loader with Bulk API and SOQL queries handles what Reports can’t. 

For one-off pulls without installing anything, Workbench gets the job done in a browser. And before you debug missing fields in any export, verify Marketing User permission and Field-Level Security on the parent Lead or Contact.