Overview

To connect an existing funnel, you'll need to integrate the Apphud Web Library and call specific methods to initialize the SDK, collect attribution data, track events, and more.

Initializing the SDK

To start using the Apphud SDK, include the SDK JavaScript file in your project. You can either download the SDK or include it via a <script> tag. Find the latest SDK version in our Github releases page.

<script src="https://js.apphud.com/web/v2/apphud.js"></script>

Collecting Attribution Data

If you're running advertising campaigns, collecting attribution data is essential (e.g., fetching Click IDs, which vary across different platforms). Apphud will use these Click IDs to post back subscription events to the relevant advertising network, ensuring accurate attribution and reporting. Follow our Configure Flow Attribution guide for details.

SDK Reference

Refer to our SDK documentation for detailed instructions. Common use cases include:

Tracking Events
Loading Placements
Fetching Product Information
Displaying a Payment Form
Listening for Payment Callbacks
Redirecting to a Success URL

For a comprehensive guide to SDK usage, visit our GitHub documentation.

FAQ

❓Can I use Apphud with a fully custom web funnel, not built with Framer?

Yes. Connect the Apphud Web SDK (apphud.js) directly to your own custom funnel — you get the same analytics as a Framer-based Flow. See Initializing the SDK above and the apphud.js GitHub repo.

❓Will post-purchase emails and access restoration still work on a custom funnel?

Yes, under two conditions on your side:

Email delivery — Apphud's server sends the post-purchase email (with the install/restore link); the funnel itself doesn't send it. The only requirement is that the user's email reaches Apphud: collect it with your own form (e.g. on a quiz step) and pass it via apphud.setEmail(email). You also need to configure your sending domain's SPF/DKIM records — see Domain Configuration.
Access restoration — the primary path is a deep link: apphud.getDeepLink() → OneLink → attributeFromWeb in the app merges the mobile user into the web user. The fallback is restoring by email (same attributeFromWeb call, with the email instead).