Guide: Using BigCommerce with Databox (Third-Party Integration)

Currently, there is not a direct Databox + BigCommerce integration available, but there are alternative ways to sync your BigCommerce data with Databox.

These alternatives utilize third-party integrations such as Zapier, or the Databox API.

Pro Tip: If you don't have the time or resources to set this up yourself, check out our services where we can build the custom integration for you. For additional information, feel free to connect with our team via chat or email us at


How to use Zapier to sync BigCommerce data

Zapier is a trigger-based app, meaning you can have certain events (such as a new card being added) trigger certain actions (updating the relevant data and syncing with Databox) using Zaps. Because triggers initiate data syncs, historical data will not be available for metrics that are synced using Zapier. 

Learn more about the Zapier + Databox third-party integration here.

Whenever possible, it’s recommended that you use a Zap Template. This will save you time and will streamline the process of syncing BigCommerce data with Databox using Zapier. 

You can also create Zaps from scratch if a Zap Template isn’t available.


Zap Templates available for BigCommerce Metrics

View the full list of prepared Zaps here.

Creating Zaps from scratch for BigCommerce Metrics

The following BigCommerce Metrics can also be synced with Databox by creating a Zap from scratch: 

  • New Order
    (triggered when a new order is placed)
  • New Customer
    (triggered when a new customer is added)

Learn how to create Zaps from scratch here.

Use the Databox API to sync BigCommerce data

If you’re comfortable using scripting languages or you have developer resources available, you can build your own custom integration and push BigCommerce data via the Databox API.

For more information, check out the Databox developer portal or BigCommerce’s API documentation.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.