Two-way sync
Changes in BigQuery or D2l Brightspace instantly reflect in both systems. No stale data, no manual imports.
Keep BigQuery and D2l Brightspace in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Workforce data is some of the most requested data in the warehouse and some of the most awkward to move: the record types are many, the fields carry sensitive personal information, the APIs are strict, and hand-built extract jobs go stale or break quietly. Whether D2l Brightspace is the system of record for employees and payroll, for candidates and applications, or for learners and course completions, the reporting belongs in BigQuery next to everything else the company measures.
Stacksync syncs Org Units, Grades, Content (Modules, Topics, and User Progress), Quizzes from D2l Brightspace into tables in BigQuery continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in BigQuery, such as headcount rollups, cost allocations, or attrition risk flags, can be written back to fields in D2l Brightspace where the HR team acts on them. You configure which records and fields cross over, and in which direction, instead of maintaining pipeline code.
People and organization records from D2l Brightspace arrive in BigQuery as queryable tables, current within seconds instead of a day behind, replacing hand-built extract jobs.
Analysts combine D2l Brightspace's workforce records with finance, product, or operational data already in BigQuery for reporting the HR system cannot produce on its own.
Because changes stream continuously, reports query current workforce data rather than waiting for an overnight load window to finish.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| BigQuery objects | D2l Brightspace objects | How this pairing syncs | |
|---|---|---|---|
| Clustered tables Supported; clustering is transparent to the sync. | Groups and Sections Group categories, groups, and section membership within an org unit; enrollments are read and written to keep cohort assignments aligned. | Clustered tables is specific to BigQuery and Groups and Sections to D2l Brightspace — each maps to any object or custom field on the other side. | |
| Datasets Organizational container — you pick which dataset’s tables to sync. | Users User accounts in the Learning Platform (lp) component; created, read, updated, and deleted through the Valence API and typically synced two-way with an SIS or HRIS. | Datasets is specific to BigQuery and Users to D2l Brightspace — each maps to any object or custom field on the other side. | |
| Projects Connection scope: the service account grants access per project. | Enrollments Links between Users and Org Units; enroll/unenroll and batch-enrollment routes let rosters be written from an upstream system and read back for reporting. | Projects is specific to BigQuery and Enrollments to D2l Brightspace — each maps to any object or custom field on the other side. | |
| Tables The syncable unit: only tables can be synced per the Stacksync docs. | Org Units The org structure — course offerings, sections, departments, and semesters; read for hierarchy and created/updated to provision courses from a database. | Tables is specific to BigQuery and Org Units to D2l Brightspace — each maps to any object or custom field on the other side. | |
| Partitioned tables Synced like regular tables; partition columns map to target fields. | Grades Grade objects, categories, schemes, and per-user grade values in the Learning Environment (le) component; values can be read out and written back onto the gradebook. | Partitioned tables is specific to BigQuery and Grades to D2l Brightspace — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionChanges in BigQuery are captured at the source via change data capture — no polling loop against its API. Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen").
DeliveryEach detected change is written to D2l Brightspace through its API, with automatic retries and rate-limit backoff.
DetectionD2l Brightspace notifies Stacksync of record changes through webhook events. Polling Valence endpoints with date/bookmark filters, differential Brightspace Data Sets (BDS) bulk exports for changed rows via the Data Hub, and.
DeliveryEach detected change is applied to BigQuery as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every BigQuery–D2l Brightspace connection.
Changes in BigQuery or D2l Brightspace instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever BigQuery or D2l Brightspace data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single BigQuery or D2l Brightspace record.
Track your BigQuery ⇄ D2l Brightspace sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between BigQuery and D2l Brightspace.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate BigQuery and D2l Brightspace with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the BigQuery and D2l Brightspace objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between BigQuery and D2l Brightspace: authenticate both systems, choose the objects to sync (such as BigQuery's Clustered tables and Datasets), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for BigQuery and D2l Brightspace: HR data in the warehouse, minus the pipeline; Headcount and cost joined with everything else; Fresh data instead of last night's load. People and organization records from D2l Brightspace arrive in BigQuery as queryable tables, current within seconds instead of a day behind, replacing hand-built extract jobs.
BigQuery: GoogleSQL via the BigQuery REST API, client libraries, JDBC/ODBC drivers, and the Storage Read/Write APIs. Authentication: Google Cloud service account: create a dedicated service account, grant roles (BigQuery Data Editor, BigQuery Job User, Cloud Functions Service Agent, Cloud Run Developer, Eventarc Event Receiver. D2l Brightspace: Brightspace (Valence) REST API split into independently-versioned Learning Platform (lp) and Learning Environment (le) components, plus the Data Hub / Data Export Framework and Brightspace Data Streams. Authentication: OAuth 2.0 authorization-code grant against the D2L auth service (auth.brightspace.com); a registered app holds a client ID and secret with per-scope grants (group:resource:action, e.g. users:userdata:read), short-lived access tokens, and refresh tokens. Stacksync manages authentication, retries, and rate limits on both sides.
BigQuery: The Storage Write API supports high-throughput streaming ingestion, which suits continuous sync loads better than legacy streaming inserts. D2l Brightspace: Differential Brightspace Data Sets can contain duplicate rows with identical values, so consumers must de-duplicate when reading changed data. Stacksync's field mapping accounts for these differences between BigQuery and D2l Brightspace without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means BigQuery and D2l Brightspace records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed BigQuery and D2l Brightspace connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom BigQuery–D2l Brightspace integration in-house.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 439 integrations available for BigQuery and D2l Brightspace.