Run an aggregate count
Counts show universe size, email readiness, phone readiness, and mail households. They do not expose voter-level records.
Campaign order help
How count packages, invoices, and file delivery work.
Use this guide when submitting a count package, approving an invoice, or tracking a fulfillment file from the public order page.
Order stepsFrom estimate to delivery
Choose a package
Priced packages can become invoices after review. Custom services stay quote-required until the scope is confirmed.
Confirm permitted use
File delivery requires a qualified campaign use case, source-path review, and any needed vendor or voter-file documentation.
Pay or approve the invoice
The public order page shows the invoice link when it is ready. Payment moves the order into fulfillment once Stripe confirms it.
Download delivery
Delivered files appear on the public order page with the filename, size, delivery date, and download link.
Package Guide
Pick the package that matches the next operational handoff.
Data file
Use this when the campaign needs a clean segment, voter-file export, append-ready fields, and model columns for its own tools.
Digital audience
Use this when the next step is a hashed ad audience handoff. Media spend and ad buying stay separate from the audience file.
Direct mail file
Use this when the campaign needs householding and a vendor-ready mail CSV. Print, postage, and creative production are separate unless scoped later.
Custom services
Use this for polling samples, GIS, consultant billing, training, managed execution, or anything that needs a manual quote.
Status ReferenceWhat the public order page means
Submitted
The request is queued for review. Package, count, and contact details are captured.
Reviewing
The team is checking scope, permitted use, source path, and any missing context.
Quoted
The scope is ready for approval, but no payment link has been issued yet.
Awaiting payment
The invoice is available on the public order page.
Fulfilling
Payment or approval is complete and the delivery file is in production.
Fulfilled
The file has been delivered and the public order page includes the download link.
Blocked
The order needs more information or cannot proceed until the review issue is resolved.
Delivery ChecklistBefore a file is released
ReadyThe submitted use case is a qualified campaign voter-data use.
ReadyThe source path is known: campaign-provided file, SoS application, partner provider, or enhanced CA file.
ReadyAny append needs, refresh cadence, and vendor handoff details are captured.
ReadyThe invoice is paid or manually approved for production.
ReadyThe delivered file is uploaded to the order with filename, size, checksum, and delivery timestamp.