Skip to main content

Google Analytics (GA4)

Overview JamLoop integrates with Google Analytics (GA4) to make JamLoop-driven attribution visible directly inside the analytics platform your team already uses.

Updated over a week ago

Channels like Connected TV (CTV) don’t generate clicks, which makes them difficult to measure in traditional web analytics. By logging JamLoop-attributed view-through conversions, customers can view traffic from CTV campaigns alongside search, social, affiliate and other paid-digital traffic sources using GA’s native reporting.

Through this integration, JamLoop sends JamLoop-attributed events into your GA4 property, including upper-funnel activity like attributed visits as well as downstream engagement and commerce events such as form-fills, add-to-carts, registrations and purchases.

For full documentation on JamLoop attribution methodology, visit: JamLoop Attribution Methodology

What Is GA4?

Google Analytics 4 (GA4) is Google’s current analytics platform, designed to measure user behavior across websites and apps using an event-based model.

GA4 is also built to support:

  • Cross-device journeys

  • Flexible attribution models (data-driven, last click, etc.)

  • Server-side event ingestion (important for CTV)

Most advertisers already rely on GA4 to answer questions like:

  • What sources are driving traffic to my site?

  • Which channels influenced conversions?

  • How do channels work together across the funnel?

JamLoop’s GA4 integration plugs CTV advertising into that same framework.

How the Integration Works

GA4 supports server-side event ingestion via its Measurement Protocol API. This means events can be sent directly from JamLoop’s servers instead of relying on the user’s browser.

This capability is what makes non-click channels like CTV compatible with GA4.

At a high level:

  1. A viewer sees a JamLoop CTV ad

  2. The viewer later visits your website

  3. JamLoop attributes the visit as CTV-driven

  4. JamLoop sends a “CTV visit” event to GA4

What JamLoop Sends to GA4

When JamLoop verifies that a user who was exposed to a JamLoop campaign later completes an action on your website, JamLoop sends an event into GA4 using Google’s Measurement Protocol API.

These events allow JamLoop-driven activity to appear inside GA4 reports alongside your other marketing channels.

Each event includes the following technical identifiers required by Google Analytics:

  • client_id: Identifies the user. This is read using GA’s SDK so GA4 can associate the event with the correct user profile

  • session_id: Groups activity into a single browsing session within GA4.

  • timestamp: The precise time the event occurred.

  • engagement_time_msec: Required by GA4 so the event is counted as a valid session interaction

JamLoop may send events representing both upper-funnel and downstream activity, including:

  • Visits

  • Product-views, Add-to-carts

  • Purchases, Form-Fills, Registrations or other conversion events

Because the events use GA4’s own identifiers, they appear within the same session GA4 is already tracking.

How JamLoop Handles Other Traffic Sources

JamLoop is designed to complement your existing analytics ecosystem, not replace it. In most cases, JamLoop defers to clear click-based attribution from other marketing channels.

However, search traffic is treated differently because searching for a brand is one of the most common ways consumers respond to TV and video advertising.

Search Traffic May Be Attributed to JamLoop

When a user sees a JamLoop campaign and later searches for the advertiser’s brand, they may click:

  • An organic search result

  • A paid search ad

Even though the visit technically arrives via search (e.g., source=google / medium=organic or medium=cpc), the intent was likely driven by the prior JamLoop campaign exposure.

For this reason, JamLoop attributes those conversions to JamLoop and sends the event to GA4.

We Defer to Other Click-Based Channels

For other digital channels where a specific campaign click drove the visit, JamLoop does not overwrite attribution

Examples include:

  • Social platforms (Meta, TikTok, LinkedIn)

  • Affiliate links (unpaid digital traffic e.g. blog post or news article)

  • Email campaigns (e.g., Klayvio)

  • Any link containing UTMs identifying another marketing source

Note: This behavior applies specifically to how events are sent to GA4. Within the JamLoop web application, attribution is calculated independently and may still credit JamLoop exposures even when another digital channel delivered the final click.

This reflects a common reality in video and TV advertising: a viewer may see a CTV campaign, become aware of the brand, and later click a social ad to respond. Because Google Analytics is fundamentally built around last-touch attribution, JamLoop will defer to those click signals when logging events in GA4 to ensure compatibility with Google’s reporting model.

What JamLoop Does Not Send to GA4

No Personally identifiable information (PII)

JamLoop never sends personally identifiable information to GA4.

This includes:

  • Email address

  • Phone numbers

  • Names

  • Any other personal identifiers

All events rely only on anonymous GA identifiers such as client_id and session_id

What You’ll See in GA4

After setup, JamLoop-driven traffic will appear in GA4 under:

Reports → Acquisition → Traffic acquisition

Break down by Session source / medium

Typical values:

  • Source: jamloop

  • Medium: ctv

    • Other mediums available through JamLoop: olv, dsy, pau, aud

Data may take 24–72 hours to appear after initial setup.

What You’ll Need Before You Start

  1. Click Admin.

  2. Click Data streams

4. Click the web data stream.

:globe_with_meridians:

5. Copy the Measurement ID in the top right. Create and copy a new Measurement Protocol API Secret


How to Connect GA4 in JamLoop (Step-by-Step)

  1. Log into the JamLoop App

  2. Navigate to Pixel Config

  3. Select Connect Google Analytics 4

  4. Enter:

    • GA4 Measurement ID

    • GA4 API Secret

  5. Save your settings

Once connected, JamLoop will automatically begin sending verified CTV visit events to GA4.


Recommended GA4 Settings

To ensure CTV appears correctly in reporting, we recommend reviewing:

  • Attribution model: Data-driven (common default)

  • Channels eligible for credit: Paid & organic

  • Lookback windows:

    • Acquisition: ~30 days

    • Other key events: ~90 days

No custom events or goals are required.


What Success Looks Like

A fully successful setup means:

  • JamLoop campaigns are live

  • Web pixel is installed

  • GA4 is connected

  • CTV-driven sessions appear as jamloop / ctv in GA4

  • Conversions in GA4 reflect CTV influence

  • JamLoop and GA4 reporting can be compared confidently

Did this answer your question?