BigQuery Consent Data Export: Architecture Guide

For data-driven organizations, having consent data in your warehouse alongside behavioral and transactional data unlocks powerful compliance analytics and marketing insights.

Why Export to BigQuery?

BigQuery gives you the ability to join consent data with your existing datasets — understanding consent rates by customer segment, campaign source, or product category.

Architecture

Arqam360 streams consent events to BigQuery via the platform connector — each consent record includes visitor ID, consent choices, timestamp, jurisdiction, and GPC status.

Data Schema

• consent_id: unique consent record identifier
• visitor_id: anonymous visitor identifier
• domain: website domain
• consent_analytics: boolean
• consent_marketing: boolean
• consent_functional: boolean
• jurisdiction: detected regulatory regime
• gpc_detected: Global Privacy Control status
• created_at: consent timestamp
• updated_at: last modification timestamp

Useful Queries

Common queries include consent rate by traffic source, consent trends over time, revenue impact of consent choices, and compliance audit reports for regulators.

Setup Steps

• Create a BigQuery dataset for consent data
• Generate a service account key with BigQuery write access
• Connect BigQuery in your Arqam360 integrations dashboard
• Enter your project ID, dataset, and service account key
• Configure export frequency (real-time or batch)
• Validate data in BigQuery console