Pixel Tracking

Convultra provides a server-side tracking pixel as a no-JavaScript fallback. When the SDK cannot load -- because JavaScript is disabled, blocked by an extension, or fails to execute -- the pixel ensures basic visitor tracking still occurs.

How it works

The tracking pixel is a 1x1 transparent image served by the Convultra API. When the browser requests the image, the server records the pageview along with available request metadata.

<!-- No-JS fallback pixel -->
<noscript>
  <img
    src="https://api.convultra.com/api/v1/pixel?key=YOUR_API_KEY"
    alt=""
    width="1"
    height="1"
    style="display:none"
  />
</noscript>

Replace YOUR_API_KEY with your project API key.

If you use a custom domain proxy, replace api.convultra.com with your custom tracking domain (e.g. track.yourdomain.com).

What the pixel captures

The pixel request provides the server with:

IP address -- used for geolocation (country, region, city)
User-Agent -- used for device, browser, and OS detection
Referer header -- the page URL where the pixel was loaded
Click IDs -- if present in the page URL and passed as query parameters to the pixel endpoint
Timestamp -- server-side request time

Limitations

The tracking pixel is a fallback mechanism and has significant limitations compared to the full SDK:

Capability	SDK	Pixel
Pageview tracking	Yes	Yes
Click ID capture	Automatic	Manual (must pass in URL)
Conversion tracking	Yes (all event types)	No
Enhanced conversions	Yes	No
E-commerce events	Yes	No
UTM parameters	Automatic	Manual (must pass in URL)
Session tracking	Yes	Limited
Device/browser data	Full	User-Agent only

⚠️

Pixel tracking provides basic pageview tracking only. It cannot track client-side conversion events such as purchases, leads, or signups. For full tracking, use the JavaScript SDK.

When to use the pixel

Email campaigns -- embed the pixel in HTML emails to track opens
AMP pages -- where custom JavaScript is restricted
Environments with JavaScript disabled -- some enterprise firewalls or kiosk setups
Universal fallback -- add the <noscript> pixel alongside the SDK to cover 100% of visitors

Setup

The pixel is available automatically for all projects. No configuration is required beyond adding the <img> tag to your page.

Automatic fallback

The recommended setup is to include both the SDK and the pixel:

<!-- SDK (primary) -->
<script>
window.Convultra=window.Convultra||(function(){
  var q=[];var c={q:q,initialized:false,config:{}};
  ['init','track','trackPurchase','trackLead','trackSignup','trackConversion',
   'trackAddToCart','trackViewContent','trackBeginCheckout','enhance',
   'setEnhancedUserData','identify','trackContact','trackSchedule',
   'trackDownload','trackSubscription','trackAddPaymentInfo',
   'trackAddToWishlist','trackSearch'].forEach(function(m){
    c[m]=function(){q.push({m:m,a:Array.prototype.slice.call(arguments,0),t:Date.now()});return c;};
  });
  return c;
})();
</script>
<script async src="https://cdn.convultra.com/ultra.min.js" data-convultra-key="YOUR_API_KEY"></script>
 
<!-- Pixel fallback (fires only if JS is disabled) -->
<noscript>
  <img
    src="https://api.convultra.com/api/v1/pixel?key=YOUR_API_KEY"
    alt=""
    width="1"
    height="1"
    style="display:none"
  />
</noscript>

This provides 100% visitor coverage: SDK-capable browsers get full tracking, and no-JS visitors get basic pageview tracking.

Requirements

The pixel endpoint (api.convultra.com/api/v1/pixel or your custom domain equivalent) must be accessible from the visitor's browser.
Image requests must not be blocked by a firewall, content security policy, or network filter.
If using a Content Security Policy (CSP), ensure img-src allows api.convultra.com (or your custom domain).

Deduplication Custom Domains