Skip to main content

Install the Tie Pixel yourself (headless, WooCommerce, and custom sites)

We're on WooCommerce / headless Shopify / a custom storefront. How do we install the Tie Pixel?

T
Written by Tim Hughes

This guide is for WooCommerce and other custom storefronts. If your store is headless Shopify (Hydrogen, Oxygen, or another storefront app on a Shopify backend), use Install the Tie Pixel on headless Shopify instead, because checkout on those stores still runs on Shopify and the install is different. Your developer adds a small Tie script to every page and implements the Tie data layer. It is a scoped development task.

Do this once your DNS is verified. Tie sends your loader script as soon as verification passes; it cannot be generated before then.

Step 1: Add the Tie Pixel loader to every page

  1. Tie sends you a custom loader script. Add it to your site's version control and place it in the <head> section of every page on your site, not just product or checkout pages.

  2. On WooCommerce this usually lives in your theme's header template or a header-scripts plugin so it loads site-wide.

  3. Once it is installed, you should see network calls to your Tie tracking subdomain (zone.yourdomain.com) on page load.

Paste the loader exactly as sent. It is a single minified line; reformatting or re-wrapping it will break it.

Step 2: Implement the Tie data layer

Your site pushes four ecommerce events to window.dataLayer so Tie can capture the funnel:

  • rr_view_item: product detail view

  • rr_add_to_cart: product added to cart

  • rr_begin_checkout: checkout started

  • rr_purchase: order confirmation / thank-you page

Each event uses a two-push pattern: first reset ecommerce to null, then push the event with its ecommerce object. The full field-by-field spec and sample code are in the Tie data layer reference.

Tie cannot build the data layer for you, because it runs directly on your site and must stay under your control. Your developer or a certified Tie agency partner implements it, and Tie validates the schema with you once it is live.

Step 3: Configure consent (if you use a consent banner)

If you run a consent management platform (OneTrust, Termly, or similar), configure it so the Tie scripts load only after the visitor grants marketing or analytics consent. Tie's tracker should not fire before consent is returned.

Step 4: Verify

Run the three checks in Verify your Tie installation: the loader returns 200, the four events appear in the data layer, and enrichment responds. Then tell your Tie contact, and we validate everything end to end with you.

Did this answer your question?