Skip to main content
When a shopper watches a shoppable video widget, Videowise sets the reeview_uid cookie (14 days). The order tracking pixel reads that cookie at checkout and sends it as uid, so the order is attributed to the widget session. You install one storefront pixel. The same pixel also attributes live shopping via reeview_lsid — see Live shopping order tracking. This page covers what is specific to widgets.

​
How attribution works

  1. The shopper interacts with a widget (stories, carousel, grid, floating, and similar).
  2. Videowise writes reeview_uid. Campaign and experiment cookies may also be set (reeview_campaign from videowise_campaign_id in the URL, REEVIEW_SESSION). See Cookies.
  3. On order confirmation, the pixel includes uid (and campaign / experiment / referral values when present) in the tracking request.
The pixel snippets already send uid. Shopify, Magento, SFCC, and custom/GTM installs all read reeview_uid. On React Native, persist and send the same ID with getStoredData (uid) and trackingPixel.

​
Install the pixel

Follow the platform guide in Order tracking pixel. Install once per storefront.

Shopify

Customer events pixel. Sends uid from reeview_uid.

Magento

Included on the default thank-you page.

Salesforce Commerce Cloud

Included on the default order confirmation page.

Other / GTM

Custom snippet. Passes uid on the order payload.