Ananasi · Campaign services
Campaign Contact Imports
An import should preserve record provenance while producing usable, clearly scoped campaign data.
Built around your contact import preparation.
Campaign identity
Use the committee’s campaign identity; keep official government notices separate.
Jurisdiction and scope
Use the actual electoral district, county, city, or retention jurisdiction.
Replies and opt-outs
Assign response coverage and keep suppression records current.
SMS or MMS. The format your campaign needs.
The service conversation
Column mapping, number normalization, duplicate handling, permission evidence, and suppression are different checks. Confirm supported formats before preparing a production file.
Review an import specification
Ask the provider for its actual file schema and limits. Test with synthetic rows covering missing fields, duplicate numbers, invalid formatting, and suppressed contacts before transferring campaign data securely.
- Schema
- Source identifier
- Validation errors
- Suppression merge
Use edge cases in the trial file
A synthetic import can include two formats of the same number, a blank field, and a record previously suppressed. Compare the returned result with the written schema and merge rules. A successful file upload should not be interpreted as proof that every imported record is eligible for the planned campaign messages.
What to retain from this review
- Field mapping
- Synthetic edge-case file
- Validation and merge result
- Secure transfer arrangement
Common questions
What belongs in the first inquiry?
Your committee, office, jurisdiction, target timing, and the schema requirement. Keep recipient lists and access credentials out of the inquiry form.
Let’s plan your next campaign message.
Start with your office, location, and campaign timeline.