Campaign use cases
Planning Traffic Routing for a PWA Funnel
A progressive web app adds caching and install state to the journey, so routing changes must be tested beyond the first page response.
Map the PWA lifecycle
Describe first visit, service-worker registration, install prompt, installed launch, update, and return visit. Mark which requests pass through the public flow and which assets or navigations may be served from a local cache.
Preserve first-touch context
Carry campaign and source identifiers into the application state or tracker according to the site's design. Do not assume a later installed launch will retain a web referrer or repeat the original routed request.
Separate page and application readiness
Validate the White Page as a normal web experience and the Target Page or app funnel through its install states. A successful initial decision does not guarantee that offline assets, updates, or deep links function.
Control stale-cache confusion
Service workers can keep an earlier page or script after the flow configuration changes. Test with fresh profiles and upgraded installations before diagnosing a stale client response as incorrect routing.
Run an install-state matrix
Check new browser, returning browser, installed PWA, cleared storage, and updated service worker on supported devices. Link each observed destination and event to the client state so the result is reproducible.