Install Idukki on BigCommerce

Status

Requirements

• A BigCommerce store on a Stencil theme (checked against Cornerstone conventions).
• Store owner access to install apps and to create a store-level API account.
• Your Business ID and a default gallery ID from the Idukki embed code.

Install

Open the install link we send you and approve the app. It asks for one scope, Content: modify, which it uses to add the storefront script and the widget template. On install it adds the Idukki UGC loader script (footer, storefront, consent category analytics) and the Idukki UGC gallery widget template.

Connect

• Open the app from Apps, My Apps. Paste the Business ID and a default gallery ID and Save; the widget template refreshes with your Business ID.
• For orders and catalogue, open the BigCommerce tab in the Idukki dashboard (Settings, Integrations) and enter the store hash and a BigCommerce API account token with Orders read-only and Products read-only (Settings, API, Store-level API accounts). Idukki registers its order webhooks. Catalogue sync from the same account is being finished; until then, import the catalogue under Products, Import.

Optional: a store connection key. In the Idukki dashboard open Settings, then the BigCommerce tab under Integrations, and create a key in the Store connection card. Early-access accounts have the tab switched on for them. On BigCommerce the key is used only by the app’s Test connection; it is stored sealed and shown only as a masked prefix.

Place galleries

In Storefront, My Themes, Customize (Page Builder), drag Idukki UGC gallery from Custom widgets onto any page or the product page template, set the gallery ID and publish. On product pages the widget filters to the product being viewed by default, or pick a product to always show.

<div data-ugc="idukki" data-bguid="<store bguid>" data-guid="..." data-platform="bigcommerce" filter-pid="<product id>"></div>

The footer script injects the async loader only on pages that contain an Idukki mount, so hand-pasted embeds work too and pages without a gallery load nothing. Whether Page Builder passes the product into the widget template is not yet verified, so the script also reads the product id from the product page itself; on a theme that differs, use the product picker.

Cookie consent

The script is registered under BigCommerce’s analytics consent category by default (switch it to functional in the app). With BigCommerce’s cookie banner on, it runs only after the shopper consents to that category. The gallery sets a visitor id and sends analytics, which is why analytics is the default.

What data is sent

How orders are matched to widget activity

A BigCommerce order has no field that can carry the widget visitor id. Idukki matches it through the order’s cart id and customer id instead, which works only when the widget has recorded those ids. The widget’s BigCommerce add-to-cart records them when a shopper adds to cart from the gallery; that piece is built and arrives with early access. Until it is on for your store, BigCommerce orders are recorded in Idukki but not matched to gallery activity.

Idukki matches each order to widget activity through the visitor id first, then the customer id and the cart id. An order counts as proven only when the same visitor added a product they bought to the cart from the widget beforehand. Orders that only followed a widget view or click land in the influence tiers, and the rest are store orders. The dashboard keeps proven, influenced and store orders in separate columns and never adds them together.

Troubleshooting

Uninstall

For a clean removal, remove placed widgets in Page Builder, click Remove storefront placement, then uninstall. BigCommerce removes the script on uninstall; the app tries to delete the widget template and deletes its store record. Disconnect the API account in the Idukki dashboard and revoke any connection key.