Complete Lead Tracking Guide for Q4 Preparations

Every website has different dynamics and measurement methodologies. Today, our topic will be building an ideal Lead Measurement system.

Compared to e-commerce sites, lead tracking systems are far more complex and difficult to monitor. Typically, tracking is done only based on event counts. The real criteria that drive lead completion and identify potential leads are often overlooked. Feeding different third-party applications and advertising channels to target the right audience is the only way to acquire potential customers.

For this reason, today we will examine where we can make improvements — from data collection to analysis.

First, let's talk about what the ideal flow should look like on a website.

• From the moment a visitor arrives on the site, their interactions are captured and stored in a data hub layer.

• When a visitor fills out a form, two things happen simultaneously. First, a Form Submit event is triggered and recorded on the analytics side. Second, a lead record is created for the user on the CRM & Backend side.

• The Form Submit event is defined as a Lead Conversion via sGTM. Conversion data can be filtered, enriched, and sent to third-party platforms through sGTM.

Let's examine these steps in more detail.

Capturing Visitor Actions

When a new user arrives on the site, you need to capture data such as the user's source, platform, etc., and then associate this data with the visitor's other behaviors.

Let's review the ideal measurement and data flow together.

• The source (source-medium) information of the incoming user should be stored in a server-side data hub.

• User interactions are also transmitted and stored on the server without relying on third-party scripts.

• This way, user source information and user interactions are correlated and routed to third-party platforms by the server.

The following parameters may be needed for projects such as better retargeting of users and building accurate segments and models:

UTM Parameters: source, medium, campaign information

Consent Status: Tracking consent permissions with user permissions in mind

User Data: device, platform, browser, OS, landing page, etc.

Capturing User Information During Form Events

For every visitor who fills out a form on the site, the dataLayer parameters must be complete to capture the necessary information. Creating a dataLayer for form submissions is the first step toward server-based event tracking.

The dataLayer parameters should include email and phone number. This data is used for two critical purposes. First, Enhanced Conversions / Advanced Matching is performed on advertising platforms for leads, improving attribution accuracy. Second, the lead's status at later stages can be correctly associated with the right user.

When user data reaches sGTM, it can be hashed with SHA-256 before being sent to third-party platforms. Processing and hashing data at the server layer prevents personal data from reaching third-party platforms in plain text and strengthens privacy compliance.

Segmentation and Analysis Data

If your lead form contains data that can be used for segmentation and analysis, it should be added to the dataLayer and event parameters. These are captured as Custom Parameters and can be sent to both analytics platforms and advertising platforms.

As an example, let's create a basic dataLayer for a company looking to receive a service.

The parameters we can capture: event_name, lead_id, lead_type, company_size, company_name, user_data (email, phone).

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

window.dataLayer.push({
  event: "lead_form_submit",
  lead_id: "LD-2024-78542",
  lead_type: "company",
  company_size: "50-100",
  company_name: "Hardal Digital",
  user_data: {
    email: "info@hardaldigital.com",
    phone_number: "+905321234567"
  }
});

With the example dataLayer we created, we set up the necessary information. For users who trigger the form event, this information is collected via the dataLayer, sent first to the server and then to third-party platforms to enrich the conversion.

Sending Customer Status Updates to Platforms via sGTM

Tracking only form submissions is not a case that improves advertising platforms. No platform can determine which leads actually convert based solely on form and similar events. This situation leads to also targeting lost users who filled out a form but whose intent we cannot predict.

Sending this information to advertising platforms via sGTM is the best option in terms of both workload and cost. There is no need to use different API endpoints for each platform or build separate integrations from scratch.

Platform Conversion Windows: Critical Limitations

Each platform has a maximum time window for accepting retroactive conversions, and these limits must be taken into account when sending data via sGTM.

GA4 Measurement Protocol: A lead can be recorded up to a maximum of 72 hours after the original interaction.

Google Ads: Accepts conversions up to 90 days after the interaction.

Meta Ads: Accepts conversion data only up to 7 days after the event occurs.

If the lead status can be assigned quickly — within a few minutes or at most 72 hours — conversion data can be seamlessly transmitted via sGTM to GA4, Google Ads, Meta, and all other platforms.

However, if your business's lead processing cycle spans days, weeks, or months, you will encounter these window limitations. In this case, identify the strongest quality signal that can be obtained within each platform's maximum conversion window. This signal could be a qualified lead status, a scheduled meeting, an accepted application, or any intermediate stage that indicates lead quality.

In conclusion, when any link in this chain breaks, results are directly impacted: a missing lead_id increases duplicate counts, unhashed user data amplifies privacy risks, a status update that misses the platform conversion window resets the optimization signal, and budget decisions made without internal attribution remain guesswork.