Customer.io (July 2026): push notifications across multiple mobile apps in one workspace (and why your metrics will jump)

Original release note (source): Customer.io Docs - “Send push notifications to multiple mobile apps in one workspace” (Released July 29, 2026)

• https://docs.customer.io/release-notes/2026-07-29-multiple-mobile-apps/

What changed

Customer.io says it is starting to enable support for multiple mobile apps per platform in a single workspace, so teams do not have to duplicate workspaces (or split audiences) just to send push to different apps.

You can:

• register each app with its own push credentials
• send push through a specific app
• segment profiles by which apps they use

Rollout note: new accounts (and accounts that have never integrated push) get it by default; existing customers may need to request access.

The “growth gotcha”: your push metrics will look different

Once multi-app support is enabled, Customer.io says push metrics reflect one delivery per device, not one delivery per customer profile.

Practical implication:

• if one profile has two devices, one push campaign can now count as 2 Sent (instead of 1)

This is good (it reflects reality), but it can break trendlines if you do not annotate the change.

Why this matters for app teams

If you run a portfolio (consumer app + companion app, markets with different app packages, lite vs full), this is the boring stuff that makes retention programs scalable:

• fewer duplicated journeys and segments
• less accidental cross-workspace drift
• clearer device-level delivery accounting (especially for “send to all devices” policies)

Tiny win

Before you flip the switch, write a one-paragraph note for your stakeholders:

• “push is now counted per device, not per profile”
• the date it changes
• what you will use as your stable benchmark metric going forward (e.g., unique profiles reached vs total deliveries)