The browse pixel is what powers the Product browsed, not bought and Cart abandoned automation triggers: it tells IcloneU when an identified customer viewed a product or filled a cart and then walked away, so your recovery workflows can follow up on WhatsApp. It only ever reports identified visitors — people who arrived from a store link that identifies them (the product and checkout links your Clone sends, or the product, cart and checkout links a store event hands to a flow), who are logged into their store account, or who signed up through one of your capture forms or, with the optional Klaviyo forms bridge, a Klaviyo sign-up form. Anonymous browsing is never recorded.
You need a connected Shopify store first — see Connecting your Shopify store. If the Browse tracking pixel section doesn't appear in your connection settings, browse tracking isn't enabled for your environment yet — contact support.
Step 1 — Copy your pixel snippet
Open your Shopify connection
In IcloneU go to Automations → Connectors, select your Shopify connection and click Settings.
Copy the snippet
Scroll to the Browse tracking pixel card and click Copy. The snippet is unique to your store — it carries your connection's ingest token, so never reuse a snippet from a different store or environment.
Step 2 — Add it as a custom pixel in Shopify
Open Customer events
In your Shopify Admin go to Settings → Customer events.
Add a custom pixel
Click Add custom pixel, name it IcloneU, and confirm.
Paste and connect
Paste the snippet into the code box, click Save, then click Connect so the pixel status shows Connected.
This is a paste-once install: the snippet only holds your store's configuration and loads the actual tracking logic from your IcloneU server, so improvements reach your store automatically — you won't be asked to re-paste when IcloneU updates.
Step 3 — Verify it works
Browse as an identified visitor
From a WhatsApp or web-chat conversation with your clone, tap any product or checkout link it sent you, then browse a product page for at least 10 seconds without buying. Logging into a customer account on the store identifies you too.
Watch the trigger fire
About 2 hours after your last product view (every further view restarts the wait, even a quick one), or 1 hour after your last cart change — fixed platform defaults — your Live automation fires and the connection's Recent events list shows the event. Test with a contact that has not paid for an order in the last 24 hours: paying closes any cart or browsing still waiting, and a recent buyer gets no browse or cart event (and none, for 14 days, for a product they bought). For the cart, add a product the contact has never put in the cart: a variant that was already in their cart before an order, or was first added in the 24 hours after it, stays quiet when it's added again, for at least 30 days.
What gets tracked — and what doesn't
Browsing is only ever reported for identified sessions: a visitor whose browser once opened a store link that identifies them (the product and checkout links your Clone sends, or the product, cart and checkout links a store event hands to a flow, not a link you type into a message yourself), one logged into their store account (verified against Shopify before it counts), or one who signs up through one of your capture forms or, with the optional Klaviyo forms bridge installed, a Klaviyo sign-up form. That sign-up sends the phone or email the visitor typed, and IcloneU matches it to a contact or creates one. Very brief views — under about 10 seconds — never fire an event on their own and are left out of it, though they still count as activity and push the 2 hours back. The pixel honors your store's cookie-consent banner: if a visitor declined marketing or analytics, nothing is reported for them.
The WhatsApp button snippet from the same connection settings is a separate install — it goes into your theme (Online Store → Themes → Edit code → theme.liquid, before </body>), not into Customer events. The same settings also carry two optional theme snippets, each with its own instructions: the Klaviyo forms bridge, for stores that use Klaviyo sign-up forms, and Capture forms for your store, which shows the popups you build in the Capture tab — see Capture links and QR codes.
Last updated September 23, 2026 · Platform Integrations
