Paddle Discounts, Custom Checkout Links, and Cleaner Funnel Data
Two things decide whether a web-to-app funnel earns its keep: how easily a ready visitor can pay, and how honestly you can read the results afterward. The September 2026 web-to-app funnel release works on both fronts. Checkout gains automatic Paddle discounts and the option to send buyers to a checkout you already run. Measurement gains a hashed email signal in Google Tag Manager, bot filtering across analytics and ad pixels, and PostHog events covering funnel steps and web purchase redemption. Smaller changes to the Paywall AI Editor, locale matching, and numeric answers round it out.
Checkout: fewer steps, more control
Every additional action between a purchase decision and a completed payment is a place a buyer can stall. The release targets two specific stalls: re-entering a promo code, and being forced onto a checkout the team does not want to operate.
Automatic Paddle discounts. Web-to-app funnels can now read a Paddle discount from URL parameters and apply it without asking the customer to type anything. You pick the discount in the dashboard and attach it to specific Packages, so eligibility is decided by plan rather than by whoever happens to hold a code. A campaign promoting an annual plan can therefore discount annual only, while monthly stays at its normal price. Buyers who choose the eligible Package see the reduced price at checkout; buyers who choose another Package do not.
Custom checkout URLs. Purchase buttons in web-to-app funnels can now point at a checkout URL you supply. Teams that already have a checkout they trust can keep it and use the funnel builder purely for the steps before purchase — the questions, the messaging, the offer presentation — then hand the visitor over when they are ready to pay. This matters most where checkout requirements had previously stopped a funnel from launching at all.
How to choose. If promotions are leaking because codes get lost between the ad and the payment page, start with Package-targeted Paddle discounts. If the blocker is that your business must use a particular checkout, start with the custom URL and leave discount handling where it already lives.
Measurement: matching purchases and removing noise
Deciding where the next acquisition dollar goes depends on connecting a paying customer back to the campaign that produced them — and on not counting visitors who were never going to buy.
Hashed checkout email in Google Tag Manager. Purchase events that Funnels sends into GTM now carry the hashed checkout email as an extra matching signal. The platform loads your configured GTM container on published funnels and pushes events into its data layer; how those events are mapped to analytics and advertising platforms is yours to define. With the appropriate downstream tags in place, the hashed email can strengthen the link between a purchase and the acquisition activity behind it. The GTM setup guide covers the container and data-layer side.
Bot filtering. Crawlers and automated traffic inflate visitor counts, which drags measured conversion rates below what real prospects actually achieve. Funnel analytics and ad pixels now skip bot traffic, and reports affected by earlier bot activity have been cleaned up. The practical benefit is fewer wrong decisions — rewriting a funnel or pausing a campaign because automated hits made the numbers look worse than the human results.
PostHog events. Teams already running PostHog can now see web-to-app funnel behavior next to the rest of the customer journey. The integration receives web funnel events and web purchase redemption events in addition to the purchase and paywall events it already handled, so step-by-step progress and drop-off points sit in the same tool as the rest of your analysis. To enable it, open Project settings → Integrations → PostHog, turn on Send funnel events to PostHog, and set event names to match your reporting conventions. Web purchase redemption has a separate event-name setting.
Funnel building: consistency, language, and input limits
Three smaller changes make the build itself less error-prone.
- Workflow awareness in the Paywall AI Editor. When you edit a single screen, the editor can now see the other screens in the workflow. Its suggestions fit the surrounding experience, which reduces the back-and-forth of keeping tone and design aligned from step to step.
- Language detection across regional locales. Funnels now match supported localizations on the language portion of a visitor's locale even when the region differs. A visitor whose locale carries an unexpected region code still lands on a translation they can read instead of falling through to a default.
- Numeric input validation. Numeric answers — age, height, weight, and similar fields — can be given minimum and maximum values. Invalid entries are caught as the customer types, which keeps the collected data usable for whatever the funnel feeds.
Which update should you configure first?
Match the update to the symptom you are actually seeing:
| Symptom | Start with |
|---|---|
| Visitors reach the offer but do not complete purchase | Package-targeted Paddle discounts; confirm the checkout destination is the one you intend |
| Checkout requirements have blocked a funnel launch | Custom checkout URL on the purchase button |
| Campaign performance is hard to judge | Hashed checkout email in GTM events, plus PostHog funnel and redemption events |
| Conversion rates look implausibly low | Bot filtering, then re-read historical reports that were cleaned up |
| Messaging drifts between funnel screens | Paywall AI Editor workflow awareness |
| Visitors miss an available translation | Regional-locale language matching |
| Numeric answers arrive out of range | Minimum and maximum values on numeric inputs |
A useful distinction: checkout friction and measurement distortion both show up as a weak funnel, but they call for opposite fixes. If real buyers are hesitating at payment, tighten the path to purchase. If the buyers are fine and the numbers are wrong, fix the data before touching the funnel — otherwise you may redesign a page that was working.
Worked example. Suppose a paid campaign promotes an annual subscription at a reduced rate. Attach the Paddle discount to the annual Package only. Visitors arriving through the promotional link get the reduced annual price with no code entry; visitors who prefer monthly see the standard monthly price. Then check the GTM purchase events for the hashed email signal and the PostHog funnel events for the step where non-buyers leave. If the drop-off sits on the offer screen rather than at payment, the discount is not the problem.
Frequently asked questions
Visitors reach the offer but do not buy — where should I start?
Begin with automatic Paddle discounts and your checkout setup. Confirm the discount is attached to the Packages you intend to promote, and confirm the purchase button leads to the checkout you actually want buyers to use.
I need to know which campaigns or funnel steps deserve attention — what helps?
Start with conversion matching, cleaner traffic data, and PostHog events. The hashed checkout email in GTM events improves purchase matching, bot filtering removes automated traffic from funnel analytics and ad pixels, and PostHog events show where visitors leave the funnel.
Do customers have to enter a Paddle discount code at checkout?
No. Funnels applies the Paddle discount from URL parameters, and you target it to specific Packages in the dashboard. Customers who select an eligible Package receive the discount without a code-entry step.
Will a custom checkout URL let me run my own payment page alongside the funnel builder?
Yes. Purchase buttons in web-to-app funnels can be configured with a custom checkout URL, so you can build the journey in the funnel builder and send buyers to your own checkout when they are ready to purchase.
How do I turn on PostHog funnel events?
Go to Project settings → Integrations → PostHog and switch on Send funnel events to PostHog. Name the events however your reporting setup expects. Redemption of a web purchase is named through a separate setting.