First-party-attributed ad recommendations
Last updated 2026-06-21
Definition
First-party-attributed ad recommendations correct what the ad platform reports with what actually happened in your own tools. Quri joins your GA4 traffic, PostHog conversions, and Shopify orders onto each campaign, so a Meta “4× ROAS” is re-checked against real revenue before Quri suggests a move or reallocates budget — recommendations built on your data, not the platform’s.
How to do this in Quri
- Connect Meta or Google ads plus GA4, PostHog, or Shopify so Quri can see spend and real outcomes.
- Open /app/ads/recommendations — the suggestions use platform numbers corrected by your data.
- Look for the chip naming which of your sources — GA4, PostHog, Shopify — is feeding the recs.
- The same first-party basis drives the budget optimiser at /app/ads/optimizer.
Frequently asked
- Why does Quri’s ROAS differ from what Meta shows me?
- Meta counts conversions it attributes to itself; Quri re-checks against your GA4, PostHog, and Shopify, so its ROAS reflects revenue that actually landed in your store, not the platform’s self-credited number.
- Does this use PostHog too?
- Yes. PostHog purchase events are now folded in alongside GA4 and Shopify, joined by each campaign’s utm_campaign. When a campaign appears in more than one source the most authoritative wins — Shopify orders over PostHog over GA4 — so the same purchase is never counted twice.