Skip to main content

​
What the Pixel does

When installed on your site, the Pixel performs three main functions:
  • UTM Capture: Records UTM parameters present in the URL (such as utm_source, utm_medium, utm_campaign, among others), which indicate where the user came from and which campaign brought them to the site.
  • Data persistence across pages: With the support of an additional script, the Pixel ensures that this source data is not lost during navigation between pages until the moment of conversion.
  • User identification with Fingerprinting: We use a probabilistic identification technique called Fingerprinting. It combines variables like IP, browser, operating system, language, and other public data to generate a unique and anonymous identifier for each visitor, even without login or cookies.

​
Why the Pixel is important

  1. UTM Data Quality
    Without Nemu Pixel, traffic source data can be lost or recorded incompletely, compromising results analysis. The Pixel ensures that UTMs are correctly captured and preserved during user navigation, resulting in more reliable data.
  2. Journey Building
    With data captured by the Pixel and the identifier generated via Fingerprinting, we can trace a precise timeline of interactions the user had with campaigns and channels before making a purchase. This is fundamental for behavior analysis and understanding the role of each channel in the journey.
  3. Attribution Models
    Based on collected data, Nemu applies attribution models like First Click, Last Click, and other custom models. This allows evaluating which campaign attracted the customer and which contributed to the final conversion, giving a more strategic view of marketing performance.

​
How Fingerprinting works in practice

Our system collects variables such as:
  • IP address (anonymized hash)
  • Browser and version
  • Operating system
  • Browser language
  • Screen resolution
  • Time zone
This information is combined in an encrypted way and transformed into a unique identifier called clientId. This identifier is used to unite all interactions of the same visitor, even across different visits and without the need for traditional cookies.

​
Additional behaviors

Nemu Pixel may have specific behaviors depending on the e-commerce platform used. Here are the main ones:

​
VTEX Store

During the checkout process, Pixel waits for the generation of the VTEX order identifier (called orderFormId). This process is completely safe and read-only mode. ✅ Read operation: the script just “observes” the orderFormId, without interfering with VTEX’s operation. ⚙️ Optional function (Currently disabled): there is a write function to fill UTMs in VTEX’s marketingData, but it is disabled by default, ensuring maximum security. 🔒 As soon as the orderFormId is detected, it is associated with the visitor session to correctly link the order to the source campaign.

​
Nuvemshop

Pixel uses the Nuvemshop cart identifier (window.LS.cart.id) to track the visitor session. 🛒 Cart identification: the script automatically collects the Nuvemshop cart ID to associate the order with the visit source. 📊 Complete tracking: allows linking each conversion to the campaign that brought the user to the store.

​
Tray

Uses HTML attributes data-session or data-checkout-session_id to identify the checkout session. 🔗 Checkout session: Pixel automatically collects the Tray checkout session ID. 💾 Persistence: data is maintained throughout the entire purchase process.

​
Shopify

Waits for the cart token generation to track the order. ⏳ Cart monitoring: script waits up to 50 seconds to detect the cart token. 🍪 Cookies and LocalStorage: uses cookies and localStorage to ensure data is not lost. 🔄 Automatic update: when detected, the cart ID is automatically updated in the tracking session.

​
WooCommerce

Uses the order key extracted from the URL during checkout. 🔑 Order key: script detects the key parameter in the checkout URL (/efetuar-pagamento) to track the order. 📦 Specific cookies: stores custom cookies (nemu_source, nemu_medium, etc.) with a 30-day validity for continuous tracking.

​
Bagy

Stores UTMs in JSON format within specific cookies for integration with the Bagy system. 🍪 Specialized cookie: data is stored in cookies with specific domain and 30-day validity. 📊 Complete metadata: captures all UTM parameters for detailed campaign analysis.

​
Magazord

Encrypts UTM data in base64 in a reversible way for secure integration. 🔐 Security: data is encoded and reversed for additional protection. 🛡️ Integration: uses the trk cookie to store data securely.

​
VNDA

Monitors the session through the platform’s ahoy_visit cookie. ⏱️ Session waiting: script monitors for up to 10 seconds for session generation. 📝 Campaign metadata: stores campaign information for later analysis.

​
Wake

Integrates directly with Wake’s checkout API to add metadata. 🔄 Checkout API: uses client.checkout.addCheckoutMetadata() to store UTMs. ⏳ Monitoring: waits up to 10 seconds to detect API availability. 📊 Complete metadata: stores all UTMs (utmSource, utmCampaign, utmMedium, etc.) in checkout.

​
Uappi

Uses the Uappi platform order identifier for tracking. 🆔 Order ID: collects WapStore.pedido.id for correct order association. 🔗 Linking: ensures each conversion is correctly attributed to the source campaign.

​
Shoppub

Monitors the customer ID in the store through the Shoppub global variable. 👤 Customer ID: uses window.Shoppub.customer.id_on_store for identification. ⏰ Continuous monitoring: checks every 500ms until customer ID is detected.

​
JetCommerce

Waits for customer email detection on the checkout page. 📧 Email as identifier: monitors the email field to obtain customer identification. ⏳ Extended timeout: waits up to 5 minutes to ensure data collection. 🔄 Automatic update: once detected, the email is used as session identifier.

​
How to install the Pixel

Pixel installation is simple and can be done in minutes. To see the complete step-by-step guide, visit: Nemu Pixel installation guide