Warehouse Export Connector for Revive Adserver (BigQuery, S3, Snowflake)

Warehouse Export Connector sends delivery and click data from Revive Adserver to Google BigQuery, S3-compatible storage and Snowflake stages on a schedule. Data teams get incremental exports with logs and retry, in a layout suitable for clean room workflows.

What it does

• Exports run on a schedule and are incremental, so your warehouse stays current without repeated full copies.
• Delivery and click data go to Google BigQuery, S3-compatible storage and Snowflake stages, so analysts work in the platform they already use.
• S3-compatible storage receives Parquet, NDJSON or CSV, so the file format matches the tool reading it.
• Hashing options for identifiers let you export without raw identifier values where your policy requires it.
• Export logs and retry show what was sent and recover failed runs, so gaps in the warehouse are visible and fixable.
• The output layout suits clean room workflows, so the data can be prepared for joining with partner data.

How it fits your ad stack

The connector reads delivery and click data from Revive Adserver and writes it to destinations you configure. IAB Tech Lab publishes Data Clean Rooms Guidance v1.0, and the output layout is designed with clean room workflows in mind. Teams combining ad logs with other data usually decide first which identifiers are exported and in what form, which is where the hashing options apply.

Full feature details

• Scheduled incremental export.
• Delivery data export.
• Click data export.
• Google BigQuery destination.
• S3-compatible storage destination with Parquet, NDJSON and CSV output.
• Snowflake stage destination.
• Hashing options for identifiers.
• Export logs.
• Retry of failed exports.
• Output layout suitable for clean room workflows.

Requirements

• A running Revive Adserver 6.x install.
• An account and access credentials for each destination you enable: Google BigQuery, S3-compatible storage or Snowflake.
• Permission to write to the target dataset, bucket or stage.
• Scheduling needs (for example cron) are confirmed at order.

Frequently asked questions

Which file formats are available?

For S3-compatible storage: Parquet, NDJSON and CSV.

Can identifiers be hashed before export?

Yes. Hashing options are available for identifiers.

What happens if an export fails?

Export logs record the run and the connector retries.