Recognise returning visitors for up to 400 days

GA4's standard JavaScript tags already use first-party cookies. Cromojo brings a custom tracking domain, a server-set visitor cookie and supported Shopify/Stripe revenue connections into one guided setup. You can connect eligible repeat visits to purchases without operating a separate tagging server.

When a visitor returns on the same browser, Cromojo can recognise them and use that identity with supported checkout data to connect visits across sessions. This helps explain purchases that happen after the first visit. Attribution depends on visitor recognition, consent and your checkout integration.

First-party tracking is included with Analytics Pro and above. You can configure returning visitor tracking and your custom tracking domain in Site settings > Analytics.

Yes. With the relevant revenue integration connected, the Cromojo snippet passes visitor information through Shopify carts and supported Stripe Payment Links and Pricing Tables. If you create Stripe Checkout sessions on your server, pass Cromojo's checkout reference when creating the session.

Enable returning visitor tracking, then add a subdomain such as stats.yourdomain.com in Site settings > Analytics. Add the DNS record shown, wait for the address and HTTPS certificate to become active, then replace your website's snippet with the updated one. Your existing snippet does not switch automatically.

Returning visitor tracking uses cookies and browser storage. In opt-in mode, visitors must accept through your connected cookie banner before recognition starts. Opt-out mode recognises visitors unless they opt out. Choose the mode that fits your consent requirements; a custom domain does not remove them.

No. A custom domain can avoid blocks aimed at shared analytics domains, but blockers may still recognise the script or request path. Recognition applies to the same browser and depends on its stored visitor ID. It does not automatically connect different browsers or devices.

Cromojo sets a rolling cookie lifetime of up to 400 days. The seven-day comparison refers to Safari's limits on JavaScript-created cookies and storage after a period without interaction, which can affect standard GA4 tracking. It is not a universal limit for GA4 or third-party analytics. Safari can also cap server-set cookies on custom domains at seven days. Actual recognition depends on the browser, domain setup, consent and stored data; 400 days is a maximum, not a guarantee.