Testing the Flow

Testing Deferred Deep Linking

Deferred deep linking can be tested independently of the Flow. There’s no need to complete the entire web funnel or make a purchase to open the link. Instead, follow these steps:

• Open the attribution link directly for testing purposes.
• Regardless of the MMP (Mobile Measurement Partner) being used, the process generally involves the following:

Steps to Test

1. Obtain the configured link as outlined in the Configure Flow Attribution guide.
2. Register the test device in the MMP dashboard.
3. Open the link on the test device.
4. Install and launch the app from your IDE.
5. Check the attribution data payload in the IDE console.

For more information on testing deferred deep linking, refer to these guides:

• AppsFlyer: Testing Deferred Deep Linking on iOS
• AppsFlyer: Testing Deferred Deep Linking on Android
• Branch: Testing Deferred Deep Linking on iOS
• Branch: Testing Deferred Deep Linking on Android

Testing Restoration by Email

Restoration by email requires completing the Flow just once. Subsequent tests do not require repeating the full web funnel.

Steps to Test

1. [One-time Setup] Complete the Flow and make a purchase.
2. Ensure the email address entered on the Flow page is correct.
3. Locate the user in Apphud using the email address. The user should appear.
4. Locate the current app user in Apphud and delete it.
5. (Recommended) Reinstall the app to clear all caches.
6. Relaunch the app, confirming that the Flow user and the current app user are not the same.
7. Call Apphud.attributeFromWeb and pass the email address:
   SwiftKotlin

   Apphud.attributeFromWeb(data: ["email": userEmail]) { success, user in
       if success && Apphud.hasPremiumAccess() {
           print("Premium access successfully activated! Skip paywall here")
       } else {
           print("Not a web subscriber.")
       }
   }
   

   Apphud.attributeFromWeb(data = buildMap { put("email", "[email protected]") }) { result, _ ->
       if (result && Apphud.hasPremiumAccess()) {
           Log.d("ApphudLogsDemo", "Premium access successfully activated! Skip paywall here")
       } else {
           Log.d("ApphudLogsDemo", "Not a web subscriber.")
       }
   }
   

8. Verify the callback:
   • The success value should be true.
   • The user should have premium access.
9. Return to Apphud:
   • The Flow user and app user should merge into one user with the User ID from the Flow.
   • The app user record should no longer exist.

If the test fails, review all steps carefully and debug using the IDE. If issues persist, contact the support team for assistance.

Testing Email Delivery

To test email delivery, make a purchase on the web.

Steps to Test

1. Complete a test purchase via the Flow.
2. Confirm receipt of the email shortly afterward.
3. Verify that the email contains a subscription cancellation link. Click the link to open the customer portal and check the subscription management options.

If emails are not received, check the status of your DNS records. Refer to the Configure Email Domain guide for assistance or contact support.

Troubleshooting

Identify the specific part of the Flow where issues occur:

• For web-related issues, follow the Website Troubleshooting guide.
• For payment-related issues, refer to the Payment Troubleshooting guide.
• For issues with premium status in the app, consult the App Troubleshooting guide.

Website Troubleshooting

📘

Need Expert Assistance?

Our Framer experts are available to help design and implement your Flow. Contact your success manager for support.

Payment Troubleshooting

Common Issues

• No Prices Displayed: Likely due to incorrect paywall or placement setup. Refer to the Configure Web Products guide.
• Payment Form Errors: If the payment form fails to load or the payment doesn't succeed, there may be an issue with the payment provider.

Steps to Troubleshoot

• Inspect the browser console for errors.
• Share the details with the support team for further investigation.

App Troubleshooting

Identifying Issues

When app users are not attributed to web subscriptions:

• Determine whether the issue is with the MMP setup or the Apphud SDK’s attributeFromWeb method.

Debugging Steps

1. Confirm that the attributeFromWeb method is being called.
2. Verify the attribution data payload includes at least one of the following fields:
   • apphud_user_id
   • aph_user_id
   • email
   • apphud_user_email
3. If none of these fields are present, check if the MMP successfully attributed the user.

If the issue persists, escalate to your developer or the support team.