The supplier reports a sent notification; the user says none appeared. They may describe different stages. When purchasing app notifications, define evidence for service acceptance, receipt, display, opening and the subsequent task rather than leaving “sent” unexplained.
Start with a notification's purpose
In a fictional training-booking app, a session changes while a phone is disconnected. The phone returns after the appointment, and the user may open a delayed notification. This is no performed test or customer case. It defines useful lifetime and the destination expected when the booking changes.
Specify event, audience, language, necessary data and the end of usefulness. Ask which devices, operating systems and app versions the proposal includes. Selecting a Push provider does not answer everything: implementation and measurement belong to the purchased scope.
Five stages with separate evidence
Complete this table for the same notification. Not every platform or message type exposes every measure; the supplier should identify unavailable evidence or explain an alternative. The objective is established behavior rather than success marks concealing coverage gaps.
| Stage | Acceptance question | Inference boundary |
|---|---|---|
| Sending accepted | Did the provider accept the request, with what reference? | Does not establish phone receipt |
| Receipt | What evidence exists for this device/platform? | Does not establish user-visible display |
| Display | Was appearance measured, in which app state? | Does not establish reading |
| Opening | Did the user open the notification and correct destination? | Does not establish task completion |
| Task | What business outcome is needed afterward? | Needs its own definition and evidence |
Add time, reference and measurement state to each row. Aggregated data describes a population and may not explain an individual incident. Before comparing percentages from different systems, understand denominator, platform, notification type and collection method.
What does sending-service acceptance say?
FCM explains that a message identifier establishes acceptance for delivery, while delivery can be delayed or the message expire. Its metrics distinguish Sends, Received, Impressions and Opens with platform, message-type and instrumentation limits. These are the documented service's meanings, not universal product terminology.
Ask the supplier to map displayed labels onto the five stages. Statistics may lag or lack coverage, so an absent metric alone does not establish failed sending. An opening event also does not promise that someone read details or agreed to them.
Permission and lifetime belong in the scenario
Android documents how notification behavior depends on permission choices, exceptions and version-specific conditions. Include denied permission in suitable test scope and specify any required in-app experience. Android behavior should not be assumed for every device or operating system.
Agree message lifetime when usefulness ends. In the training example, opening should lead to the current booking state with understandable handling of an expired or cancelled session. A specialist must explain provider and app capabilities without promising withdrawal of every previously displayed message.
Request an acceptance sample covering waiting
The proposed plan includes granted and denied permission, delayed connectivity, expired usefulness and a destination whose record state changed. An authorized team prepares synthetic data and records measurable and unknown behavior. No notification is sent or device permission changed here.
Identify who investigates differences between reported metrics and user experience and what information is necessary without excess collection. Do not enable analytics or data sharing merely to populate a commercial worksheet; appropriate measurement requirements and limits need authorized specialist review.
For a person with two phones, specify whether the target count means devices or people. Delivery to one phone answers a different question from delivery to both; preserve that distinction in the outcome definition.
Mobile proposal components place this function within the wider project. Bring evidence stages and waiting scenarios when discussing app development with Nextwave to define what “notifications work” means before handover.
Definition references
Relevant FCM message lifespan, delivery metrics and Android permission sections were read on 4 November 2026. Prepared with AI assistance and information and translation review, without actual sending or device tests.