Resources

Guides for getting it right the first time.

Practical help for list owners and sending partners.

Sending partners

Preparing a CSV for scrubbing

Save your file as CSV (comma-separated, UTF-8). Phase 1 accepts CSV only, with configurable limits currently set to 5 MB and 100,000 data rows. A header row is optional and is kept in eligible results.

One identifier column

Put email addresses or phone numbers in one identifier column. Other columns, like names or reference IDs, can stay. Choose one channel and map the identifier column before analysis. Eligible results preserve original columns; cells that could execute spreadsheet formulas are prefixed with an apostrophe for safety, including phone values beginning with +.

Formats that match

  • Email: any letter case, with spaces around the value. Jane@Example.com matches jane@example.com.
  • Phone: valid numbers are normalized to E.164, for example +14155550134. Choose a country for national numbers such as 4155550134; without it, those numbers are rejected. Countries are never guessed.
  • MD5: 32-character hex hashes of the already-normalized value (trimmed, lowercased email with dots and plus tags intact, or E.164 phone including +).

Before you upload

  • Split very large files so each one fits your remaining allowance.
  • Check that the right channel's lists are assigned to you. The upload page lists them.

List owners

Managing suppression lists

Create one list per channel and purpose, for example “Global email opt-outs” and “SMS STOP replies”. Lists are assigned to partners individually, so separating them lets you control exactly what each partner is scrubbed against.

Adding records

Add one suppression manually or import a CSV of up to 5 MB and 50,000 rows. Choose the identifier column and review validation before confirming. Existing records are skipped; smaller imports never remove earlier opt-outs. Review the added, duplicate and invalid counts in Import history.

Plain or hashed

Plain values are saved with their MD5 hash. If you'd rather not store addresses, upload MD5 hashes only. Use trimmed, lowercased emails with dots and plus tags intact, or E.164 phone numbers including the + sign.

Removing records

Only the owner can remove a suppression, with confirmation and a reason recorded in the removal audit. The list remains Pending until synchronized. Scrubbing refuses assigned lists whose latest changes are not Synced.

Both roles

Understanding monthly allowances

Each partner-company relationship has one owner-set allowance shared by every approved login and both email and SMS jobs. Adding another login does not add capacity. Stored suppressions are a separate measure.

What counts

Every nonblank data row excluding the CSV header counts once when an accepted job completes successfully. Duplicate and invalid rows count. Analysis alone consumes no allowance. Files with no usable identifiers are rejected.

When it's checked

Available rows equal monthly allowance plus approved additional rows, minus completed usage and active reservations. Before processing, the full row count is reserved atomically; concurrent jobs cannot exceed available rows. Success commits once. Confirmed terminal failures without a usable result release the reservation; uncertain timeouts stay reserved until reconciled.

Resets and increases

Calendar months follow the workspace timezone, and the exact reset is displayed. Unresolved reservations remain held across resets. Partners request a higher total; the owner approves additional rows for the current month or declines with a reason. Base allowance and access changes are also audited.

Sending partners

Retrieving results

Completed jobs reconcile every input row into invalid, duplicate, suppressed unique or eligible unique rows. Select Download eligible CSV to retrieve the first valid occurrence of each eligible identifier with the original columns and spreadsheet-safe escaping. Eligible means not found in the selected suppression lists; it does not establish consent or validate deliverability.

Download links last at most 60 seconds. Active company access is rechecked for each request. Results expire at the date shown on the job; owners configure future-result retention from 1–365 days. Confirmed failures without a usable result release rows; uncertain outcomes stay reserved until reconciliation.

Owners see their workspace jobs and eligible output. Approved partner-company logins see their authorized company jobs, never master lists or matched suppression records. Limits reduce probing but cannot eliminate membership inference.

FAQs

Still stuck? Contact us.

See it with sample data.

A walkthrough of lists, a partner invitation, an upload and a clean download.