single php
cdp menu

Improve Attribution with 1P Domain Tracking in Meta and Google Ads



Everyone knows third-party cookies can no longer be used for retargeting users. They’re dead.

But it doesn’t stop there. Even the first-party cookies are at stake. 

With the Intelligent Tracking Prevention 2.3 version upgrade (ITP 2.3), first-party cookies set from a different domain (not the user’s first-party domain) will be automatically deleted after 7 days by browsers like Safari and Firefox.

When these cookies expire, you’ll have a short window for attribution. As you might have noticed FB defaults attribution to 7 days.

Similarly, the GA4 also reports a high number of new users due to the fact the cookies expire after 7 days.

The other scenario was when we wanted to reach out to more abandoned carts via email, sms, or whatsapp campaigns. Since those cookies expire we won’t be able to reach out to more people.

However, when the first-party cookies are set from the server-side they are retained for one year.

1P domain tracking simply involves tracking website visitors and setting cookies for them on the server-side from the first-party domain.

For example, when a user visits the domain the cookie should be set from the domain or sub-domains such as or

But here’s an important point: These sub-domains and shouldn’t be mapped using CNAME to another domain If they are, the cookie will still be deleted in 7 days. However, subdomains can be mapped using CNAME within the same domain or to other subdomains to avoid cookie deletion limitations. 

By setting the cookie from the same domain or subdomains (first-party domain), the cookie lifespan is extended for a longer period. 

While setting this up might require some technical expertise, our new update – 1P domain tracking – simplifies the process and extends the lifespan of your cookies

Imagine a user visits your website by clicking on a Paid Ad. A first-party cookie (from client-side/from a different domain) is assigned to that user. The user leaves the website and doesn’t come back for seven days. The first-party cookie assigned to that user is deleted by the browser, say Safari, after 7 days.

Now, the same user visits again on the 8th day through the direct channel. Since the old cookie was deleted by the browser, the user is assigned a new first-party cookie.

infographic showing how first-party cookie is being deleted without 1p domain tracking

The user then makes a conversion (e.g., purchase) during this session. However, this conversion is attributed to the direct channel, not the Paid Ad that initially brought the user to your website. This is because all external IDs (FBCLID, GCLID, etc.) are lost after 7 days due to cookie deletion.

That’s why setting the first-party cookie from the first-party domain (server-side) is crucial for accurate conversion attribution without missing any interactions.

But the benefits don’t stop here..

With 1P domain tracking, 

1. Enhanced ID resolution

With an extended 1P domain cookie lifetime, our ID resolution system, Stitcher appends the external IDs collected across different sessions, and unifies them under a 360-degree profile.

2. Increased conversion attribution accuracy

Conversions happening beyond 7 days can be attributed accurately. Stitcher enables the collection and unification of external IDs, click IDs starting from the user’s first interaction under the lifetime cookie. With this unified information, the right acquisition channel gets the credit and you avoid losing out on costs.

infographic showing how first-party cookie is retained beyond 7 days with 1p domain tracking

70% lift in ROAS in Meta(FB) Ads

14 days after going live with 1P domain tracking, one of our customers is seeing a 70% lift in ROAS due to better attribution inside Meta.

Shopify Default Purchase vs CustomerLabs Purchase Comparison

3. Increased audience match rates

With the lifetime cookie, we can append all the external IDs and other additional information across different user sessions. This helps identify users on ad platforms like Google Ads, Meta Ads, and TikTok Ads, significantly increasing audience match rates.

Reap the benefits with our one-time setup of 1P domain tracking and preserve your user cookies for a longer period of time.

Get started with 1P domain tracking

Frequently Asked Questions (FAQs)

1P domain tracking is a server-side tracking feature that collects the user data using a lifetime cookie to store the data beyond 7 days. The tracking is done by the same domain that hosts the website instead of another third-party domain. For example, is tracked using the domain or and not
A first-party domain or 1P domain is the same domain where the website that the user visits is hosted. It matches exactly with the domain name, but can also be a sub domain. For example, is a domain, and the sub-domains,, come under first-party domains. will be a third-party domain.
With 1P domain tracking, the first-party cookie is set from the same domain (server-side). Even in browsers like Safari, where the cookie is automatically deleted, you can still identify the user and unify their data beyond 7 days. The 1P cookie is almost a lifetime cookie, helping you attribute conversions accurately

The latest news, perspectives, and insights from CustomerLabs

More Blogs

View all
What is First-party Data? | Comprehensive Guide

First-party data is the data collected by organizations from the user directly in compliance with GDPR, CCPA etc. for your marketing needs

Read more
The image is the blog banner with the text Implement Google Consent Mode V2 to save your audience signals. It also has a graphic that shows how Google consent mode has flags user data and personalization and how Google is shielding and providing privacy to the users through the consent mode
Implement Google Consent Mode v2

Google consent mode v2 has new parameters ad_user_data ; ad_personalization that lets tags collect more signals and sync it with Google Ads

Read more
The blog banner shows an infographic where GCLID WBRAID & GBRAID parameters are synced with Google Ads
What are GCLID, GBRAID and WBRAID parameters?

GCLID parameter lets Google ads track the conversion from non iOS devices. WBRAID and GBRAID parameters help track metrics from iOS device

Read more

Get started with CustomerLabs CDP

Schedule a 1-1 Demo


Unified data to boost ecommerce growth


Engage your customers across the funnel with a unified martech stack


Increase product metrics with a unified martech stack


Scale your customers quickly with the right data