Product roadmap
This page summarizes what you can rely on today, how it maps to the documentation, and what we tend to improve over time. Exact features and timing depend on your plan and workspace; your administrator or success contact can confirm what is enabled for you.
How the docs are organized
The guides follow the same sections as the in-app documentation sidebar:
| Section | Topics |
|---|---|
| Getting started | Introduction, Quickstart, Concepts |
| Dashboard | Overview, Funnels, Funnel settings (including Web-to-App Access), Analytics, Audience, Subscribers, Settings |
| Builder | Funnel editor and step type guides from Landing through Success, including Score Result |
| Go live | Publishing & URLs, Funnel analytics (GTM), Stripe and Paddle payments, App integration, Webhook Relay, Webhooks |
Available today
Funnel builder and publishing
- Visual funnel editor - canvas, step connections, branching (for example from quiz answers), save and publish lifecycle
- Step types - landing, quiz, calculating, email capture, score result, paywall (section-based offer page), checkout, success
- Step images - upload or AI-generate visuals on landing, quiz, email capture, score result, and paywall steps
- Per-funnel settings - name and URL slug, branding, navigation, appearance, footer, SEO, built-in or external legal pages, optional GA4 / Meta Pixel IDs
- Publish - each live funnel has a public address: default platform link or your custom domain (several funnels can share one hostname)
- Custom domains - your own hostname for branded links; multiple funnels per domain with path by slug; DNS guidance in Publishing
Payments and subscribers
- Stripe and Paddle - workspace-level keys and webhooks; one active processor at a time for new checkouts
- Checkout - Stripe Express checkout plus card form, or inline Paddle checkout frame; subscriptions and one-time prices you attach in the paywall
- Subscribers - view tied to successful payments and subscription state from processor webhooks
- Audience - leads from email capture; export and filters where the product exposes them
Web-to-app and mobile
- Web-to-App Access - Managed Access (purchase token + short access code; your app talks to documented HTTPS endpoints), Webhook Relay (your backend owns entitlements; signed outbound events), Attribution Only (AppsFlyer links and context without platform-managed app access)
- Success step - open-app flow, optional QR, store fallbacks, access code display, and alignment with OneLink handoff described in Success and App integration
- AppsFlyer - OneLink settings on the funnel; S2S (server-to-server) marketing events from workspace settings when configured
- App integration - purchase claim, access checks, and optional in-app events: full request shapes and security are in App integration
- Universal Links / Android App Links - verification files on your funnel domain when you supply Apple and Android identifiers in funnel settings
Outbound automation
- Funnel webhooks - HTTPS POST with envelope
api_version: "1"(purchase.completed,purchase.claimed,subscription.canceled,refund.created, plus funnel and lead events). See Webhooks - Webhook automation - signed outbound events so your backend or automation tools can grant access, send email, and react to payment lifecycle changes
Analytics and tracking
- In-product funnel analytics - built-in events and dashboard summaries, independent of GA4 / Meta
- Optional GTM / dataLayer - Funnel analytics (GTM) for your own tagging and pixels on the live funnel
Security and data handling
- Encrypted storage for payment and integration secrets (for example processor keys, AppsFlyer dev key, app access key) as described in Settings
Likely next directions
Priorities change, but work often clusters around:
- Editor and content - more layout control, polish, and preview ergonomics
- Analytics - richer reports, more export options, and clearer marketing-tool integrations
- Growth workflows - experiments (A/B or variants), templates, and localization
- Collaboration - team and billing controls in workspace settings
- Dual-brand polish - more web-first templates alongside today's app-store examples
- Web-to-app hardening - clearer lifecycle signals for integrators, richer webhook payloads where useful, rate limits, and operational visibility
- Entitlements - today access is driven largely off purchases and subscriptions the product records for your workspace; a fuller entitlements model may appear if we need multiple overlapping products or seats per workspace
Nothing above is a committed ship date; treat it as orientation.
What we do not aim to be
web2app is focused on web funnels that convert, take payment, and hand off to your app with optional attribution - not a full replacement for:
- Your payment processor's dashboard (disputes, tax configuration, global pricing rules)
- A CRM or CDP (we surface leads and subscribers; deep customer journeys stay in your tools)
- AppsFlyer's full analytics UI (we generate links and send configured S2S events; installs and cohort reporting remain in AppsFlyer)
- App Store / Play Console or StoreKit / Play Billing as the system of record for in-app purchases you do not route through the web funnel
- An email service provider (customer emails, sequences, consent, sender reputation, and deliverability stay in your tools)
Heavy multi-PSP orchestration, subscription migration from legacy stacks, or legal advice on external purchase programs in every region are outside core scope unless explicitly offered on your plan. For regulatory context on web payments and apps, use official Apple and Google documentation linked from App integration.