Docs/Integrations/BigCommerce
🛒

BigCommerce Integration

Beta

Script Manager snippet + customer sync

The RocketShield storefront script checks email fields on checkout, account and contact pages in real time and blocks bad addresses before submit. The customer sync verifies existing and new customers and writes the result into customer attributes.

No BigCommerce App Marketplace app is needed or listed. The storefront script is pasted into Script Manager, and the customer sync connects with a store API account from the RocketVerifier dashboard.

Add RocketShield with Script Manager

1

Create a shield

In the RocketVerifier dashboard open RocketShield and create a shield. Choose the blocking rules and message there; the widget loads them from the shield. Add the store's domains to Allowed domains: the custom domain and store-xxxx.mybigcommerce.com, plus the checkout domain if it is different. Copy the public rs_... key.

2

Create the script

BigCommerce: Storefront → Script Manager → Create a Script. Name RocketShield, placement Footer, location All pages (the snippet narrows this itself; "All pages" includes checkout), script type Script, category Essential. With the cookie consent banner on, "Functional" scripts wait for consent and the forms would be unprotected until then; mention the script in your privacy policy.

3

Paste the snippet and your key

Replace rs_REPLACE_WITH_YOUR_SHIELD_KEY. Until it is replaced (or if it is malformed), the snippet does nothing.

4

Test

Test on the storefront with a sandbox shield and @sandbox.rocketverifier.com addresses, or a few known-bad addresses.

Script Manager snippet
<script>
(function () {
  var SHIELD_KEY = 'rs_REPLACE_WITH_YOUR_SHIELD_KEY';
  // 'forms': checkout, account creation/login and contact pages only.
  // 'all':   every page (also protects footer newsletter forms).
  var PAGES = 'forms';
  var WIDGET_URL = 'https://app.rocketverifier.com/widget/v2.js';

  if (!/^rs_[A-Za-z0-9_-]+$/.test(SHIELD_KEY) || SHIELD_KEY.indexOf('REPLACE') !== -1) return;
  if (window.__rocketShieldLoaded) return;

  var path = (window.location.pathname || '/').toLowerCase();
  var isCheckout = /^\/(embedded-)?checkout(\/|$|\.php)/.test(path) || path === '/finishorder.php';
  // /login.php also serves ?action=create_account (registration).
  var isAccount = path === '/login.php' || path === '/account.php';
  var isContact = /^\/contact(-us)?(\/|$)/.test(path);
  if (PAGES !== 'all' && !(isCheckout || isAccount || isContact)) return;

  window.__rocketShieldLoaded = true;
  var existing = window.rocketShieldConfig || {};
  var config = {};
  for (var k in existing) {
    if (Object.prototype.hasOwnProperty.call(existing, k)) config[k] = existing[k];
  }
  config.apikey = SHIELD_KEY;
  config.platform = 'bigcommerce';
  window.rocketShieldConfig = config;

  var s = document.createElement('script');
  s.src = WIDGET_URL;
  s.async = true;
  s.setAttribute('data-shield-key', SHIELD_KEY);
  s.setAttribute('data-platform', 'bigcommerce');
  (document.head || document.body).appendChild(s);
})();
</script>

With PAGES = 'forms' the snippet runs on /checkout, /embedded-checkout, /finishorder.php, /login.php (login and account creation), /account.php and /contact-us.

  • Checkout: Script Manager scripts run on checkout only with Optimized One-Page Checkout. Inline feedback works; test whether blocking stops the React "Continue" step on your store. The customer sync still flags any address that gets through.
  • Headless / Catalyst storefronts do not use Script Manager: add the two-line RocketShield embed (see Webflow) to the storefront layout instead.

BigCommerce Connector

Beta

Verifies BigCommerce customers through the Management API with a store API account (store hash + access token).

Connect with

API key

Category

Ecommerce

Write-back

Fields

Auto-verify new

Yes

How to Connect

1

In BigCommerce create a store API account (Settings → Store-level API accounts) with the Customers: modify scope.

2

In RocketVerifier open Dashboard → Integrations → BigCommerce, paste the credentials below (the access token and store hash) and click Connect. They are validated against the platform before anything is saved.

3

Pick the source to sync, the schedule and the write-back options in the integration settings, then click Sync now or wait for the schedule.

FieldRequiredWhere to find it
API keyRequiredThe API account's access token.
Store hashRequiredThe stores/<hash> part of the API path shown with the API account.

Credentials are stored encrypted and are only ever sent to the platform's own API hosts.

What It Syncs

Sources

All customers or any customer group.

Incremental syncs

Customers modified since the last sync.

Schedules & Credits

  • Schedule: Manual only, Daily, Weekly or Monthly. Each run syncs the source chosen in the settings; Sync now starts one immediately. Only one sync runs per integration at a time.
  • Mode: Full re-checks every contact in the source except those verified in the last N days (default 30, 0-365); Incremental only checks contacts changed since the last sync.
  • Each sync creates a regular verification job: 1 credit per unique address, and unknown results are refunded when it completes. If the balance is too low the sync stops with insufficient_credits before anything is charged.
  • Results are written back when the job completes; the sync history in the dashboard shows updated, failed and skipped counts per run.

Write-back

Fields ("Write status fields")

  • rv_email_status
  • rv_email_sub_status
  • rv_email_score
  • rv_verified_at

Customer attributes, created on first use.

Status values are deliverable, undeliverable, risky and unknown (disposable addresses are undeliverable, catch-all addresses unknown). Sub-status is a sub_status value (none when there is no extra detail), score is 0-100 and verified-at is an ISO 8601 UTC timestamp.

Auto-verify New Contacts

Turn on Auto-verify new contacts. RocketVerifier registers a store/customer/created webhook to https://api.rocketverifier.com/webhooks/connectors/bigcommerce/{integration_id}. BigCommerce does not sign webhooks, so a random token is sent in an X-RV-Webhook-Token header and checked on every delivery, and the customer is re-read from the API before it is verified.

Every new contact costs 1 credit. Addresses this integration verified in the last 30 days are skipped, and webhook events are de-duplicated for 24 hours, so platform retries never charge twice.

Beta: the BigCommerce connector is new. Sync reports list every contact that could not be updated; please tell us if something looks wrong.

Need Help?

Having trouble setting up BigCommerce? We're here to help.