You’ve got Google Ads, Meta campaigns, maybe even TikTok running. But when you check your GA4 dashboard, it feels like a ghost town. Meanwhile, Meta’s reporting more sales than you actually made. TikTok? It’s as if it doesn’t know your store exists.

I get it — you’re doing the right things. You’re spending on ads, optimizing your creatives, tweaking your budget. But none of that matters if the data you’re seeing isn’t real.

Tracking is the difference between scaling confidently and flying blind. And right now, if you’re using MyOnlineStore with the default setup, chances are good your tracking is incomplete, misfiring, or flat-out broken.

This guide is built on real client work — actual setups where we took underperforming data stacks and rebuilt them into conversion machines using GTM, GA4, server-side tagging, and structured dataLayers. Let’s fix this — one platform at a time.

If you’ve ever looked at your GA4 report, scratched your head, and thought, “Wait… why does it say 2 purchases when we had 10 today?” — you’re not alone.

Meta says one thing. TikTok says nothing. Your store backend says something else entirely.

I’ve helped dozens of MyOnlineStore merchants fix this exact mess. And let me tell you — the problem isn’t your ads. It’s your tracking stack. What’s broken is the way your site talks to your ad platforms.

This guide is my full blueprint — based on real-world fixes — that I use to clean up tracking, recover lost attribution, and get ads performing the way they should. Let’s dig in.

Section 1: The Real Problem With MyOnlineStore Tracking

What really breaks inside MyOnlineStore?

1. No Native GA4 Integration: MyOnlineStore doesn’t push ecommerce events like purchase, add_to_cart, or view_item into the dataLayer. You have to build this manually.
2. Meta Pixel Breakage: Events often fire without values or fire twice. Match quality drops, and Facebook CAPI can’t deduplicate.
3. Other Ad Platforms Ignored: No support for TikTok Pixel, Pinterest Tag, Microsoft UET, or LinkedIn Insight. You’re missing full-funnel tracking.
4. Consent Mode v2 Missing: This is a big deal. If you’re marketing in the EU or UK, tags will be blocked unless you implement Consent Mode.
5. No Server-Side Tracking: Browser-only tracking fails in Safari/iOS. Conversion APIs and SSGTM are required for reliable attribution.
6. Click ID Loss: gclid, fbclid, ttclid, msclkid — all drop off after the first page unless you manually store them in cookies.
7. No Consistent Event Schema: Purchase values are misaligned across platforms. GA4 might show 5 sales, Meta shows 8, but your backend says 12.

The Silent Killer: Incomplete Attribution

Because these issues aren’t always visible on the front end, most merchants don’t notice until it’s too late. What you see is:

• ROAS dropping
• CPA rising
• Ad platforms making bad optimization decisions

Why it matters: Clean tracking isn’t a nice-to-have. It’s the foundation of scaling your store. If ad platforms can’t see real purchase data and click IDs, your ads don’t just underperform — they waste money by optimizing for phantom metrics.

📉 Pro Tip: If your GA4 revenue doesn’t match your payment processor and you rely on Smart Bidding, you’re not just losing visibility — you’re training Google on the wrong signals.

Section 2: The 2025 Tracking Stack You Actually Need

The future of accurate marketing attribution is not one tag — it’s a stack. For MyOnlineStore in 2025, this stack must bridge client-side visibility, server-side reliability, and privacy-first compliance.

🔍 Why You Need a Full Stack

Modern browsers block cookies. iOS limits trackers. EU users require consent. If you rely only on client-side pixels, you’re seeing only 50–70% of what’s really happening.

This stack below fixes that with platform-grade precision.

 Browser-Side (Client):

• GTM Web Container — centralizes tracking logic
• GA4 Tags — tracks ecommerce interactions, sessions, engagement
• Meta Pixel — triggers standard events for Meta’s ad delivery
• TikTok Pixel — triggers top-of-funnel awareness & conversions
• Pinterest Tag — tracks Pinterest’s visual-driven ecommerce journey
• Microsoft UET — powers Microsoft Ads remarketing and offline import
• Reddit Pixel — still browser-only, great for niche traffic
• LinkedIn Insight Tag — enables retargeting and conversions for B2B audiences

 Server-Side Layer:

• GTM Server Container (hosted on App Engine, Cloud Run, or EC2)
• Meta Conversions API (CAPI) — boosts match rate and iOS attribution
• TikTok Events API — required to unlock deduplication + full conversion data
• Google Ads Enhanced Conversions — recovers lost conversions from Safari/iOS
• Pinterest Conversion API — optional fallback to browser pixel
• Microsoft/LinkedIn Offline Conversion Uploads — close the loop for manual imports

 Consent & Privacy Tools:

• Google Consent Mode v2 — lets tags adapt to user consent
• Cookiebot / OneTrust — cookie banners that hold tag firing until allowed
• Custom consent logic for SPA behavior or complex forms

 Bonus: First-Party Click ID Capture for Attribution

Store ad click IDs immediately in cookies for future use by server tags:

<script>
['gclid','fbclid','ttclid','msclkid','li_fat_id'].forEach(param => {
  const val = new URLSearchParams(window.location.search).get(param);
  if (val) {
    document.cookie = `${param}=${val}; path=/; max-age=2592000`;
  }
});
</script>

Pro Tip: A hybrid stack like this doesn’t just restore visibility. It gives you platform-verified conversions, improves match quality, unlocks Smart Bidding accuracy, and sets you up for long-term scaling.

Here’s a battle-tested tracking stack that gives full-funnel, privacy-compliant visibility:

Browser-Side (Client):

• GTM Web Container
• GA4 Tags (events + pageviews)
• Meta Pixel
• TikTok Pixel
• Pinterest Tag
• Microsoft UET
• Reddit Pixel
• LinkedIn Insight Tag

Server-Side:

• GTM Server (App Engine, Cloud Run, or AWS EC2)
• Meta CAPI via SSGTM
• TikTok Events API via SSGTM
• Google Ads Enhanced Conversions
• Pinterest CAPI fallback
• Microsoft/LinkedIn Offline Conversions

Consent/Privacy:

• Google Consent Mode v2
• Cookiebot/OneTrust to delay tag firing

Bonus: Store all click IDs in 1st-party cookies

<script>
['gclid','fbclid','ttclid','msclkid','li_fat_id'].forEach(param => {
  const val = new URLSearchParams(window.location.search).get(param);
  if (val) {
    document.cookie = `${param}=${val}; path=/; max-age=2592000`;
  }
});
</script>

Section 3: Build a Clean dataLayer for MyOnlineStore

The core of all accurate tracking starts with the dataLayer. This is where you define structured ecommerce data that every tag — GA4, Meta, TikTok, Pinterest, and more — depends on. If your dataLayer is incomplete, all downstream tags will fail or report incorrect values.

Why it matters:

• GA4 expects specific keys like transaction_id, value, currency, and items
• Meta Pixel + CAPI uses value, currency, and content_ids
• TikTok Events API requires event_id, ttclid, currency, and value
• Google Ads Enhanced Conversions depends on clean user and order data

Example: Full Purchase dataLayer Push

Add this script to the order confirmation page (after the transaction is confirmed):

window.dataLayer = window.dataLayer || [];

dataLayer.push({
  event: "purchase",
  transaction_id: "ORD-4567",
  affiliation: "MyOnlineStore",
  value: 149.99,
  currency: "USD",
  coupon: "WELCOME10",
  shipping: 5.99,
  tax: 12.50,
  items: [
    {
      item_name: "Cotton Hoodie",
      item_id: "CH_001",
      price: 69.99,
      quantity: 1,
      item_category: "Apparel",
      item_variant: "Large / Navy"
    },
    {
      item_name: "Sports Water Bottle",
      item_id: "WB_004",
      price: 80.00,
      quantity: 1,
      item_category: "Accessories",
      item_brand: "HydroMate"
    }
  ]
});

Key Attributes to Always Include:

• event: Signals the type of user behavior (like purchase, add_to_cart, etc.)
• transaction_id: Unique ID for deduplication across platforms
• value and currency: Required for ROAS calculation
• items[]: Structured array of purchased products
• Optional: coupon, shipping, tax, affiliation, item_brand, item_variant

 Pro Tip: Avoid hardcoding values. Use dynamic template variables or server-side rendering to populate real order data. Always validate output in Tag Assistant or GA4 DebugView.

 Once this structure is in place, GTM tags for all platforms will become much easier to manage and scale.

The core of all tracking is a standardized dataLayer push. Here’s an ideal version:

window.dataLayer = window.dataLayer || [];

dataLayer.push({
  event: "purchase",
  transaction_id: "ORD-4567",
  affiliation: "MyOnlineStore",
  value: 149.99,
  currency: "USD",
  coupon: "WELCOME10",
  shipping: 5.99,
  tax: 12.50,
  items: [
    {
      item_name: "Cotton Hoodie",
      item_id: "CH_001",
      price: 69.99,
      quantity: 1,
      item_category: "Apparel"
    },
    {
      item_name: "Sports Water Bottle",
      item_id: "WB_004",
      price: 80.00,
      quantity: 1,
      item_category: "Accessories"
    }
  ]
});

Why this format?

• It complies with GA4
• Meta uses value, currency, content_ids
• TikTok needs event_id, value, and currency
• Works for server deduplication

Section 4: Setup Google Tag Manager (Web)

Google Tag Manager (GTM) acts as your control tower for all browser-side tracking. It helps you manage tags, triggers, and variables without constantly editing your site’s code.

Step 1: Install GTM Snippet

Insert the GTM container snippets into your MyOnlineStore site:

• <script> snippet in the <head>
• <noscript> iframe snippet directly after the opening <body> tag

Step 2: Create Tags for Key Events

You’ll need GTM to listen for and fire tags on:

• view_item
• add_to_cart
• begin_checkout
• purchase

These events are triggered by the dataLayer code you push on each interaction.

Step 3: Example GTM Trigger for Purchase Event

Go to Triggers > New:

• Type: Custom Event
• Event name: purchase

This trigger will fire when the dataLayer includes event: ‘purchase’.

Step 4: Configure Variables for Your Tags

Use Data Layer Variables (DLVs) to pull values like:

• transaction_id
• value
• currency
• items

Create DLVs by navigating to Variables > New > Data Layer Variable.

Step 5: Platform-Specific Event Naming (Lookup Table)

Different platforms expect different event names. Use GTM’s Lookup Table variable to map generic purchase events to platform-specific naming conventions:

• GA4 → purchase
• Meta → Purchase
• TikTok → CompletePayment
• Pinterest → checkout
• LinkedIn → Lead

Bonus: Add Tag Sequencing and Blocking Rules

Prevent duplicate tags by using tag sequencing and exceptions. For example:

• Only fire the GA4 purchase tag after a successful ecommerce event push
• Block Meta Pixel from firing if URL already includes thank-you=true

Pro Tip: Always preview and test tags before publishing. Use the GTM Preview mode + platform-specific tools like Meta Pixel Helper, TikTok Pixel Helper, and GA4 DebugView to confirm everything fires correctly.

Install GTM:

• Add GTM script to <head> and <noscript> to <body>

Create tags for key events:

• view_item, add_to_cart, begin_checkout, purchase
• Use event triggers linked to dataLayer push

Example GTM Trigger for Purchase:

• Trigger type: Custom Event
• Event name: purchase

Use Variables:

• DLV – transaction_id, value, currency, items

Platform Mapping (Lookup Table):

• GA4: purchase
• Meta: Purchase
• TikTok: CompletePayment

Section 5: Setup Google Analytics 4 (GA4) Properly

Google Analytics 4 is the core analytics layer for every modern ecommerce setup. But it only works if you send the right data, in the right format, with the right structure.

Step 1: Use Recommended GA4 Ecommerce Events

Define and fire the following GA4 events from GTM:

• view_item
• add_to_cart
• begin_checkout
• purchase

Each event should include:

• transaction_id
• value
• currency
• items[] (with item ID, name, price, quantity)

Example GA4 Event Tag (GTM Web):

• Tag Type: GA4 Event
• Configuration Tag: Your GA4 config tag
• Event Name: purchase
• Event Parameters:
  • transaction_id: {{DLV – transaction_id}}
  • value: {{DLV – value}}
  • currency: {{DLV – currency}}
  • items: {{DLV – items}}

Step 2: Use Data Layer Debugging Tools

Open Chrome → Tag Assistant Preview + GA4 DebugView

• Trigger test transactions
• Make sure purchase values match real backend orders
• Ensure parameters show up in Realtime > Events

Step 3: Build Funnel Reports in GA4

GA4’s funnel exploration reports let you track:

• Drop-off from product view → add to cart
• Drop-off from add to cart → checkout
• Drop-off from checkout → purchase

This helps you identify UX bottlenecks or pixel/tag failures.

Bonus Tip: Enable Google Signals

Turn on Google Signals in GA4 to allow cross-device reporting and remarketing list creation in Google Ads.

Pro Tip: If GA4 is underreporting purchases, check that your purchase tag is firing on the confirmation page only once, and not being blocked by consent or redirects.

GA4 Tag Settings:

• Tag Type: GA4 Event
• Event Name: purchase
• Parameters:
  • transaction_id = {{DLV – transaction_id}}
  • value = {{DLV – value}}
  • currency = {{DLV – currency}}
  • items = {{DLV – items}}

Debugging Tips:

• Use GA4 DebugView with Chrome GTM Preview Mode
• Match GA4 revenue with MyOnlineStore dashboard

Create custom funnel reports:

• Add-to-cart → checkout start → purchase

Section 6: Google Ads Enhanced Conversions

Enhanced Conversions improve your Google Ads performance by matching conversions more reliably — even when third-party cookies are blocked. This setup helps fill the gaps using hashed first-party data and click IDs.

Step 1: Capture the gclid (Google Click ID)

Store it in a first-party cookie as soon as the user lands:

const gclid = new URLSearchParams(window.location.search).get('gclid');
if (gclid) {
  document.cookie = "gclid=" + gclid + "; path=/; max-age=2592000";
}

Step 2: Collect User Data at Checkout

When a customer completes a purchase, capture their email and/or phone securely. Then, hash it using SHA-256. This can be done client-side or on your server.

Step 3: Send Hashed User Data via GTM (Client-Side)

gtag('set', 'user_data', {
  email: 'hashed_email_value',
  phone_number: 'hashed_phone_value'
});

Step 4: Send Enhanced Conversions via GTM Server

Here’s what the payload looks like when sent via SSGTM:

{
  "conversion_data": {
    "email": "hashed_email",
    "phone_number": "hashed_phone",
    "gclid": "stored_cookie_value",
    "value": 149.99,
    "currency": "USD",
    "transaction_id": "ORD-4567"
  }
}

Step 5: Choose How to Report Conversions

You can:

• Use GA4 events as Google Ads conversion goals
• OR use standalone Google Ads conversion tags in GTM (Web or Server)

Validation Tips:

• Use Chrome’s GTM Preview mode to test client-side tags
• Inspect server requests in GTM Server logs
• Monitor Google Ads > Tools > Enhanced Conversions section

Pro Tip: Enhanced Conversions typically recover 15–30% of lost conversions in iOS and privacy-restricted environments. They’re essential for accurate ROAS and Smart Bidding efficiency.

Steps:

1. Capture gclid via URL
2. Store in cookie
3. Collect email/phone at checkout
4. Hash and send to Google via GTM

Client-Side Example:

gtag('set', 'user_data', {
  email: 'hashed_email_value'
});
Server-Side JSON:
{
  "conversion_data": {
    "email": "hashed_value",
    "gclid": "stored_cookie_value",
    "value": 149.99,
    "currency": "USD"
  }
}

Section 7: Meta (Facebook & Instagram) Tracking

Meta’s tracking relies on both browser (Pixel) and server-side (CAPI) data. Using both ensures better attribution, particularly for iOS and Safari users.

Step 1: Install Meta Pixel via GTM

Use a Custom HTML tag or a Community Template inside GTM:

<script>

fbq('init', 'META_PIXEL_ID');

fbq('track', 'PageView');

</script>

Replace META_PIXEL_ID with your actual Meta Pixel ID.

Step 2: Fire Standard Events

Create GTM tags to fire on ecommerce events. For example, the Purchase event:

<script>
fbq('track', 'Purchase', {
  value: {{DLV - value}},
  currency: '{{DLV - currency}}',
  content_ids: {{DLV - item_ids}},
  content_type: 'product',
  eventID: '{{event_id}}'
});
</script>

Use eventID to deduplicate with server-side events.

Step 3: Capture User Data for Enhanced Matching

Collect email or phone number on checkout, hash them using SHA-256, and send to Meta CAPI. Example with GTM Server:

{
  "event_name": "Purchase",
  "event_time": 1719940000,
  "event_id": "event123",
  "user_data": {
    "em": "hashed_email",
    "ph": "hashed_phone"
  },
  "custom_data": {
    "value": 149.99,
    "currency": "USD",
    "content_ids": ["CH_001"],
    "content_type": "product"
  }
}

Step 4: Use Meta Conversions API (CAPI)

Setup GTM Server or use direct API with secure token authentication. Ensure:

• event_id matches Pixel tag
• external_id or em/ph are passed
• content_ids, currency, and value are accurate

Step 5: Validate in Meta Events Manager

• Check for deduplication status
• Review Match Quality Scores
• Confirm event parameters match backend values

 Pro Tip: When CAPI and Pixel are both active and accurate, Meta will automatically deduplicate and boost conversion reporting. You’ll see higher match rates, which means better ad delivery, cheaper cost-per-purchase, and clearer ROAS data.

Meta Pixel via GTM:

fbq('track', 'Purchase', {
  value: {{DLV - value}},
  currency: {{DLV - currency}},
  content_ids: {{DLV - item_ids}},
  content_type: 'product',
  eventID: {{event_id}}
});

Meta CAPI (via SSGTM):

{

"event_name": "Purchase",
  "event_time": 1719940000,
  "event_id": "event123",
  "user_data": {
    "em": "hashed_email"
  },
  "custom_data": {
    "value": 149.99,
    "currency": "USD",
    "content_ids": ["CH_001"]
  }
}

Section 8: TikTok Ads Tracking the Right Way

TikTok’s attribution model relies heavily on capturing first-party identifiers and deduplicating browser and server events. If you’re not using both client and server-side tracking, you’re missing up to 50% of your actual conversions.

Step 1: Install the TikTok Pixel via GTM Web

Add the TikTok Pixel using GTM’s “Custom Template” or HTML tag method. Fire events like PageView, AddToCart, and CompletePayment based on dataLayer triggers.

ttp('track', 'CompletePayment', {
  value: {{DLV - value}},
  currency: {{DLV - currency}},
  content_id: {{DLV - item_id}},
  event_id: {{event_id}}
});

Use a shared event_id between Pixel and Events API to ensure deduplication.

Step 2: Capture the ttclid Parameter

TikTok click IDs must be stored in a cookie for attribution. Add this script sitewide:

const ttclid = new URLSearchParams(window.location.search).get('ttclid');
if (ttclid) {
  document.cookie = "ttclid=" + ttclid + "; path=/; max-age=2592000";
}

Step 3: Setup TikTok Events API via Server-Side GTM

This is where you fix lost attribution. Trigger the server-side event on purchase:

You must include the ttclid for attribution and event_id for deduplication.

Validation Tools:

• TikTok Events Manager → Realtime view
• TikTok Pixel Helper extension → for browser-side validation
• GTM Server Logs → to confirm Events API hits

Pro Tip: When TikTok Events API is properly configured, match rates increase dramatically. You’ll also notice algorithm performance improve within 3-5 days as signal quality improves.

Pixel via GTM Web:

ttp('track', 'CompletePayment', {
  value: {{DLV - value}},
  currency: {{DLV - currency}},
  content_id: {{DLV - item_id}},
  event_id: {{event_id}}
});

Server Event Payload:{

"event": "CompletePayment",
  "event_id": "tt_abc123",
  "ttclid": "xyz_ttclid_123",
  "properties": {
    "value": 149.99,
    "currency": "USD"
  }
}

{
  "event": "CompletePayment",
  "event_id": "tt_abc123",
  "ttclid": "xyz_ttclid_123",
  "properties": {
    "value": 149.99,
    "currency": "USD"
  }
}

Section 9: Pinterest Ads Conversion Tracking

Pinterest can be a powerful channel for ecommerce brands, especially in niches like fashion, beauty, home decor, and wellness. But without proper tracking, your campaigns will lack the data needed to optimize.

Step 1: Install the Pinterest Tag via GTM Web

Use a Custom HTML tag inside GTM to install the base pixel:

<script>
!function(e){if(!window.pintrk){window.pintrk = function () {
window.pintrk.queue.push(Array.prototype.slice.call(arguments))};
var n=window.pintrk;n.queue=[],n.version="3.0";
var t=document.createElement("script");
t.async=!0,t.src=e;
var r=document.getElementsByTagName("script")[0];
r.parentNode.insertBefore(t,r)}}("https://s.pinimg.com/ct/core.js");
pintrk('load', 'PINTEREST_TAG_ID');
pintrk('page');
</script>

Replace PINTEREST_TAG_ID with your actual ID from the Pinterest Ads Manager.

Step 2: Track Conversion Events

Fire the checkout or purchase event via GTM based on your dataLayer trigger:

<script>
pintrk('track', 'checkout', {
  value: 149.99,
  order_quantity: 2,
  currency: 'USD',
  order_id: 'ORD-4567'
});
</script>

You can also track events like add_to_cart, search, or signup depending on your funnel.

Step 3: Implement Pinterest Conversion API (Optional but Recommended)

Use GTM Server to send fallback events to Pinterest:

{
  "event_name": "checkout",
  "event_time": 1719847000,
  "currency": "USD",
  "value": 149.99,
  "order_id": "ORD-4567",
  "user_data": {
    "em": "hashed_email_here"
  }
}

This improves reliability when cookies are blocked or browser-side tags fail.

Step 4: Validate Your Setup

• Use Pinterest Tag Helper Chrome extension
• Check Pinterest Events Manager for real-time logs

Pro Tip: Pinterest often performs best when you build and optimize for rich pins and product catalog campaigns. Clean conversion tracking unlocks the ability to use dynamic retargeting and measure real ROAS inside the platform.

Pinterest Checkout Tag:

<script>
pintrk('track', 'checkout', {
  value: 149.99,
  order_quantity: 2,
  currency: 'USD',
  order_id: 'ORD-4567'
});
</script>

Optional Server-Side Payload:

• Pinterest CAPI fallback using order_id and hashed email

Section 10: Microsoft Ads (UET) and Offline Conversions

Microsoft Ads may not be as flashy as Meta or Google, but when set up properly, it offers incredible ROI, especially for search campaigns.

Step 1: Install the UET Tag via GTM

Use a Custom HTML tag in your GTM Web container:

<script>
(function(w,d,t,r,u){
  var f,n,i;w[u]=w[u]||[],f=function(){var o={ti:"UET_TAG_ID"};o.q=w[u],w[u]=new UET(o),w[u].push("pageLoad")},
  n=d.createElement(t),n.src=r,n.async=1,n.onload=n.onreadystatechange=function(){
    var s=this.readyState;s&&s!="loaded"&&s!="complete"||(f(),n.onload=n.onreadystatechange=null)
  },
  i=d.getElementsByTagName(t)[0],i.parentNode.insertBefore(n,i)
})(window,document,"script","//bat.bing.com/bat.js","uetq");
</script>

Replace UET_TAG_ID with your actual UET Tag ID from Microsoft Ads.

Step 2: Capture msclkid

To ensure offline conversion matching, you must store the click ID:

const msclkid = new URLSearchParams(window.location.search).get('msclkid');
if (msclkid) {
  document.cookie = "msclkid=" + msclkid + "; path=/; max-age=2592000";
}

You’ll use this cookie value later during your offline conversion upload.

Step 3: Collect Conversion Event Details

At the moment of purchase, log the following data into your CRM or database:

• msclkid (from cookie)
• transaction_id
• conversion_time (ISO 8601 format)
• value
• currency

Step 4: Upload to Microsoft Ads

Use their offline conversions import tool or API to send this data. You can upload CSVs manually or automate the process.

Example CSV Headers:

MSCLKID,ConversionName,ConversionTime,ConversionValue,CurrencyCode

fgh456…xyz,Purchase,2025-06-29T15:45:00Z,149.99,USD

Pro Tip: Microsoft Ads rewards accounts that consistently feed back conversion data. Offline conversions improve Smart Bidding results by up to 25% in most accounts I’ve managed.

 Validate in the “Offline Conversions” section inside your Microsoft Ads dashboard.

Section 11: Reddit Ads Conversion Tracking

Reddit Ads is still developing its tracking infrastructure, but with a solid setup, you can gather meaningful insights.

Step 1: Install Reddit Pixel via GTM Custom HTML

Use the following snippet in a Custom HTML tag within your GTM web container:

<script>
!function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'event':'PageView'});
var f=d.getElementsByTagName(s)[0],j=d.createElement(s);
j.async=true;j.src='https://www.redditstatic.com/ads/pixel.js';
f.parentNode.insertBefore(j,f);
}(window,document,'script','rdt','REDDIT_PIXEL_ID');
</script>

Make sure this fires on All Pages to capture page views platform-wide.

Step 2: Track Purchase or Conversion Events

Create a separate tag in GTM to fire on the purchase custom event from your dataLayer:

<script>
rdt('track', 'Purchase', {
  transaction_id: '{{DLV - transaction_id}}',
  value: {{DLV - value}},
  currency: '{{DLV - currency}}'
});
</script>

Step 3: Store Reddit Click ID (Optional)

If Reddit passes a click ID (often in beta or custom tracking setups), store it:

const redditclid = new URLSearchParams(window.location.search).get('redditclid');
if (redditclid) {
  document.cookie = "redditclid=" + redditclid + "; path=/; max-age=2592000";
}

You can then use this for server-side event matching in the future if Reddit launches their Conversions API.

Validation

• Use the Reddit Pixel Helper extension to verify events
• Check that the PageView and Purchase events fire correctly

 Note: As of 2025, Reddit does not yet offer a server-side API. All conversions must be tracked client-side.

Section 12: LinkedIn Ads Setup With Offline Support

LinkedIn is essential for B2B and high-ticket products, but its conversion tracking requires a bit more manual effort.

Step 1: Capture li_fat_id from Ad Clicks

This ID allows LinkedIn to match users with conversions.

const li_fat_id = new URLSearchParams(window.location.search).get('li_fat_id');
if (li_fat_id) {
  document.cookie = "li_fat_id=" + li_fat_id + "; path=/; max-age=2592000";
}

Store this in a first-party cookie so it can be picked up at checkout and passed into your CRM or server log.

Step 2: Collect Conversion Data

When a customer purchases, capture the following:

• Transaction ID
• Value & Currency
• Timestamp
• Hashed Email or Phone (SHA-256)
• li_fat_id stored from Step 1

Step 3: Upload Offline Conversions

Use LinkedIn’s Offline Conversions tool or API. The upload fields should include:

• li_fat_id
• conversion_time (ISO format)
• conversion_value
• currency
• user_identifier (email/phone hashed)

Optional:

• Automate the upload daily with a cron job or webhook
• Use LinkedIn Matched Audiences to retarget purchasers with high-ticket upsells

 Pro Tip: High match rates on li_fat_id lead to more accurate cost-per-lead data and better attribution inside LinkedIn Campaign Manager.

Final Call to Action

Let’s get real — if your tracking is broken, your growth is stuck. You can’t scale what you can’t measure. That’s where I come in.

I work directly with MyOnlineStore owners like you to rebuild tracking from the ground up: GA4, Google Ads, Meta CAPI, TikTok Events API, and server-side tagging that actually works.

Here’s what I’m offering: ✅ A 100% free audit of your entire tracking setup — no fluff, no hard sell. ✅ A line-by-line breakdown of what’s missing, what’s misfiring, and what needs to be fixed. ✅ A clear game plan you can implement to finally trust your data.

This isn’t a template — it’s built from real audits I’ve done for stores just like yours.

📞 Don’t keep guessing. Let’s turn your tracking into a real asset. 👉 Book Your Free Tracking Audit Now and get the clarity you need to grow confidently.