The name is historical: early pixels were one-pixel images loaded from a server so the server could log the visit. Today’s pixel is a script. Meta describes its Pixel as a snippet of JavaScript code that lets a site track visitor activity; when a visitor takes an action, called an event, the Pixel can report it as a conversion that advertisers use to measure ads, build audiences and study funnels (Meta).
For commission UGC the pixel is what connects a creator’s link to a purchase. The link brings the visitor; the pixel sees the order; the attribution rule decides whether the link gets credit.
Example. A creator’s link lands a visitor on a product page. The pixel records a page view, then an add-to-cart, then a purchase of $64 five days later. With a 7-day click window the purchase is attributed to the creator’s link, and at 15 % the creator is credited $9.60. Without the pixel the store would see an order and no history. Example numbers.
When brands use it. The pain this answers: “I have no idea which creator actually drove sales.” Every store that runs ads has a pixel. Brands paying creators on tracked sales rely on it, or on a dedicated attribution pixel, to see which link or code preceded which order. Browser privacy settings and in-app browsers lose some of this, which is why brands pair pixels with a server-side connection and with codes.
The creator’s view. A pixel is invisible to the creator, so the question is whether the brand’s tracking survives the path a viewer actually takes: from a TikTok in-app browser, to a product page, to a purchase three days later on a laptop. Codes are the fallback when it does not.
On HourlyUGC. When HourlyUGC counts sales itself, it reads them from a connected Shopify store or its own pixel, with creator links and codes, last touch within 7 days.