---
title: "Complete GA4 Conversion Tracking: Browser + Server-Side Implementation"
description: "How we built bulletproof conversion tracking for syntermedia.ai — combining browser-side GA4 with server-side APIs for Google Ads, Meta, Reddit, and LinkedIn."
date: "2026-01-28"
draft: false
tags:
  - "Engineering"
  - "Attribution"
---

## The Problem with Browser-Only Tracking

Ad blockers break browser-side tracking. iOS privacy changes limit
cookie lifetimes. Third-party cookies are dying. If you&apos;re
still relying solely on client-side pixels, you&apos;re missing
30-50% of your conversions.

This tutorial walks through exactly how we set up conversion
tracking for syntermedia.ai — combining
browser-side GA4 events with server-side conversion APIs for Google
Ads, Meta, Reddit, and LinkedIn.

## The Architecture: Defense in Depth

Our conversion tracking uses two parallel paths to ensure nothing
gets missed:


If the browser-side event fires, great. If the user has an ad
blocker, the server-side upload ensures attribution still works.

## Part 1: GA4 Browser-Side Setup

Step 1: Install the GA4 Tag

Add the gtag.js snippet to your site. For Next.js, put this in
layout.tsx:

`}
/>


Step 2: Fire Conversion Events

When a user signs up, fire the synter_signup event:

)

// Called after successful signup
trackGA4Event("synter_signup", );`}
/>


Step 3: Mark Events as Conversions

In GA4 Admin → Events → Mark as conversion. Or use the Admin API:




Step 4: Link GA4 to Google Ads

In GA4 Admin → Google Ads Links → Link to your Google Ads account.
Then in Google Ads → Tools → Conversions → Import → GA4 → Select
your events.

## Part 2: Server-Side Google Ads Offline Conversions

Browser-side tracking breaks with ad blockers. Server-side uploads
work by sending the GCLID directly to Google Ads when a conversion
happens.


Step 1: Capture the GCLID

When users land from a Google ad, capture the gclid
parameter:




Step 2: Upload on Conversion

When the user converts, read the GCLID and send it to Google Ads:

## Part 3: Multi-Platform Server-Side Tracking

The same pattern works for Meta, Reddit, and LinkedIn. Create a
unified tracking service:

## Platform-Specific Click IDs

Each platform has its own Conversions API and click ID cookie:


| Platform | API | Click ID Cookie |
| --- | --- | --- |
| Google Ads | Offline Conversions API | `gclid` (URL param) |
| Meta | Conversions API (CAPI) | `_fbc`, `_fbp` |
| Reddit | Conversions API | `rdt_cid`, `_rdt_uuid` |
| LinkedIn | Conversions API | `li_fat_id` |

## Part 4: The Cron Job for Retries

Sometimes uploads fail — rate limits, network issues, token expiry.
Run a cron job to retry failed conversions:

NOW() - INTERVAL '90 days'
ORDER BY timestamp DESC
LIMIT 20
\`;

for (const conv of pendingConversions) );

if (result.success)
}

return NextResponse.json();
}`}
/>

## Part 5: Using the Google Analytics MCP

Synter supports the

Google Analytics MCP

, allowing you to query GA4 data and configure conversions
programmatically.

Available Tools
- ga4_get_properties — List all GA4 accounts and
properties
- ga4_get_report — Run reports with custom dimensions
and metrics
- ga4_get_conversions — List all conversion events
- ga4_create_conversion — Mark an event as a conversion
- ga4_get_google_ads_links — Check Google Ads account
links


Example: Pull Campaign Performance

## Results: Complete Attribution Coverage

After implementing this architecture, we saw:

- +35% more conversions attributed — Server-side
uploads caught conversions that ad blockers were hiding
- Better ROAS visibility — Google Ads now has
accurate conversion data for Smart Bidding
- Multi-platform attribution — We can see which
platform actually drove the conversion

## Try It Yourself

If you&apos;re using Synter, you can set up this same conversion
tracking for your clients. The Campaign IDE agent can help you:

- Configure GA4 conversion events
- Verify Google Ads property links
- Set up server-side tracking for multiple platforms
- Monitor conversion attribution across channels

Open Campaign IDE →
