Documentation

Introduction

TrackRight is a server-side event tracking platform. Your website sends conversion events to your TrackRight container, and we deliver them to your marketing platforms (Meta, Google, TikTok, LinkedIn, Snapchat) over server-to-server connections that ad blockers and browser privacy restrictions cannot interfere with. Personal data is SHA-256 hashed, bots are filtered, and duplicates are removed automatically.

Installation

Pick the integration that matches your stack — every option feeds the same container and receivers.

1. 1

   Create a container

   App → Tracking → Containers → New container. Choose Proxy (Event Forwarding) unless you specifically need a full GTM server — you get an endpoint like /t/tr_abc123.

2. 2

   Add receivers

   App → Tracking → Receivers → New receiver. One receiver per destination platform, each with its own credentials (see Platform Config below).

3. 3

   Connect your website

   WordPress plugin, GTM DataLayer template, or direct API calls — guides for each are in the Integrations section.

4. 4

   Verify events arrive

   Watch App → Event Logs in real time, and use the free Event Tracking Tester before going live.

Domain Setup

Point a subdomain of your own website at TrackRight so tracking requests are first-party. Add this record at your DNS provider (e.g. Cloudflare):

• ✓ Survives ad blockers better — requests go to t.yourstore.com, not a known tracking domain.
• ✓ First-party cookies — attribution cookies can live up to 2 years instead of 7 days.
• ✓ Your brand everywhere — no third-party domains in your page requests.

Custom domains are activated per account after deployment — contact support to enable yours.

Platform Config

Each receiver needs credentials from its platform. Here's exactly where to find them:

WordPress / WooCommerce Plugin

The plugin tracks the full WooCommerce funnel automatically: PageView AddToCart InitiateCheckout Purchase — with billing email and phone attached for match quality (hashed on arrival) and click IDs stored in 30-day cookies so delayed purchases keep their attribution.

1. 1

   Install the plugin

   Download below, then WordPress admin → Plugins → Add New → Upload Plugin → Activate.

2. 2

   Configure settings

   Settings → TrackRight → paste your container endpoint URL (from Containers → Install code).

3. 3

   Choose purchase timing

   COD store? Keep "Delay Purchase until order completed" ON (default) — Purchase fires when you mark the order Completed, so cancellations never pollute your ads data. Card-only store? Turn it off to fire at checkout.

4. 4

   Publish & test

   Place a test order, then watch it arrive in App → Event Logs with per-platform delivery status.

GTM with DataLayer

For Laravel, PHP, or any custom site already using Google Tag Manager: push standard GA4 e-commerce events to the dataLayer and forward them to your container with a Custom HTML tag.

1 — Push events to the dataLayer

window.dataLayer = window.dataLayer || [];
dataLayer.push({ ecommerce: null });
dataLayer.push({
  event: 'purchase',
  ecommerce: {
    transaction_id: 'T-1001',
    value: 2450,
    currency: 'BDT',
    items: [{ item_id: 'SKU-1', item_name: 'Blue T-Shirt', price: 1200, quantity: 2 }]
  },
  user_data: { email: 'customer@example.com', phone: '+8801712345678' }
});

Tip: generate any event's snippet with the free DataLayer Generator.

2 — Forward to TrackRight from GTM

Add a Custom HTML tag that fires on your e-commerce events:

<script>
  var dl = {{Data Layer - ecommerce}} || {};
  fetch('https://your-domain.com/t/YOUR_CONTAINER_KEY', {
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify({
      event_name: {{Event}} === 'purchase' ? 'Purchase' : {{Event}},
      event_id: dl.transaction_id || String(Date.now()),
      source_url: location.href,
      revenue: dl.value, currency: dl.currency,
      custom_data: { items: dl.items }
    })
  });
</script>

A ready-to-import GTM container template is coming to the Downloads section.

3 — Publish and verify in Event Logs

Server-side API

Send events directly from any backend — the most reliable integration of all.

{
  "event_name": "Purchase",
  "event_id": "order-1001",
  "event_time": 1767139200,
  "source_url": "https://shop.com/checkout?fbclid=ABC",
  "revenue": 49.99,
  "currency": "USD",
  "user_data": {
    "email": "customer@example.com",
    "phone": "+8801712345678",
    "first_name": "Rahim",
    "city": "Dhaka",
    "country": "BD"
  },
  "click_ids": { "fbclid": "ABC" },
  "custom_data": { "items": [] }
}

Http::post('https://your-domain.com/t/'.$containerKey, [
    'event_name' => 'Purchase',
    'event_id' => 'order-'.$order->id,
    'revenue' => $order->total,
    'currency' => $order->currency,
    'user_data' => ['email' => $order->email, 'phone' => $order->phone],
    'click_ids' => ['fbclid' => $order->fbclid],
]);

{ "success": true, "event_id": "order-1001", "receivers": 2, "bot_filtered": false }

Delayed Purchase API COD

For cash-on-delivery and manual-payment stores: don't send Purchase at checkout — send it when the money is real. Attribution still works because click IDs were captured on the first visit.

Capturing click IDs on the first visit (JavaScript)

function getParam(name) { return new URLSearchParams(location.search).get(name); }
['fbclid', 'gclid', 'ttclid'].forEach(function (key) {
  var v = getParam(key);
  if (v) document.cookie = 'trk_' + key + '=' + v + ';max-age=2592000;path=/';
});
// Save these cookie values with the order at checkout.

Sending the delayed Purchase (server-side)

POST /t/{container-key}
{
  "event_name": "Purchase",
  "event_id": "order-1001",            // same ID = safe to retry, never double-counted
  "event_time": 1767139200,            // when payment was confirmed
  "revenue": 2450, "currency": "BDT",
  "user_data": { "email": "...", "phone": "..." },
  "click_ids": { "fbclid": "stored-value", "gclid": "stored-value" }
}

sGTM Variables Setup

Running an sGTM container? Create these Event Data variables so your server tags can read incoming event fields. In your server container: Variables → New → Event Data → enter the key path → name it → save.

Essential variables

Meta CAPI variables

GA4 & Google Ads variables

Other platforms variables

sGTM Hosting

We run Google's official Server-Side Tag Manager for you — no cloud accounts, servers, or updates to manage. Full GTM server features including Google Ads Enhanced Conversions and Preview/Debug mode.

1. 1

   Create an sGTM container

   App → Containers → New container → type "sGTM (Server-Side GTM)".

2. 2

   Paste your Container Config

   From tagmanager.google.com: Admin → Container Settings → "Manually provision tagging server" → copy the config string.

3. 3

   Pick a server location

   Bangladesh BDIX on all plans; USA and UK on premium plans.

4. 4

   Wait for provisioning

   Your tagging server spins up automatically — status turns Active on the Containers page.

5. 5

   Point your web container

   In your GTM web container, set the server_container_url to your TrackRight endpoint and publish.

Downloads — Plugins & Templates

How to import a GTM container

1. Open tagmanager.google.com and select your container.
2. Admin → Import Container.
3. Choose the downloaded .json file.
4. Pick a workspace and choose Merge (keeps your existing tags).
5. Review the changes, confirm, then Preview and Publish.

Debugging