Import participants from a CSV

Add participant records with explicit choices for updates, reporting, and follow-up.

Prepare the promotion and file

Open a promotion's Participants panel and select Import. Download its current CSV template. Keep the header row and replace the example data with your own rows. The template reflects supported fields for that promotion, so use a fresh copy after changing the form.

Uploads must be CSV files no larger than 10 MiB. Supported columns include participant contact details, a unique identifier, initial entries, entry source, timestamp, and supported custom fields. File uploads, signatures, payment, and CAPTCHA cannot be imported as completed form interactions.

Choose the import's effects

Review the options before starting:

  • Counting imported entries in analytics is off by default. Turn it on only when imported participation belongs in your reported campaign results.
  • Updating existing participants is off by default. Choose deliberately whether matching records should be updated.
  • Triggering workflows is off by default. It requires permission to edit promotions, an active attached Form Submitted flow, and confirmation that the imported contacts have permission to receive that workflow.

Participant imports do not automatically sync contacts to promotion integrations. Importing a row is also not proof that a person completed verification, paid, signed a document, or consented to marketing.

Review completion and failures

Wait for processing and review created, updated, skipped, and failed results. Correct failed rows before importing again; do not assume every row in an accepted file succeeded. Avoid resubmitting the entire file without considering existing participants and any enabled follow-up.

Test a small staging file first, including a new person, an existing person, and an invalid row. Confirm participant details, entry totals, reporting treatment, and any explicitly enabled workflow. Store and dispose of CSV files according to your organization's personal-data policy.