Install on BigCommerce

Add the Luria tag with Script Manager, then add a second script on the Order confirmation page so purchases are counted.

About 8 minutes

BigCommerce has a built-in place for third-party code, so you never touch theme files. You create two scripts: one for the whole storefront, one for the order confirmation page.

What you'll need

Your Luria tag, with your site ID already filled in. Luria gives you the tag during onboarding, or by email from hello@luriart.com. The dashboard does not show the site ID yet.
A BigCommerce user account with the Manage Scripts permission (store owner works)

Steps

Step 1: Add the storefront script

In your BigCommerce control panel go to Storefront → Script Manager → Create a Script.

Name of script: Luria
Location on page: Head
Select pages where script will be added: All pages
Script type: Script
Script contents: paste the tag below

<script async src="https://luriart.com/snippet.js" data-luria-site="YOUR_SITE_ID"></script>

Click Save. If your store shows a consent category field, pick the category your cookie banner allows for analytics, otherwise the script never runs for visitors who have not opted in.

Script Manager exists on Stencil themes. On an older Blueprint theme there is no Script Manager, so paste the tag into the theme's HTML head file instead.

Screenshot comingBigCommerce Script Manager Create a Script form with Location set to Head and Pages set to All pages

Step 2: Count the purchase on the order confirmation page

BigCommerce sends shoppers to its own order confirmation URL after checkout. That is not one of the paths Luria detects on its own (/thank-you, /thank_you, /orders/<id>), so add the call yourself.

Create a second script: Storefront → Script Manager → Create a Script.

Name of script: Luria conversion
Location on page: Footer
Select pages where script will be added: Order confirmation
Script type: Script

<script async src="https://luriart.com/snippet.js" data-luria-site="YOUR_SITE_ID"></script>
<script>
  (function go(n) {
    if (window.luria) return window.luria.convert("purchase");
    if (n < 50) setTimeout(function () { go(n + 1); }, 200);
  })(0);
</script>

The tag is in there twice on purpose. If your first script already covers the confirmation page, the snippet ignores the second copy, so there is no risk in leaving it. The loop waits for the snippet to finish loading, up to about ten seconds.

To send an order value, pass it as the second argument, for example window.luria.convert("purchase", 129.00), reading the total from your theme's confirmation template. Without a value the conversion still counts, it just carries no revenue.

Verify it worked

Open your storefront in a private window with ad blockers off. If you are in the EU, UK or Switzerland, Luria shows a small consent banner; click Accept, since nothing is tracked before you answer it.
View the page source. The tag is inside <head> with your site ID in it, not YOUR_SITE_ID.
In the browser's Network tab, look for a request to luriart.com/api/events. Events are batched, so give it a couple of seconds.
Place a test order and land on the confirmation page. On luriart.com/app, the Overview card "Conversions this period" goes up by one, and the Customers tab lists that session.

Luria dashboard Overview tab showing conversion rate, lift and conversions this period

Full checklist: Verify your install.

Common failures

Nothing tracked at all. The tag is missing its site ID or the ID has a typo. Without a valid data-luria-site the snippet stops immediately.
Script saved but not on the page. It was saved to the wrong page selection, or a consent category is holding it back until the shopper accepts. Check both fields in Script Manager.
Tracking works, orders do not count. The second script is on the wrong page selection, or the confirmation page never loads because the shopper closes the tab after paying. Only shoppers who land on the confirmation page are counted.
Counted twice. The convert call is in two scripts, or the shopper reloaded the confirmation page. Keep exactly one call. See Duplicates.
Nothing in the test browser. Global Privacy Control or Do Not Track is on, or you clicked Decline on the banner earlier. Luria collects nothing in both cases. Clear the site data and try again.
Blocked by your own site. A Content Security Policy that does not allow luriart.com stops the script. Add it to script-src and connect-src.