Customer.io: multi-app push in one workspace (and the metrics change you must annotate)

Original article (source): Customer.io Release Notes - “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/

The punchline

Customer.io is rolling out support for multiple mobile apps per platform inside a single workspace. That means fewer duplicated audiences and less “split-workspace” overhead when you run more than one app (or multiple bundles) under one lifecycle program.

But the part worth paying attention to is measurement.

The bit that can break your dashboards overnight

When multi-app support is enabled, Customer.io says push metrics change from:

• one delivery per customer profile

to:

• one delivery per device

So if a single profile has two devices, a push can count as two “Sent”, where it previously counted as one.

This is not wrong, it is just different. If you do not annotate the change, you will interpret a reporting jump as “performance changed” when it is really “counting changed”.

What to steal

1) Treat messaging-platform changes as analytics changes

Put a simple rule in your release checklist:

• if push tooling / credential model / workspaces change, you add an analytics annotation and rerun one sanity-check report (Sent, Delivered, CTR, Uninstalls) for the next 72 hours.

2) Confirm how you define reach

If your internal KPI is “users reached”, decide whether you mean:

• unique profiles
• unique devices
• unique people (if you have identity stitching)

Then make sure your dashboards match.

Tiny win

Before enabling a change like this, write down three numbers for a baseline week:

• total pushes sent
• unique profiles messaged
• estimated devices per profile

It makes the post-change deltas explainable in one sentence, instead of a Slack thread.

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