Suppression List Import Conflict Report

What does the Suppression List Import Conflict Report do?

Compare intended audience-import rows with supplied global and audience suppression evidence before an import or cross-CRM handoff. Paste JSON arrays or mapped CSV exports and receive a source-linked report for human review. The Actor uses exact caller-defined contact keys and audience IDs. Already pseudonymized, consistent keys are recommended.

A result called no-supplied-match means only that no applicable record appeared in the supplied evidence. It does not establish consent, sendability, eligibility, lawfulness, or verified permission. Missing, partial, or ambiguous scope coverage remains unknown. Every candidate result requires review before an operator makes an import decision.

Why use a suppression import conflict report?

An operations team may hold a candidate export, a shared suppression export, and separate audience exclusion files. This report connects those supplied records while preserving each declared scope. A global record applies to every audience for the same exact key. An audience record applies only to its exact audience ID. It also exposes repeated candidate row IDs, repeated contact/audience identities, repeated suppression IDs, and contradictory scope coverage declarations. Nothing is silently overwritten.

Mailchimp’s suppression import documentation describes separate audience scopes and an existing native workflow. This Actor is useful for comparing exports across systems; it does not operate that workflow, change contact status, or perform a live import. It does not send email, scrape websites, verify addresses, normalize actual email addresses, infer consent, or provide legal compliance advice.

How to prepare an import review

1. Create a consistent opaque contactKey across the candidate and suppression exports. Preserve exact strings, including leading zeros and case.
2. Supply candidate rows with rowId, contactKey, and audienceId.
3. Supply suppression rows with recordId, contactKey, scope, audienceId, reason, and source. Use scope:"global" with audienceId:"", or scope:"audience" with a nonempty exact audience ID.
4. Declare coverage separately for the global suppression scope and each relevant audience scope. Coverage rows require coverageId, scope, audienceId, status, and source. Choose complete, partial, or unknown based on the supplied export. An empty coverage table is valid and yields unknown coverage.
5. Run once and review the candidate table, findings, identity groups, and scope coverage before deciding what to do in your CRM.

Input and CSV mapping

See the input tab for the full configuration. snapshotId, matchingPolicy:"exact-keys", and noMatchPolicy:"evidence-only" are explicit required choices. Each of the three tables must be supplied as either an array or nonempty CSV. Use [] for a legitimate empty table. Remove its array when using CSV. A header-only CSV represents an empty table.

CSV accepts UTF-8 BOMs, quoted commas, and quoted multiline text. Canonical headers match the field names above. Optional candidatesColumns, suppressionsColumns, and coverageColumns map every canonical field to a distinct export header. Unmapped columns, duplicate headers, irregular rows, unknown JSON fields, invalid scopes, blank IDs, and surrounding ID whitespace are rejected. Source references use one-based array positions or logical CSV record numbers, including the header.

Capacity is 5,000 combined input rows, 4 MB input JSON, and 20,000 candidate/suppression evidence links. Excessive evidence amplification is rejected without truncation. Split larger exports into separate reviews, retaining the relevant suppression and coverage evidence for each batch.

Output and interpretation

Field	Meaning
status	blocked-by-supplied-evidence or no-supplied-match
coverageStatus	Complete only when both relevant scopes have a single complete caller declaration; otherwise unknown
globalCoverage, audienceCoverage	Each supplied scope’s complete, partial, or unknown coverage
identityStatus	Unique, duplicate, or conflicting candidate identity
suppressionEvidenceIds, sourceRefs	Links back to retained supplied evidence

One dataset item contains the full report and its rows array. Download full JSON (OUTPUT), flat candidate CSV (evidence.csv), findings CSV (findings.csv), and standalone HTML (report.html) from the output links. CSV cells neutralize spreadsheet formulas; HTML escapes supplied text and includes no external scripts. The full JSON stays below 8 MB and each export below 9 MB, checked before charging.

Price, storage, and repeat runs

The price is $0.25 per completed report, with platform usage included and no startup or dataset-item fee. Invalid input, insufficient budget, or exceeded output limits fail before the report event is charged. Each new run is a new report and may be billed again. Resuming the same run reuses an intact saved report and one report charge. A failed run can leave partial uncharged export files; resuming rewrites them before completing delivery.

Only process data you are authorized to use. Input and result files remain in Apify run storage and may include identifiers if you supply them. Review your run storage and access settings before uploading exports. Use the API tab for programmatic runs and the Issues tab for questions or reproducible problems. This report cannot determine whether your exports are complete, current, accurate, or lawful to use; coverage remains your declaration.