Run controlled A/B tests on Bigcommerce with Optimizely to improve conversion rate, validate UX changes, and roll out winning experiences with reliable tracking.
• Optimizely Web and Feature Experimentation tags are served on Bigcommerce storefront pages, and variation decisions are resolved per visitor and persisted via cookies or local storage.
• Bigcommerce product, category, and page identifiers are mapped to Optimizely attributes to keep experiment audiences and reports aligned with the catalog structure.
• Commerce events such as product view, add to cart, begin checkout, and purchase are emitted from the storefront and forwarded to Optimizely as custom events for conversion tracking.
• Order confirmation data from Bigcommerce (order ID, revenue, currency, and line items when available) is normalized and passed to Optimizely to support revenue-based goals.
• Visitor identifiers are stitched across sessions where possible using first-party IDs, and mismatched or missing IDs are handled with fallbacks and event deduplication.
• Event payloads are validated and logged, and failed deliveries are retried or routed to monitoring to reduce silent gaps in Optimizely experiment data.
.png)
We map Bigcommerce events (view, add to cart, checkout steps, purchase) into Optimizely and QA them against your order records so test results reflect real revenue.
Yes, with a clean data layer and event payloads, you can build audiences and targeting rules based on catalog, cart, and customer signals from Bigcommerce.
We limit experiments to approved templates, add guardrails for edge cases, and use staged rollouts with monitoring so critical checkout logic stays intact.
It can, as long as store, locale, currency, and channel identifiers are passed consistently for segmentation and reporting inside Optimizely.
scandiweb’s analytics team has delivered 575+ eCommerce BI dashboards and works with GA4 and tagging setups that keep experimentation data trustworthy.










