Home / Use cases / Paid social

Paid social5 min read · Playbook

Retarget the people who left your site — on Meta, not just email

Most retargeting only reaches the sliver of visitors who gave you an email or triggered a pixel event. Here's how paid social teams reach the other 98%.

The gap in standard retargeting

Meta's pixel is excellent at tracking behavior, but it can only build an audience out of visitors it can already see doing something trackable — a purchase, an add-to-cart, a form fill. Everyone who scrolled, read, and left without triggering an event just disappears from the retargeting pool.

What identity resolution adds

IntentCurrent's Retarget engine runs alongside your existing pixel. It resolves a portion of your anonymous visitors into real people — name, email, phone, and company where there's a confident match — and rebuilds them into a Meta custom audience automatically, refreshed daily.

What this looks like in practice

For example: a home-services business running ads sees thousands of monthly site visitors and a much smaller number of form fills. Under a standard pixel, only those form-fillers ever get retargeted. With identity resolution added, a real chunk of the visitors your pixel alone would never catch becomes reachable again — the same ad spend now works against a bigger, still-relevant audience.

Where this fits your stack

This runs alongside — not instead of — your existing pixel and standard retargeting. It's an additional, complementary audience source layered onto what you already have working.

You already paid for that traffic once. This is what gets you a second look at most of it.

Key takeaways

  • Runs alongside your existing Meta pixel — doesn't replace it
  • Refreshed daily, not a one-time upload
  • Best paired with your highest-traffic, highest-intent pages

See it on your own site

Fifteen minutes. We'll show you the intent records and identified visitors you're currently missing.

Book a 30-min data audit →

Quick questions

Does this replace my Meta pixel?
No — it runs alongside it. Your existing pixel and standard events keep working exactly as they do now; this adds an additional identity-based audience on top.
How fresh is the audience?
Refreshed daily as new visitors are identified.