top of page
Typographic Black and Blue.png

OneSignal + Meta Ads — Push Audiences That Become Paid-Media Lookalikes

Push subscribers are an underused asset on Indian D2C ad accounts. They've opted in to hear from you, they're engaged enough to allow push notifications, and most are already buyers. Meta Ads has no idea they exist.


OneSignal is the default push platform for Indian D2C brands running web + mobile. Sync OneSignal subscribers and engagement segments into Meta Custom Audiences and you unlock a high-intent lookalike seed — typically delivering 30-50% lower prospecting CPA than generic purchase-based lookalikes.


Why Push Subscribers Make Strong Meta Audiences


  • Self-selected high intent. Push opt-in is a meaningful commitment versus passive web visitor.

  • Engaged behaviour signal. Push-engaged users (open rate > 0%) signal active brand attention.

  • Cross-device identity. OneSignal stitches web push, mobile push, and known users into one profile.

  • Bigger pool than email opt-in. Push opt-in rates in India run 35-50%, versus email opt-in around 15-25%.

  • Hashed identifier export. Compatible with Meta's match requirements.


Architecture: Two Sync Patterns


Pattern 1: OneSignal Segments → Meta Custom Audiences


OneSignal's Meta Audiences integration pushes subscriber segments (hashed email/phone where collected) to Meta. Daily refresh. Setup: 60-90 minutes. Best for: engaged subscribers, push-engaged-last-30-days, recently-active.


Pattern 2: OneSignal Engagement Events → Meta CAPI


Engagement events (Push Sent, Push Opened, Push Clicked) stream to Meta CAPI via webhook → Worker. Setup: 4-6 hours. Best for: brands wanting real-time engagement-based retargeting.


Setup: Pattern 1


  1. In OneSignal, build three segments: `Push Engaged Last 30 Days` (opened ≥ 1 push), `All Subscribers > 30 Days`, `Recently Subscribed < 7 Days`.

  2. OneSignal Dashboard → Settings → Integrations → Facebook Audiences. Connect Meta Business.

  3. Map identifier fields: hashed email (em), hashed phone (ph) where collected via tags.

  4. Enable daily sync per segment.

  5. Validate in Meta Audiences Manager — audience populates within 24 hours.


Once audiences are live, two immediate use cases:


  • Build a 1% lookalike off `Push Engaged Last 30 Days` — strong prospecting seed.

  • Retarget `Recently Subscribed < 7 Days` with conversion-focused first-purchase creative.


Pattern 2: Engagement Event Stream


  • OneSignal webhooks fire on Push Opened and Push Clicked events.

  • Cloudflare Worker filters and enriches with user-level data from your DB.

  • Worker hashes user-data fields, generates event_id, ships to Meta CAPI.

  • Dedupe with web Pixel events via shared event_id where applicable.

  • Validate in Meta Events Manager — EMQ ≥ 8.0.


Full Meta CAPI mechanics in our [CAPI complete guide](https://www.wittelsbach.ai/post/conversion-api-capi-for-meta-ads-complete-india-d2c-setup-guide).


Match Rate Considerations for OneSignal


OneSignal's data model is push-first, not customer-first. By default, OneSignal collects a player ID per device — not an email or phone. To make subscribers match-ready for Meta:


  1. Set External User ID = your Shopify customer_id at OneSignal init.

  2. Set tags `email` and `phone_number` when users provide them.

  3. On checkout or login, update OneSignal subscriber with hashed email/phone.

  4. Run a one-time backfill if your historical subscribers don't have email/phone tags.


Without this, OneSignal-Meta match rates run at 15-30%. With it, expect 60-75% match rates — meaningful audience size for lookalikes.


Common Mistakes


  • Syncing all subscribers in one big audience. Defeats the purpose — too generic. Sync engaged subsets.

  • Forgetting to tag email and phone in OneSignal. Match rate collapses to single digits.

  • Ignoring push opt-out signals. If a user unsubscribes from push, exclude from related Meta audiences. Respect the signal.

  • Building lookalikes off `All Push Subscribers`. Lower-quality seed. Always use engaged subsets.

  • Not consent-gating. DPDP Act requires marketing consent — push opt-in is not equivalent to ad-marketing consent. Verify with your DPO.


What Indian D2C Brands Typically See


  • Push-engaged lookalike CPA: 30-50% lower than generic purchase-based lookalikes (assuming clean tagging and consent).

  • Recent-subscriber retargeting CPA: 40-60% lower than generic site-engaged retargeting.

  • Audience size: depends on push opt-in rate, typically 50K-500K subscribers for ₹10-50Cr ARR brands — enough for stable lookalike performance.


How Wittelsbach AI Spots Underused Push Audiences


Bach AI scans your Meta audiences against your subscriber base and flags missing push-engaged segments, unused lookalike seeds, and the ₹ revenue gap of not activating them. One-click recommendations for each. Try Bach AI on your account at [app.wittelsbach.ai](https://app.wittelsbach.ai).


Frequently Asked Questions


Is OneSignal the right push platform for Indian D2C?


For brands focused on web push + mobile push without heavy lifecycle needs, yes — OneSignal is free up to a generous tier, simple to deploy, and has solid India delivery rates. For brands needing push + email + WhatsApp + SMS in one platform, MoEngage or WebEngage are usually better. The Meta sync use case alone doesn't justify migrating; pick OneSignal for push capabilities first, take the Meta sync as a bonus.


How do I improve OneSignal-to-Meta match rates?


Tag email and phone on every OneSignal subscriber as early as possible — on signup, login, or checkout. Without tagged identifiers, OneSignal can only export player_ids, which Meta can't match. Brands that tag aggressively see 60-75% match rates. Brands that don't see 15-30%. The difference is the gap between a usable Meta audience and one too small to matter. Run a one-time backfill for historical subscribers using Shopify customer_id as the join key.


How do I handle DPDP Act consent for push-to-ads sync?


Push opt-in is not equivalent to ad-marketing consent under DPDP Act. Track a separate `marketing_consent` attribute in OneSignal (set when the user opts in at signup or checkout). Filter every Meta-bound segment against this flag. If a user opts in to push but declines marketing consent, exclude them from Meta sync. Conservative interpretation, but defensible — DPDP is new and enforcement details will tighten.


Can I use push-engaged audiences for both prospecting and retargeting?


Yes, but separately. Use the lookalike of push-engaged users for prospecting (Meta finds new users with similar profiles). Use the push-engaged audience itself for retargeting — they already know your brand, the message and creative should be conversion-focused, not introduction. Don't combine them into a single campaign or you'll get confused delivery — Meta won't know if it's prospecting or retargeting.


What's the typical setup time and ROI?


Pattern 1 is 60-90 minutes plus backfilling identifier tags (which can take a day if you have a large historical subscriber base). Pattern 2 adds 4-6 engineering hours. Indian D2C brands typically see 0.3-0.7x ROAS lift within 60 days from push-engaged lookalikes alone. At ₹15L/month spend, that's ₹4.5-10L/month in incremental revenue. The lookalike performance peaks around day 21 as Meta absorbs the new seed.

Comments

bottom of page