Customers do not think in platforms. They may discover a service on the web, return through an Android app and complete an important action on iOS. Your measurement should preserve that journey without pretending each interface behaves the same way.
Start with the decision
Before naming events, write down the questions that product, marketing and operations need to answer. An event is useful only when it supports a decision. This keeps the tracking plan compact and prevents teams from collecting data simply because they can.
Share meaning, not implementation details
Use a common business definition for an action such as completing registration, then document how each platform produces it. Screen names, native lifecycle behaviour and browser constraints can differ while the resulting event retains one meaning.
Test complete journeys
Quality assurance should cover sequence, identity and properties across devices. Keep evidence for each test case and assign an owner to investigate drift after releases. A small, trusted event set is more valuable than a large stream nobody can explain.