Set up the DROP integration

This guide walks through creating and configuring the California DROP erasure integration. DROP only mints erasure privacy requests, and a single integration is supported per Astralis deployment.

Prerequisites

Before you begin, collect the following:

• DROP API key — issued by the California Privacy Protection Agency when you register as a data broker (opens in a new tab) on the DROP platform. Sandbox keys are issued separately from production keys and are requested from the CPPA through that same registration; a sandbox key only works against the Sandbox environment.
• A Snowflake integration — the DROP match index is built inside your Snowflake warehouse, currently the only supported storage engine for the index, so a working Snowflake integration is required before DROP cycles can run. See Match index & backfill.
• An erasure policy (optional) — the request policy used when minting erasure privacy requests for matched consumers. If omitted, Astralis records matches in the suppression ledger without minting erasure requests.

Required permissions

DROP administration is guarded by dedicated scopes. The built-in Owner and Contributor roles include them; custom roles need:

Create the integration

1. Navigate to Integrations and click Add integration.
2. Select California DROP.
3. Provide the connection details:
   • API key (required) — your DROP API key. Stored encrypted.
   • Environment (optional) — Production (default) or Sandbox.
   • List types (optional) — the DROP list types to process (Email, Phone, MAID, CTVID, NDZ, NameVIN). Leave empty to process every list DROP delivers.
   • Policy (optional) — the erasure policy for minted erasure requests. Leave empty to record suppression decisions in the ledger without creating erasure requests.
4. Click Save, then use Test connection to confirm Astralis can authenticate against the DROP API.

Configure and backfill the match index

After the connection test succeeds:

1. Open the Mapping tab.
2. Select the Snowflake integration and Target schema where Astralis should create the match index.
3. Enter the Gather query that resolves your consumer identifiers. See Match index & backfill for the query contract.
4. Click Validate & save and resolve any reported validation errors.
5. Click Run backfill to build the index.
6. Confirm Backfill status shows a successful run. Scheduled DROP cycles can now begin.

What happens next

Once the integration is active and the first backfill has completed, Astralis runs automatically every day (all times Pacific):

Monitor runs from the DROP cycles tab on the integration page, and see Suppression cycles for the full lifecycle.