BigCommerce Integration

Connect Bloomreach Engagement with your BigCommerce store, analyze BigCommerce data, execute omnichannel marketing campaigns, and use Bloomreach Engagement’s AI-driven capabilities on your BigCommerce store.

Integration saves costs on integration projects and radically speeds up the time needed to integrate. Without our new native integration with BigCommerce, you would need to develop your own solution - invest into a system integrator partner, agency, or in-house development.

Installation guide

  1. Go to Bloomreach Engagement App > Integrations > add BigCommerce integration
  2. Copy Integration URL
  3. Go to BigCommerce Marketplace and search for Bloomreach app
  4. Install Bloomreach app
  5. Go to Bloomreach app
  • Engagement settings and paste Integration URL
  • Activate integration
  • Activate storefront data layer tracking
  1. Go to Bloomreach Engagement app > Tag Manager
  • create and customize Data Layer helper tag from templates to track frontend tracking or use Google Tag Manager

After integration setup, Bloomreach Engagement downloads all historical data (data up to that point), and subsequently tracks new data (changes, additions, etc.) from the BigCommerce API. The app also exposes identification and other useful data in data layer (works on the default storefront Stencil theme).

Integration specifications

Initial data load

  • customer base (customer and attributes)
  • subscriber base (email, consents)
  • orders and line items (created orders)
  • product catalogs (products and variants)

Events loaded from BigCommerce

  • purchase
  • purchase_item
  • consent

Customer attributes loaded from BigCommerce

  • personal information

Near real-time webhooks (2 minutes)

Exponea subscribes and listens for webhooks from BigCommerce API:

  • customer updates (create, update, delete)
  • new orders (order placed)
  • cart updates
  • consents changes (subscriber create, delete)

Web tracking

  • datalayer is populated with
  • identification (email_id, customer_id)
  • view_item event data

Required project identifiers setup:

  • email_id - Hard ID, lowercase, trim; email address is the primary identifier for customers in Bloomreach Engagement. If there are multiple BigCommerce customers/subscribers/guest orders with the same email address, there is one customer for Bloomreach Engagement.
  • customer_id - Hard ID - numeric BigCommerce Customer identifier
  • subscriber_id - Hard ID - numeric BigCommerce Subscriber identifier
  • cookie - Soft ID - device unique cookie identifier (i) standard cookie identifier that is used in web tracking

See tracking document for details on data structure.

BETA Limitations

BigCommerce integration is enabled on shared instances by default. For other instances, please ask the support team for activation.

JS SDK must be added manually by editing the theme files or Google Tag Manager. Actual tracking can be added manually be Data Layer helper Tag Manager.

Customer anonymization must be done manually in the Bloomreach Engagement app. BigCommerce does not have a concept of anonymization to comply with CCPA/GDPR. BigCommerce admins are advised to delete private field values in the BigCommerce Admin UI when such a request comes. The integration will transfer these private customer attributes' empty values to Bloomreach Engagement customer properties, however Customers on the Bloomreach Engagement side will not be anonymized as per Bloomreach Engagement rules. Anonymization triggers when a customer is deleted on the BigCommerce side. Anonymization can be always triggered manually for a specific customer in the Exponea app Customer UI. BigCommerce admins can read more on Implementing CCPA with BigCommerce - Deleting Personal Information.

Guest orders are tracked as purchase events into a customer profile identified by email address. These are not automatically anonymized at any point and you can set up an automated scenario to anonymize, or anonymize these guest customers manually.

When BigCommerce admin deletes ALL subscribers manually, it will not revoke consents on the Bloomreach Engagement side in their customer profiles. As far as we know, this is a design decision on the BigCommerce side: BigCommerce is not sending a webhook about full subscriber list deletion. Workaround is a manual revocation of all consents on the Bloomreach Engagement side.

Anonymization scenario is not part of the integration and shall be created by hand: Repeat daily => Condition: subscriber_id has value AND customer_id has no value AND customer bigcommerce consent is not valid AND last bigcommerce consent timestamp is older than X days => anonymize customer

The integration does not have customizable backend tracking, this means that only customer attributes and events in the Tracking document are available.

Multiple stores in one project are not supported. BigCommerce customer ID is not unique and since the customer_id is a Hard ID, importing from multiple BigCommerce stores would cause customer collisions.