Skip to main content

​
Preparing Contacts

Clean contact data is what makes campaigns predictable. This guide shows how to prepare contacts and load them into Truedy using either:
  • the Contacts API (recommended for reuse + analytics)
  • the Batch Call contacts upload endpoint (good for quick drafts)

​
Who this is for

  • Teams building outbound campaigns with folders/segments.
  • Developers importing leads from CSV or CRM exports.

​
The one rule: use E.164 phone numbers

Every outbound call ultimately depends on a phone number in E.164 format. Examples:
  • +14155550123
  • +15551234567
Avoid:
  • 415-555-0123
  • (415) 555-0123
  • local formats without country code
This matters because the API validates phone numbers and because telephony providers only accept normalized numbers. When you import contacts into a folder, you can reuse that curated set across campaigns. High-level flow:
  1. Create a contact folder
  2. Import contacts into that folder (CSV or JSON)
  3. Create a batch campaign using that contact_folder_id

​
1) Create a folder

​
2) Import contacts (JSON array)

For CSV import, use the same endpoint and provide csv_base64.

​
Alternative workflow: upload contacts directly to a draft campaign

If you want a one-off campaign draft, you can upload contacts to the batch call directly. Endpoint:

​
Upload inline contacts to a draft campaign

​
Deduping and data quality

Best practices:
  • Deduplicate by phone_number in your own system before importing (prevents wasted calls).
  • Keep consistent first/last name fields if your prompt relies on personalization.
  • If you rely on segmenting, use metadata/custom fields consistently (and document the keys you use).

​
Next steps