Manage Devices in Customer.io

Overview

Managing devices in Customer.io is how you keep mobile push audiences clean and actionable, so cart recovery, back-in-stock, and post-purchase flows reach the right phone at the right time. For D2C brands, device hygiene is the difference between “push works” and “push is noisy,” especially when shoppers reinstall your app, switch phones, or toggle permissions.

If you want this wired into a revenue-ready orchestration layer (events, segments, frequency rules, and creative) Propel can help you pressure test the setup and turn it into repeatable programs, book a strategy call.

How It Works

Manage devices in Customer.io connects a person profile to one or more device records, which are then used to deliver push notifications and to segment audiences by device attributes and push eligibility. In practice, every time your app SDK registers a device token, Customer.io stores it under the correct person, tracks platform details (like iOS vs Android), and uses the latest valid token to send push.

From an execution standpoint, you want three things to be true: the device is associated with the right customer, the token is current (old tokens get replaced or invalidated), and your segments exclude people who cannot receive push. Your mobile SDK implementation and identity strategy drive most of this, then campaigns and segments do the targeting work inside Customer.io.

Step-by-Step Setup

Managing devices in Customer.io starts with getting reliable device registration and identity mapping, then operationalizing it in segments and campaigns.

1. Confirm your identity strategy: decide when an app user becomes “identified” (login, checkout, email capture) and ensure you consistently identify the person before or immediately after device registration.
2. Implement the mobile SDK properly: enable push in your iOS and Android apps, then verify the SDK is registering device tokens and updating them when they change.
3. Verify device records on real profiles: open a few known customer profiles and confirm you can see associated devices (platform, last updated activity, and that the customer is push addressable).
4. Handle reinstall and token refresh: confirm your app re-registers tokens on app open and after OS updates, and that old tokens are not being treated as active.
5. Create push eligibility segments: build segments like “Has a valid device token” and “Push enabled” so campaigns do not waste sends on unreachable devices.
6. Layer in commerce context: add segments that combine device eligibility with intent, like “Viewed product in last 24 hours” or “Started checkout but no purchase.”
7. QA deliverability and routing: run internal tests across iOS and Android, confirm deep links work, and ensure messages land on the most recent device.
8. Set frequency rules: cap push sends per day per person to protect conversion and reduce opt-outs.

When Should You Use This Feature

Managing devices in Customer.io matters most when push is a meaningful revenue lever and you need accurate targeting across iOS and Android devices.

• Abandoned cart recovery on mobile: if a shopper adds to cart in-app and bounces, push can outperform email on speed, but only if the device token is current and tied to the right person.
• Back-in-stock and price drop alerts: these are time-sensitive, so device accuracy directly impacts conversion rate.
• Post-purchase replenishment and cross-sell: device-based targeting helps you hit the window when the customer is most likely to reorder (for example, 21 days after purchase for supplements).
• Reactivation for lapsed app customers: you can prioritize customers who still have a reachable device and suppress those who have uninstalled or disabled push.

Realistic scenario: A skincare brand sees high app browse rates but low email clickthrough. They build a “Viewed product twice in 48 hours, no purchase” push journey. Once device management is cleaned up, pushes stop going to stale tokens, opt-outs drop, and the journey becomes a consistent first purchase driver instead of a noisy channel.

Operational Considerations

Managing devices in Customer.io is operationally sensitive because it sits at the intersection of identity, permissions, and message orchestration.

• Identity merges: if a shopper browses anonymously then later logs in, you need a plan to merge that activity and ensure the device attaches to the identified profile. Otherwise, you will under-message high-intent shoppers or double-message across profiles.
• Multi-device customers: some customers have both a phone and tablet. Decide whether you want to message all devices or prioritize the most recently active device (most D2C brands prioritize recency to reduce duplicate sends).
• Permission states: treat “has device” and “can receive push” as separate concepts. A device record might exist even if push permissions are off.
• Channel coordination: push should not compete with SMS and email. Use holdouts, time windows, and suppression rules so cart recovery does not become three messages in 10 minutes.
• Deep links and landing pages: push is only as good as the click destination. Ensure deep links route to the exact PDP, cart, or checkout state, not a generic home screen.

Implementation Checklist

Managing devices in Customer.io is easiest to maintain when you treat it like a system, not a one-time SDK task.

• Mobile SDK installed and registering device tokens for iOS and Android
• Clear identify call timing (email capture, login, or checkout) to associate devices with the correct person
• Token refresh behavior verified (reinstall, OS updates, app open)
• Segments for “push reachable” built and used as campaign entry filters
• Frequency caps and quiet hours configured for push
• Deep links tested for PDP, cart, checkout, and order status pages
• Suppression rules to prevent push colliding with SMS and email
• Reporting view: push sends, delivered, opens, conversions, and opt-outs tracked by journey

Expert Implementation Tips

Managing devices in Customer.io becomes a revenue multiplier when you build around intent and recency, not just “everyone with the app.”

• In retention programs we’ve implemented for D2C brands, the best-performing push audiences are usually “recent high intent” (checkout started, multiple PDP views, back-in-stock request), then filtered to only reachable devices.
• Use a “most recent app activity” filter to avoid sending cart pushes to a customer’s old phone. It reduces duplicate notifications and keeps opt-out rates down.
• Build a push fallback path. If the customer is not push reachable, route them to email or SMS instead of dropping them from the journey.
• Keep push copy tighter than email. Lead with the product and the reason to act now (low stock, cart saved, limited-time offer), then deep link directly to the next step.

Common Mistakes to Avoid

Managing devices in Customer.io can quietly break performance when teams assume device data “just works” after the SDK is installed.

• Not segmenting by push reachability: sending to everyone with an app profile inflates send volume and hides real performance issues.
• Ignoring identity edge cases: anonymous browsing, guest checkout, and multiple emails can create duplicate profiles and split device associations.
• Over-messaging multi-device customers: two devices receiving the same cart push feels spammy and increases opt-outs.
• Broken deep links: pushes that open the app but do not land on the intended PDP or cart step waste the click and kill conversion.
• No channel rules: push, SMS, and email all firing on the same abandonment event leads to short-term lift and long-term list decay.

Summary

Use device management when push is part of your revenue mix and you need accurate targeting across real shoppers and real phones. Clean device data improves cart recovery speed, reduces opt-outs, and makes cross-channel orchestration in Customer.io more predictable.

Implement with Propel

Propel helps brands operationalize Customer.io device data into segments and journeys that drive first and repeat purchases. If you want a clean push foundation tied to cart recovery and post-purchase flows, book a strategy call.