---
title: "Solving the 'direct traffic' problem | Cometly Academy"
description: "Most B2B SaaS teams running paid ads see 50–70% of their attribution land in 'Direct' or 'Unknown'. That’s not your traffic mix — it’s a tracking gap. The Comet Pixel uses cookieless first-party fingerprint tracking that survives ad blockers, OAuth redirects, Calendly iframes, and 90-day sales cycles, typically pulling the direct bucket down to 5–10%."
source: "https://www.cometly.com/academy/solving-the-direct-traffic-problem"
---

# Solving the 'direct traffic' problem

Recovering the 60% of journeys your CRM lost.

- Module 01: Foundations
- Lesson: 1.4
- Track: Both
- Format: Playbook
- Read time: 9 min

Most B2B SaaS teams running paid ads see 50–70% of their attribution land in 'Direct' or 'Unknown'. That’s not your traffic mix — it’s a tracking gap. The Comet Pixel uses cookieless first-party fingerprint tracking that survives ad blockers, OAuth redirects, Calendly iframes, and 90-day sales cycles, typically pulling the direct bucket down to 5–10%.

## Key takeaways

- First-party fingerprint stitches sessions across IP, device, and browser
- Cross-device tracking links a mobile click to a desktop demo to an email follow-up
- Cross-domain tracking maintains source data when users move from your marketing site to your app
- UTMs survive Calendly bookings when you redirect to a thank-you page on your domain
- OAuth flows (Google, Microsoft sign-in) no longer break the journey

When more than half of your conversions show up as 'direct,' the simplest interpretation is that your tracking is broken — not that 60% of your customers magically remembered your URL. Solving this problem is usually the single highest-leverage attribution improvement a B2B SaaS team can make.

## Why it matters

Direct traffic is mostly a measurement artifact. It happens because UTMs were stripped, cookies expired, the visitor was on a privacy-restricted browser, or the journey crossed a domain or an iframe boundary that broke the session. Until you fix it, every channel-level decision is being made against a corrupted dataset.

## Where direct traffic actually comes from

There are five common reasons a real ad-driven journey ends up tagged as direct: a long sales cycle that exceeds the cookie lifetime, an iframe-based booking tool like Calendly that strips UTMs, an OAuth flow (Google or Microsoft sign-in) that drops the referrer, ad blockers or ITP killing the third-party pixel, or the visitor moving from your marketing site to your app on a different domain.

Cometly’s pixel uses first-party fingerprint identifiers (IP, device characteristics, browser fingerprint, and any first-party identifiers like email when available) to bridge sessions across all of these failure modes.

## The fix, in order of impact

The order to attack these problems matters. Start with the largest source of leakage in your funnel — usually the booking flow or app sign-up — and work outward.

- Install the Comet Pixel on every page across both your marketing site and your app
- Configure Calendly (or your scheduler) to redirect to a thank-you page on your domain
- Enable cross-domain tracking between your marketing site and app subdomain
- Capture click IDs (`fbclid`, `gclid`, `li_fat_id`) as hidden fields on every form
- Verify the pixel is firing post-OAuth on app sign-up flows

## Common pitfalls

### Assuming direct traffic is real intent

Most of it isn’t. Treat it as missing data and instrument until it shrinks below 10% of total attribution.

### Skipping cross-domain tracking

The marketing site → app handoff is the single biggest source of attribution loss for PLG SaaS. Don’t skip it.

### Using only third-party cookies

Safari, Firefox, and most privacy plugins block third-party cookies entirely. First-party fingerprint is the only durable approach.

### Trusting GA4’s 'Direct / None' bucket

GA4’s direct attribution is even worse than ad-platform attribution because it can’t see most ad clicks at all. Don’t use it as the source of truth.