Full Answer

The Safari direct traffic problem is one of the most financially damaging attribution gaps in e-commerce, and understanding the exact mechanism reveals why it cannot be solved with client-side tracking alone.

The sequence works like this: a customer clicks a Facebook ad on Monday, lands on your WooCommerce store, and Safari sets a first-party cookie storing the traffic source. Because the click came from a classified tracking domain, Safari's ITP restricts that cookie to a 24-hour lifespan. When the customer returns on Thursday to complete their purchase, the cookie is gone. GA4 receives a session with no stored identifier, no utm parameters, and no referrer header — so the platform defaults to direct.

The financial impact is that your Facebook Ads Manager shows fewer conversions, your ROAS calculation drops, and algorithm-based bidding optimises against incomplete data. Meanwhile, your GA4 direct traffic channel inflates, masking the true performance of paid acquisition channels.

The scale of this problem depends on three variables: your Safari traffic percentage (25-45% in most English-speaking markets), your average time-to-purchase (longer cycles lose more), and how many of your paid channels are classified by ITP. Google, Facebook, TikTok, and most major ad platforms are all classified.

Server-side tracking solves this by capturing the original traffic source at the server level during the first visit and maintaining that attribution data independently of browser cookies. When the customer returns days later, your server matches the session to the original source regardless of what Safari has done to the cookie.