Visit Website →
← Back to blog

22.9% Push Conversion: iOS Focus and App Clip Push for Ecommerce

October 6, 2026
22.9% Push Conversion: iOS Focus and App Clip Push for Ecommerce

Yes, iOS Focus modes can silence App Clip push notifications, the same way they silence standard app notifications, unless the notification qualifies as Time Sensitive, counts as an allowed Communication notification, or the app sits on a user's allowed list. For cart-recovery campaigns, that means a chunk of your standard marketing pushes will get delayed, bundled into a Notification Summary, or held back entirely while a shopper has Focus turned on.

TL;DR:

  • Most App Clip notifications are subject to the same Focus and Notification Summary filtering rules as regular app notifications, unless marked as Time Sensitive or communication alerts.
  • Push interruptions depend heavily on the payload's interruption level, with standard (passive or active) being silenced easily, while Time Sensitive and communication notifications can break through Focus restrictions.
  • Driving Focus universally blocks app notifications, including marketing pushes, until the mode ends, which can significantly delay cart recovery efforts.
  • Sending targeted, behavior-triggered push messages shortly after cart abandonment and avoiding misuse of urgency labels improves delivery and conversion rates despite Focus delays.
  • Proper technical setup, including setting correct interruption levels and respecting Apple’s restrictions, is vital for accurate attribution and long-term campaign success.
StorePush
Recover More Abandoned Carts
StorePush uses native iOS App Clips to re-engage shoppers through lock screen push notifications, even without email or phone data.
Visit StorePush

Table of Contents

How iOS treats App Clip notifications, interruption levels, and Notification Summary

Apple does not give App Clips a free pass around its notification system. Once a shopper invokes your App Clip and grants permission, the notification you send is filtered through the exact same rules that apply to any installed app, according to Apple Support's Focus documentation. Focus and Notification Summary sit on top of that filtering layer, deciding in real time whether a push reaches the lock screen now, later, or not at all.

The deciding factor is the interruption level attached to the push payload:

  • Passive or active (default): treated as standard priority, easy to silence under an active Focus.
  • Time Sensitive: can break through Focus when the user hasn't explicitly blocked it, reserved for genuinely urgent updates.
  • Communication notifications: can interrupt Focus when the app has authorization and the metadata identifies a real person-to-person exchange, as described in Apple's developer documentation on communication notifications.

Notification Summary adds a second filter on top of Focus: notifications tagged as non-urgent can get queued and delivered later in a scheduled digest rather than the moment you send them.

What different Focus modes mean in practice

What different Focus modes mean in practice — overview diagram

Every Focus mode works from an allow or silence list the user builds, and that list decides whether your push shows up on the lock screen immediately, gets bundled into Notification Center, or disappears into a later summary. Work, Personal, and Sleep Focus modes are flexible: a shopper can choose to allow your store's App Clip notifications through, and many will if they opted in with clear intent.

Driving Focus is different. It's a system-controlled mode built with safety partners, and it generally blocks app notifications from breaking through no matter how the app is categorized, based on discussion in Apple's support community. A cart-recovery push sent while someone is driving typically sits unseen until the mode ends.

  • Allowed apps: notification appears on the lock screen as normal.
  • Silenced apps: notification is delivered quietly to Notification Center, no banner, no sound.
  • Driving Focus: notifications are held back almost universally, regardless of interruption level.

One figure worth internalizing: push notifications convert shoppers at roughly 22.9% compared to 5.6% to 9% for email recovery flows, based on StorePush's own campaign data, which is exactly why Focus-driven delivery delays matter so much to your recovery math.

Marketing best practices for timing, content, and permission

Respecting Focus controls isn't a compliance chore, it's a conversion strategy. A push that lands at the right moment with the right message outperforms a higher volume of generic blasts, and that's doubly true once you factor in how many of your sends get filtered by Focus before a shopper even sees them.

  1. Trigger on behavior, not a schedule. Send the cart-recovery push shortly after abandonment, when intent is still warm, rather than batching sends at a fixed hour.
  2. Keep the message short and specific. Mention the item, not a generic "come back" line; shoppers respond to relevance faster than to urgency language.
  3. Ask for permission with a clear reason. A one-line explanation of what the shopper gets (a reminder before the item sells out, not spam) raises opt-in rates, as covered in our guide on raising push notification opt-in rates.
  4. Use progressive prompts. Ask for notification access at the moment of clear value, like right after someone adds to cart, instead of immediately on App Clip launch.
  5. Never force a Time Sensitive or Communication label onto a marketing push. Apple's WWDC guidance on Time Sensitive and Communication notifications is explicit that these classes exist for genuine urgency or person-to-person exchange, and misuse risks App Review rejection or a user revoking permission entirely.

Pro Tip: Test your push copy with Focus enabled on a personal device before launch. If the message still feels worth reading in a scheduled summary hours later, it's doing its job.

Developer checklist: interruption levels, communication capability, and App Clip specifics

Getting the technical setup right keeps your notifications compliant and predictable. Start with the APNs payload itself.

  • Set interruption-level to active for standard marketing and cart-recovery pushes, the honest default for promotional content.
  • Reserve time-sensitive for cases with a real deadline, like a price hold expiring in minutes, and only after enabling the Time Sensitive Notifications entitlement.
  • Enable the communication notifications capability only if your flow involves direct messaging between people, not storefront alerts, per Apple's developer guidance.
  • Review your App Clip's invocation URL and metadata configuration, since discovery and notification permission both depend on a properly registered App Clip experience.
  • Avoid stacking interruption levels or requesting repeated permission prompts to work around a silenced state. Apple's review process and user trust both suffer from that pattern.

Measuring and attributing App Clip push performance

Focus-related delays introduce noise into your delivery data, so your attribution model needs to account for it rather than panic over a slow first hour. A push that was silenced under Focus might still convert once the shopper checks their phone later, and your reporting should credit that sale correctly.

  • Use an attribution window in the P90 to P95 range for click-to-purchase, long enough to catch delayed opens without crediting unrelated return visits.
  • Attach a unique click ID to every push link so conversions tie back to the specific send, not a general session.
  • Track open rate, click-through rate, and revenue separately from delivery timestamp, since a delayed delivery under Focus can still produce a full-price conversion hours later.
  • Treat a spike in "delivered but not opened immediately" as a Focus signal, not a broken campaign, before adjusting your send strategy.

Built around App Clip push: what our data shows

Our core product sends push notifications straight to a shopper's lock screen through a native App Clip, with no email, phone number, or app install required. That matters here because the same Focus and Notification Summary rules this guide covers apply to every App Clip push we send, so we build our timing and attribution models around them rather than ignoring them.

Across campaigns, we see roughly 22.9% push conversion versus 5.6% to 9% for email, and behavioral templates triggered right after cart abandonment generate two to four times more opens than scheduled blasts. We measure every send with a P90 to P95 attribution window and unique click IDs, which keeps revenue credit accurate even when a Focus-silenced push converts hours after it was sent.

Push and email conversion comparison chart

Why respecting Focus is the smarter long game

The instinct to chase every possible delivery trick, mislabeled interruption levels, aggressive permission re-prompts, is understandable and almost always backfires. A shopper who feels pushed too hard turns off notifications permanently, and that's a much bigger loss than one delayed send.

Treat every Focus-silenced push as information, not failure. It tells you something about when and how that shopper wants to be reached. The stores that win long term aren't the ones sending the most pushes, they're the ones whose pushes still get opened a year later because permission was never abused. Keep testing message timing and content, measure honestly, and let the data guide frequency rather than a fixed calendar.

— Lucas

Try App Clip push built for how iOS actually works

We built StorePush around the reality that App Clip notifications live inside the same Focus and Notification Summary rules as every other app on a shopper's phone, so the platform handles timing, triggers, and attribution with that in mind rather than fighting it.

  • Send lock-screen push through a native App Clip with no email or phone number collected.
  • Connect directly to Shopify, WooCommerce, BigCommerce, or a custom storefront.
  • Track opens, clicks, and attributed revenue through a dashboard built for P90 to P95 attribution windows and click IDs.

The Free plan gets you started with no cost, and the Pro plan runs $50 per month plus a 5% usage commission on attributed recovered revenue once you're ready to scale. Visit Storepush to see how it fits your storefront.

FAQ

Can Focus modes completely block App Clip push notifications?

Focus modes can silence App Clip push notifications the same way they silence any app, queuing them in Notification Center or a later summary instead of showing them on the lock screen. They're rarely blocked forever since a silenced notification is usually still waiting once the shopper checks their phone.

Does Driving Focus affect cart-recovery push notifications?

Yes. Driving Focus is a stricter, system-managed mode that generally prevents app notifications, including marketing pushes, from breaking through while it's active, according to Apple's community discussion on Driving Focus behavior. A cart-recovery push sent during that window typically waits until the mode ends.

Should I mark cart-recovery pushes as Time Sensitive to get through Focus?

No. Time Sensitive is meant for genuinely urgent alerts, and Apple's guidance from its developer session on Time Sensitive notifications treats marketing misuse as a policy risk that can lead to App Review rejection. Stick to standard interruption levels and improve relevance and timing instead.

How does StorePush measure push performance affected by Focus delays?

We use a P90 to P95 attribution window paired with unique click IDs so a sale from a Focus-delayed push still gets credited correctly. Conversion reporting runs separately from delivery timestamp, which keeps revenue attribution accurate even when delivery itself was held up.

Sources

Primary sources for App Clip push and Focus behavior

These are the Apple and StorePush resources behind this guide, useful if you want the underlying technical detail.