How to Set Up Server-Side Tracking: A Step-by-Step Guide

Server-side tracking sends your website data directly from a server to advertising and analytics platforms, bypassing browser-based limitations like ad blockers and cookie restrictions. 

If you've noticed gaps between conversions in Google Analytics and what shows up in your Meta or Google Ads beyond normal attribution differences, that's often a sign your tracking is missing data due to browser restrictions.

Your tracking systems are missing transactions and other valuable user actions because privacy features, ad blockers, and browser restrictions increasingly block client-side pixels.

Real customers are converting, signing up for newsletters, downloading resources, and taking other valuable actions, but your tracking systems are missing these transactions.

Prefer your setup instructions on video? Here's our quick guide

Choose your implementation method

There are three main paths to implementation: 

• Building custom infrastructure (DIY)
• Using Google's server-side Google Tag Manager (sGTM)
• Implementing a managed platform like Tracklution 

The right choice depends on your technical resources, budget, and specific business needs.

In this guide, we'll walk through the complete setup process using Tracklution as our primary example since it's the most straightforward and cost-effective approach for most businesses. We’ll also include quick notes for DIY and sGTM approaches at each step. By the end, you'll have verified events flowing to your platforms, duplicate tracking prevented, and a safe rollout plan.

Prerequisites and background:

What you’ll need: 

• Website with conversion tracking already implemented
• Admin access to your advertising platforms (Google Ads, Meta, TikTok, etc.)
• Basic understanding of your current tracking setup

Check out our comprehensive guide on how server-side tracking works for a deeper background on the technicalities. For additional context, you can also explore our complete server-side tracking overview.

Right now, your ad platforms are missing conversion data. Server-side tracking captures more complete information, helping platforms like Google Analytics and Meta optimize your campaigns more effectively without spending more money.

Client-side tracking relies on browser-based pixels that are increasingly blocked. Server-side tracking moves data collection to a server, where it can't be blocked, then forwards clean data to platforms via APIs. This shift becomes increasingly critical as third-party cookies are being phased out and privacy regulations tighten worldwide.

Start for free →

Step 1: Create a tracking container & install base tags

The foundation of server-side tracking starts with installing the core tracking infrastructure on your website.

With Tracklution:

1. Create a new Tracking Container in your Tracklution dashboard
2. Install the Main script site-wide (typically in your site's header)
3. Add base event scripts to key pages:
   • PageView events on every page
   • Purchase events on checkout confirmation pages
   • Lead events on form submission pages
   • Additional conversion events based on your business goals 
4. Include ContactInfo collection where user provided data is available (email, phone, etc.)
5. Configure DNS settings to load tracking from your own domain for first-party data collection

You can proceed with Tracklution's standard events or create custom events that match your business needs.

For GDPR and privacy compliance, there are two main approaches: 

• Load tracking after explicit user consent (set the tags to be loaded only after consent has been granted)
• Use the advanced consent mode to reflect the real-time consent status to tracking tags to enable anonymous data modeling on unconsented sessions to get more complete data. In Tracklution, you can use our automatic consent reading features (plug-and-play approach) or configure consent data to be sent manually. 

Here's what's critical: The first PageView event must fire immediately when sessions starts or after consent is granted to preserve UTM parameters and click IDs from your traffic sources.

If you're not using Tracklution: 

You'll need to provision server-side Google Tag Manager with a server container, configure a custom domain with SSL certificates, and manually wire the client-to-server data flow before connecting to platform APIs. 

This approach requires, depending a bit on the complexity, dedicated engineering resources on average for 3+ months of development and ongoing maintenance.

If you're considering different approaches, our guide to the best server-side tracking tools compares all available options in detail.

Step 2: Map events & parameters

Proper event mapping ensures your data reaches advertising platforms in the expected format.

With Tracklution:

1. Configure Standard & Custom Events in your container
2. Add ecommerce parameters for purchase events:
   • Transaction value and currency
   • Product details in items[] array
   • Customer identifiers
3. Manage Event Mappings in Settings → Standard and Custom Events
4. Rename, block, or remap events per connector as needed

This flexibility allows you to send different event names to different platforms while maintaining consistent data collection on your site.

If you're not using Tracklution: 

You'll need to set up and map events separately for each advertising platform to which you want to send data. Configure event names, ecommerce parameters, and custom data fields according to each ad platform's specific requirements

Then ensure consistent event names and payload structures across your client-side and server-side implementations. Include all identifiers required by each advertising platform's API (customer information, transaction IDs, product catalogs).

Step 3: Validate in Tracklution (before connecting platforms)

Before connecting any advertising platforms, confirm your data flows correctly through the tracking system. This validation step prevents wasted time debugging platform connections when the issue is in your base tracking setup.

With Tracklution:

1. Click Start Listening for Events in your dashboard
2. Navigate your website to trigger events (page views, form submissions, purchases)
3. Confirm events appear in real-time: PageView, conversion, and ContactInfo events
4. Use the Session Data Table in your dashboard to inspect:
   • Event payloads and parameters
   • UTM parameter capture
   • Click ID preservation (GCLID, FBLID, etc.)

Review session drill-downs to verify complete user journey tracking

This validation step prevents wasted time debugging platform connections when the issue is in your base tracking setup.

If you're not using Tracklution: 

Use server-side Google Tag Manager's preview mode and browser network tools to confirm server-side hits are firing with expected parameters. Monitor server logs to verify data processing.

Get started with validated tracking →

Step 4: Connect your ad & analytics platforms

With validated data flowing, you can now connect your advertising and analytics platforms to receive server-side data.

With Tracklution: 

Navigate to Connectors and add your platforms:

Google Ads setup:

1. Connect your Google Ads account 
2. Create Conversion Action lists for your events in Tracklution’s simple UI. You can choose which events to create and if they are used as Primary or Seconday goal.
3. Ensure you have Enhanced Conversions set up in Google Ads → Goals → Settings (if you want to use them) and the delivery method is ‘Google Ads API’ acceptance rules (requires GCLID or Enhanced Conversions via ContactInfo)
4. Note: It takes approximately 6 hours for new conversion action lists to appear in Google’s side. Tracklution will store all events and send them to Google when Google is ready with processing the list, so no data will be lost even though there is a delay.

Meta (Facebook) setup:

1. Add your Pixel ID and Conversions API token
2. Optionally, map your custom events to Meta's standard events (Purchase, Lead, ViewContent, etc.) in Settings if needed
3. Important: Avoid duplicate data by ensuring no other tools send to the same Pixel simultaneously

TikTok/Snapchat/LinkedIn setup:

1. Provide Pixel ID or API tokens for authentication
2. Optionally, map custom events to platform-specific naming conventions in Settings
3. Toggle Live when ready to start sending data
4. Remove old pixel implementations to prevent duplicates

Once connected, all platforms work with the same accurate customer data instead of operating on conflicting reports.

If you're not using Tracklution: 

Reference each platform's API documentation for authentication requirements and handle OAuth flows, API rate limits, and error management for each platform. Many businesses find this approach overcomplicated and challenging because it pulls developers away from other important projects.

Step 5: Prevent duplicates & pick your test plan

Duplicate tracking inflates your conversion numbers and skews campaign optimization. Plan your transition carefully to avoid inflated metrics that lead to poor scaling decisions.

With Tracklution:

For Meta/TikTok/Snapchat:

• Don't run multiple tools sending events to the same Pixel ID
• If you must keep legacy tracking temporarily, test Tracklution on a separate test Pixel until you're ready to switch completely
• Never send the same conversion event from both browser pixels and server-side simultaneously

For Google Ads:

• Run Tracklution conversions in Secondary status for parallel testing
• After validation, promote to Primary status and demote legacy actions to Secondary
• Ensure only one conversion action per event type is set to Primary to avoid double-counting

Testing strategy options:

1. Separate test environment: Use staging/test pixels for initial validation
2. Gradual rollout: Start with less critical campaigns or event types
3. Parallel comparison: Run both systems briefly with clear labelling for analysis

If you're not using Tracklution: 

Implement the creation and logic for deduplication keys or event IDs in your server-side setup, test and ensure that it works. Carefully coordinate pausing legacy browser-based tracking to avoid gaps or overlaps in data collection.

Step 6: Run parallel & compare results

Before switching to server-side tracking, confirm that your new setup matches expected performance.

With Tracklution:

1. Use Processed Data filtering to analyze:
   • Volume comparison by connector, event type, and date range
   • Data match quality and attribution accuracy
   • Processing lag between event occurrence and platform delivery
2. Compare Tracklution's processed data against platform reporting dashboards
3. Account for attribution window differences when comparing conversion counts
4. Monitor for any missing UTM parameters or click ID issues

What healthy parity looks like:

• Expected conversion volume reaching platforms consistently
• UTM parameters and click IDs are properly preserved
• Similar conversion values and customer matching rates
• Platform reporting showing consistent trends with historical data

If you're not using Tracklution: 

Export data from each platform and align attribution windows for accurate comparison. Set up server logging and API response tracking to monitor data delivery and identify any issues.

Step 7: Roll out to production

Once you've validated parallel performance, complete the transition to server-side tracking.

With Tracklution:

1. Toggle Live status for each connector you've tested
2. In Google Ads, set your Tracklution conversion actions to Primary status
3. Remove or retire legacy browser-based tracking tags
4. Monitor to confirm stable data flow
5. Archive old conversion actions once you're confident in the new setup

Keep your old tracking code commented out or paused (not active) as a rollback option while you monitor the transition.

If you're not using Tracklution: 

Systematically disable legacy pixels and browser-based integrations. Confirm that only your new server-side implementation sends data to avoid accidentally reintroducing duplicates.

Complete your server-side setup →

Troubleshooting & common pitfalls

When server-side tracking goes wrong, most issues fall into predictable categories.

Data not flowing at all? 

This almost always comes down to script loading order. Your Main script needs to load before any event scripts can fire. Check your browser console for JavaScript errors blocking execution, even unrelated site issues can interfere with tracking.

Getting events but missing customer information? 

Your ContactInfo scripts aren't firing on the right pages or then the information is missing from the data layer. This tag must be active where customer data is available: during login, form submissions, or checkout completion. Don't expect to capture user data on pages where users haven't provided it yet.

UTM parameters and click IDs disappearing into thin air? 

This is the classic consent timing problem. Your first PageView event must fire immediately after consent is granted, before any page redirects or navigation. If a split-second delay occurs, those valuable UTM parameters and click IDs vanish forever.

Can't figure out which marketing efforts deserve credit? 

You can see deals closing and money coming in, but you can't connect the dots between marketing spend and results. This makes budget allocation decisions extremely difficult. 

Review your Processed Data to confirm UTM parameters and platform click IDs are being captured from traffic sources. If attribution data is missing, check that your first PageView timing is correct and that your server is forwarding this data to connected platforms.

Conversion numbers looking suspiciously high? 

Most probably you've got duplicate tracking running somewhere. This is more common than you'd think. For example, legacy browser pixels hide in old code, multiple Google Ads conversion actions are set to Primary status, or different tools are sent to the same Meta Pixel. Your campaigns optimize for inflated numbers, explaining why scaling efforts fall short of expectations.

Is the platform reporting delayed or missing? 

Don't worry about delays. DNS propagation for custom domains can take up to 48 hours, which won't affect your data collection. However, if events aren't showing up after 48 hours, check your API credentials and connector settings.

Events firing, but platforms rejecting them? 

Usually, it is an event naming or formatting issue. Platforms like Meta and Google expect specific event names and parameter structures. Fortunately, Tracklution's event mapping feature lets you rename events per connector without changing your website code. This saves weeks of development work!

Why Tracklution is the fastest path

Server-side tracking doesn't have to be a never-ending technical project. Unlike DIY server infrastructure or complex Google Tag Manager server setups, Tracklution provides immediate server-side tracking with minimal technical overhead.

What you get with Tracklution:

• One tag installation (no complex infrastructure setup)
• Automatic event and data mappings, validation, and monitoring
• Pre-built connectors for major advertising platforms
• Built-in duplicate prevention and deduplication
• Optional first-party data enrichment through DNS configuration
• Managed API authentication, rate limiting, and error recovery
• Ongoing maintenance is handled automatically

This lets you concentrate on optimizing campaigns instead of maintaining tracking infrastructure.

What it can’t fix: While Tracklution solves many critical issues, it's not a silver bullet. If your pixels are incorrectly installed or your events are inconsistently named, server-side tracking won't automatically fix that.

However, for most businesses, a ready-made solution offers the best balance because implementation takes minutes instead of months. Whether you want better data accuracy, improved attribution, or a working setup, the easiest option is often the best.

For businesses looking to understand the broader impact, our article on the power of server-side tracking in digital advertising explores how this shift affects campaign performance and ROI.

Start your free trial today →

Frequently asked questions

Here are the most common questions we get about server-side tracking implementation:

1. How long does server-side tracking setup take? 

With Tracklution, most implementations, including validation and platform connections are completed quickly within a single day. DIY approaches typically require dedicated engineering teams for 3+ months of development and ongoing maintenance.

1. When should I switch from parallel testing to production? 

Switch after parallel testing when you've confirmed consistent conversion volume parity and similar attribution performance across your key campaigns. Depending on your traffic volume and desired confidence level, this typically takes anywhere from a few days to 14-30 days.

1. How do I handle consent management with server-side tracking? 

You have two options: 

• Basic consent mode (load tracking only after users accept cookies)
• Advanced consent mode (collect anonymous data before consent, then enhance with personal data after acceptance). 

The critical requirement is that the first PageView event fires immediately when the session starts (in advanced mode) or immediately after consent is granted (in basic mode) to preserve click IDs and UTM parameters.

1. What happens if I have duplicate tracking running? 

Duplicate tracking inflates conversion counts, leading to incorrect ROAS calculations and suboptimal campaign bidding. Always ensure only one system sends each conversion event to each platform.

1. Do I need technical expertise to implement server-side tracking? 

Tracklution requires basic tag installation skills, similar to Google Analytics setup, so no developers are needed. DIY approaches necessitate dedicated engineering teams for server infrastructure, API integrations, and ongoing maintenance, which is many times a full-time job.

Ready to implement reliable server-side tracking without the technical complexity? 

While your competitors still play marketing roulette with incomplete data, you'll make decisions based on the whole picture. It's the difference between driving with a clear windshield and driving in fog: the same road, dramatically different outcomes. 

Your ad platforms are currently missing conversion data, making it impossible to know your true ROAS. Start your free Tracklution trial and get your first container running quickly.