Activation detail

Activation detail

The activation detail view at /activation/{id} is the control surface for one audience activation — the pipe that pushes a consent-cleared audience to an ad platform (Meta, Google, LinkedIn, TikTok, Reddit, Snap, X) as a hashed match list. It is served by the /v1/activation API (api/routes/activation.py), which orchestrates resolve → consent gate → hash → upload → audit.

What the page controls

The header shows the activation's status and destination. Primary actions map directly to endpoints:

• Run — POST /v1/activation/activations/{id}/run executes the full pipeline and reports included_count / suppressed_count.
• Pause / Resume — POST …/pause and …/resume toggle the activation's lifecycle state.
• Run history — GET …/runs pages through past runs; selecting one opens the member audit.

The consent gate is the point

Before any identifier is hashed or uploaded, every candidate passes apply_consent_gate (core/activation/consent_gate.py), which classifies each member as included or suppressed with one of four reason codes rendered in the suppression donut:

An activation declares a purpose — advertising, retargeting, lookalike_seed, or suppression_list — and the gate maps that to the consent ledger's action type and purpose string (PURPOSE_MAP). This is why a raw CRM segment and the audience that actually reaches Meta are different sizes: the suppressed members never leave the building.

Preview before you run

POST /v1/activation/activations/{id}/preview runs resolve + gate + hash without uploading or persisting — a dry run that returns the included/suppressed counts and breakdown so marketing-ops can see exactly what would ship. Preview deliberately never exposes the hashes themselves.

Hashing and matching

Included members are hashed with the canonicalization every ad platform expects: sha256(email.strip().lower()) for email and sha256(digits_only(phone)) for phone (core/activation/hashing.py). The platform hashes its own user data the same way and matches on equal hashes — the raw email or phone never leaves Pact. Because upload is keyed by the same hashed identifiers, re-running an activation is idempotent.

Member audit

Selecting a run opens the per-member audit (GET /v1/activation/runs/{id}/audit), a paged drilldown of every candidate with its included / suppressed action and reason — the compliance record proving why each person was or wasn't uploaded.

segment ──▶ consent gate ──▶ included ──▶ sha256 ──▶ platform upload
                 │
                 └──▶ suppressed (opted_out | purpose_missing |
                                  jurisdiction_mismatch | no_match_key)
                          │
                          └──▶ activation_member_audit (per-member reason)