Skip to content
E-commerce ⇄ Data warehouse

Akeneo to BigQuery integration — real-time, two-way sync

Keep Akeneo and BigQuery in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Akeneo and BigQuery

Make BigQuery the analytics and enrichment layer behind Akeneo: orders, products, and customers stay current in both directions.

BigQuery is the analytical store where the business joins, models, and reports on its data; Akeneo runs the storefront, catalog, and transactions that generate most of it. The overlap is every record that has to be counted and enriched on one side and acted on the other — and when the bridge is a nightly export, the warehouse reports on yesterday while the store operates without the segments and metrics the warehouse just computed.

Stacksync syncs Datasets, Projects, Tables, Partitioned tables in BigQuery with Assets, Channels and locales, Media files, Products in Akeneo field by field, in real time, and in both directions. Transactional records land in the warehouse as they change, computed attributes and cleaned catalog data flow back to the store, and you decide which system owns which fields so Stacksync resolves conflicts by rules you set.

Common use cases

  • 01 Maintain a customer master table in BigQuery joined across CRM, billing, and support sources
  • 02 Feed ML feature tables in BigQuery from operational systems on a continuous schedule
  • 03 Read Reference entities records such as brands and manufacturers into a data warehouse for cross-catalog reporting.
  • 04 Mirror Products and completeness data into a warehouse to track enrichment progress by channel and locale without manual CSV exports.

Common sync patterns

Live analytics on store activity

Orders, products, and customer records from Akeneo land in BigQuery as they change, so dashboards and models read current data instead of last night's export.

Where Akeneo accepts writes: push computed attributes back

Segments, lifetime value, and scores built in BigQuery write onto the matching records in Akeneo, so merchandising and messaging act on warehouse logic.

One product catalog

Where both systems hold product or catalog data, cleaned and enriched attributes stay aligned so the store and the warehouse describe the same items.

What you can sync between Akeneo and BigQuery

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.

Akeneo objects BigQuery objects How this pairing syncs
Media files Product images and files uploaded via the media endpoint; referenced by products and pushed to downstream commerce and content systems. Clustered tables Supported; clustering is transparent to the sync. Media files is specific to Akeneo and Clustered tables to BigQuery — each maps to any object or custom field on the other side.
Products Core catalog records addressed by UUID (recommended) or identifier/SKU; synced two-way with databases, ERPs, and storefronts. Values are scoped per channel and locale. Datasets Organizational container — you pick which dataset’s tables to sync. Products is specific to Akeneo and Datasets to BigQuery — each maps to any object or custom field on the other side.
Product models Parent records for configurable products; hold shared attribute values that cascade to their variant products, synced alongside Products. Projects Connection scope: the service account grants access per project. Product models is specific to Akeneo and Projects to BigQuery — each maps to any object or custom field on the other side.
Categories The category tree used to classify products; read out for storefront navigation or written in from an ERP to seed catalog structure. Tables The syncable unit: only tables can be synced per the Stacksync docs. Categories is specific to Akeneo and Tables to BigQuery — each maps to any object or custom field on the other side.
Attributes Attribute definitions plus attribute options and groups; describe the shape of product data, usually mastered in Akeneo and read downstream. Partitioned tables Synced like regular tables; partition columns map to target fields. Attributes is specific to Akeneo and Partitioned tables to BigQuery — each maps to any object or custom field on the other side.

How changes propagate between Akeneo and BigQuery

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.

Akeneo BigQuery Sub-second propagation

DetectionAkeneo notifies Stacksync of record changes through webhook events. Events API webhooks (product.created, product.updated, product.deleted, plus product-model equivalents.

DeliveryEach detected change is applied to BigQuery as a row-level write, with types converted between the two schemas.

BigQuery Akeneo Sub-second propagation

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 Akeneo through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Akeneo: REST protection triggers above roughly 100 requests/second per PIM instance (HTTP 429 with Retry-After); the Events API caps at 4000 requests/hour with a 500ms webhook ack timeout.
  • BigQuery: Subject to Google Cloud quotas on queries, DML, and streaming; DML is supported but the platform favors append-heavy batch and streaming loads over row-at-a-time writes.
What ships with Akeneo ⇄ BigQuery

Connect Akeneo and BigQuery for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Akeneo–BigQuery connection.

Real-time

Two-way sync

Changes in Akeneo or BigQuery instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Akeneo or BigQuery data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Akeneo or BigQuery record.

Observability

Monitoring

Track your Akeneo ⇄ BigQuery sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Akeneo and BigQuery.

How the Akeneo and BigQuery connectors work

Akeneo

Integration surface
REST API (plus a GraphQL API) and an Events API for webhooks
Authentication
OAuth2 password grant: client_id/secret plus an API user's username/password exchanged at /api/oauth/v1/token for a bearer access_token and refresh_token; Apps use the OAuth2 authorization-code flow
Change detection
Events API webhooks (product.created, product.updated, product.deleted, plus product-model equivalents; product.updated.delta carries old and new values); falls back to polling the 'updated' datetime search filter where the Events API is unavailable
Capabilities
read · write · webhooks
Rate limits
REST protection triggers above roughly 100 requests/second per PIM instance (HTTP 429 with Retry-After); the Events API caps at 4000 requests/hour with a 500ms webhook ack timeout.

BigQuery

Integration surface
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
Change detection
Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen") with a Cloud Run "secure portal for real-time notification service in
Capabilities
read · write · CDC
Rate limits
Subject to Google Cloud quotas on queries, DML, and streaming; DML is supported but the platform favors append-heavy batch and streaming loads over row-at-a-time writes
BigQuery setup guide
How it works

How to connect Akeneo to BigQuery — three steps, no code

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.

  1. 01

    Connect your apps

    Authenticate Akeneo and BigQuery with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Akeneo connected
    BigQuery connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Akeneo and BigQuery 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Akeneo ⇄ BigQuery
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Akeneo BigQuery
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Akeneo and BigQuery integration FAQ

SECURITY

Security teams trust Stacksync

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.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 500 integrations available for Akeneo and BigQuery.

Popular · 8 of 500
All Akeneo integrations All BigQuery integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own