Is retargeting still worth it after iOS privacy changes?

Yes, but only for audiences you can actually reach and measure. First-party audiences built from your own site, CRM and server-side events still convert well. Broad platform-inferred lookalikes have degraded the most and need to be tested, not assumed.

What is a good retargeting ROAS in India?

Cart abandoners and past purchasers typically return 6x to 12x+ ROAS. Product viewers and content engagers sit closer to 3x to 6x. Anything below 2x on a warm audience usually means the exclusion or frequency rules are broken, not that retargeting has stopped working.

How do I set up server-side tracking for retargeting?

Run a server-side container (server-side GTM or the platform's own conversions API) alongside your pixel, send deduplicated events with a shared event ID, and match on hashed first-party identifiers like email and phone. NPR Design sets this up as part of any performance retainer that includes retargeting.

Retargeting in 2026: What Still Works After the Signal Loss

The complaint we hear most about retargeting in 2026 is that it "stopped working." It didn't stop working it stopped being free. The audiences that used to build themselves off a pixel now need first-party data and server-side plumbing to reach the same accuracy. Do that work and retargeting is still the highest-ROAS line in most accounts we run.

Audience-by-audience: what still delivers

Ranges below are what we typically see across Indian D2C and lead-gen accounts once server-side tracking is in place and exclusions are set correctly.

Cart / lead-form abandoners (0–3 days)

Highest-intent audience in the account. Server-side event required since many of these visitors block third-party cookies. Triggered within an hour of drop-off.

8–14×

Past purchasers (repeat / replenishment window)

Timed to typical reorder cycle for the category. Works best matched via CRM email/phone upload rather than pixel-only.

6–12×

Product page viewers, no add-to-cart (7–14 days)

Still valuable but decays fast after two weeks. Needs frequency capping or it turns into an annoyance, not a nudge.

3–6×

Video / content engagers (75%+ view, no site visit)

Warms cold traffic toward a site visit. Treat as upper-funnel; measure assisted conversions, not last-click ROAS.

2–4×

Email / CRM list matches (non-buyers)

Your best first-party asset. Match rates depend entirely on data hygiene clean, deduplicated lists match far better than raw exports.

4–9×

Platform-inferred lookalikes seeded from retargeting

The audience type hit hardest by signal loss. Test in isolation with a capped budget; don't assume it performs like it did in 2021.

1.5–3×

Server-side setup, non-negotiable in 2026

Server-side container. Run server-side GTM or the platform's native Conversions API alongside the browser pixel, not instead of it.
Deduplication. Send a shared event ID from browser and server events so the platform doesn't double-count a single conversion.
First-party identity matching. Hash and send email and phone on every event you can server-side match rates are consistently better than pixel-only.
CRM sync. Push purchase and lead status back into the ad platform on a schedule (daily minimum) so exclusion audiences stay current.

Frequency and exclusion rules that prevent waste

Most retargeting waste isn't a bad audience it's a good audience with no rules.

Cap frequency at 4–6 per week per audience. Past that, CTR drops and cost per result climbs with no offsetting lift.
Exclude converters immediately. Sync purchase/lead events so buyers drop out of the pool within hours, not days.
Set a hard audience age-out. Product viewers older than 30 days rarely convert at a profitable rate; move them to a cold or lookalike pool instead.
Separate creative by recency. A 1-day abandoner should see the exact product with an urgency message; a 20-day viewer should see a broader offer or social proof.

Retargeting waste is almost never the audience. It's the account still running a rule set built for a pixel that no longer sees everything.

What we'd set up in your account this month

Audit pixel + Conversions API coverage and fix deduplication gaps.
Rebuild the audience list around the six segments above, with explicit exclusions.
Set frequency caps per audience and retire anything past 30 days stale.
Match creative recency to audience recency instead of running one ad across every pool.

None of this needs new budget. It's usually a reallocation, and it's where the honest ROAS in the account already is.

Retargeting in 2026: what still works after the signal loss

Audience-by-audience: what still delivers

Server-side setup, non-negotiable in 2026

Frequency and exclusion rules that prevent waste

What we'd set up in your account this month