Contact Data

1. 1

   Party / authorized voter data

   VAN for Democratic campaigns, Data Trust-linked or other authorized Republican voter-data sources, or another voter-file source the campaign is entitled to use. Access method depends on the campaign’s existing permissions and provider relationship.

2. 2

   Campaign-owned data

   Existing supporter, donor, volunteer, event, petition, website, fundraising, phone-bank, and prior-outreach lists owned or controlled by the campaign.

3. 3

   Approved supplemental outreach data

   Additional contact sources approved for the campaign program, including supplemental small-business-owner contact data sourced through 360AI Media when included in the agreed FreeMessaging.ai outreach scope and permitted for the intended use.

1. 1

   Authorized voter-data access or exports

   Where applicable, access or approved exports from VAN, Data Trust-linked sources, another voter file, or the campaign’s existing data provider. The campaign must have authority to provide or connect the data.

2. 2

   Campaign-owned contact files

   Current supporter, donor, volunteer, event, fundraising, signup, and other campaign-managed contact lists that should be considered for the messaging program.

3. 3

   Field definitions and source context

   Enough information to understand what each file and field means, including source IDs, voter/supporter status fields, geography, audience labels, and relevant historical fields.

4. 4

   Suppression and opt-out information

   Current do-not-contact, opt-out, suppression, or other exclusion information that should carry forward into the FreeMessaging.ai data environment.

5. 5

   Audience and data-use priorities

   Direction on which sources and segments should be prepared first and any known restrictions on how particular data sources may be used.

6. 6

   Approval for supplemental data

   If the campaign will use supplemental outreach data, approval of the audience definition, geographic scope, and intended messaging purpose.

• Create a source inventory showing which party, campaign-owned, and supplemental datasets will be used.
• Coordinate secure receipt of exports or connection information using the method appropriate for the campaign and provider.
• Profile incoming files and map source-specific fields into a common FreeMessaging.ai contact structure.
• Normalize names, phone numbers, email addresses, geography, addresses, dates, and other fields needed for matching and segmentation.
• Deduplicate records across sources while preserving source provenance, source IDs, and materially different campaign attributes.
• Carry forward campaign-provided suppression, opt-out, exclusion, and contact-status data into the import-ready dataset.
• Flag records with missing, malformed, conflicting, or incomplete fields for campaign review rather than silently inventing values.
• Add approved supplemental outreach data where the campaign has requested it and the data is within the agreed scope.
• Prepare the unified contact dataset and mapping documentation for Step 5 — Build the Voter CRM.

• Campaign data owner / authorized staff contact
• List of contact sources to be included in the first messaging program
• Authorized VAN, Data Trust-linked, voter-file, or other provider access / export where applicable
• Current campaign-owned supporter, donor, volunteer, event, fundraising, and signup files
• Source IDs or field dictionaries where available
• Current opt-out, suppression, do-not-contact, and exclusion lists
• Geographic and audience priorities for the first program
• Approval and scope for supplemental small-business-owner or other outreach data, if used
• Known source-use restrictions or provider-specific requirements
• Preferred secure transfer / connection method and expected data-refresh cadence

• The campaign does not yet have authorized access to its party voter file or data provider.
• Exports arrive with missing field definitions, unknown codes, inconsistent column names, or different schemas across files.
• The same voter appears in multiple sources with conflicting phone, address, support-status, or identity information.
• Suppression / opt-out history is incomplete or is stored separately from the main campaign contact lists.
• Source-specific IDs needed for future synchronization are missing from the export.
• Phone numbers are missing, malformed, shared across multiple people, or not clearly associated with the intended contact.
• The campaign changes its target geography or first messaging audience after mapping and quality work has begun.
• A third-party data provider controls export/API permissions or timing and FreeMessaging.ai cannot independently accelerate that provider’s approval process.
• Supplemental data scope has not yet been approved or the intended use requires additional campaign/compliance review.

Questions