Deep linking allows you to direct your account holders from a Larky push notification to a specific screen or page within your mobile app. This functionality enhances the user experience by reducing friction, helping account holders take action faster.

*Unlike web links, deep links are processed by the mobile banking app. Additional assistance may be needed from your mobile banking provider.

Format for Deep Links

Larky supports two deep link formats depending on your mobile banking platform: relative links and Universal Links. The correct format depends on your mobile banking provider and how your app has been configured.

Relative Links (supported on most platforms)

Relative links are compatible with many mobile banking platforms. Test both with and without a leading backslash, as either may work depending on your provider.

✅ Example 1: /documents/base-paperless-settings
✅ Example 2: documents/base-paperless-settings

Universal Links (Q2 only, if configured)

If your institution uses Q2 as your mobile banking provider and Universal Links have been configured within your environment by Q2, Larky also supports full HTTPS Universal Links. These open directly within your mobile app when tapped on a device.

✅ Example: https://demo.q2.com/salesdemo/uux.aspx#/transfer

For setup details, refer to Q2's documentation: Q2mobility Apps — Universal and App Links

Note: Universal Link configuration is managed by Q2. Please work with your Q2 representative to confirm they are enabled in your environment before using them in a Larky nudge.

Testing Deep Links

Before launching a nudge with a deep link, we recommend testing the deep link with your internal team by creating a test nudge segmented to internal testers.
 

Best Practices

• Use relative links.
• Relative links are case sensitive.
• Targeting the test users multiple times by overriding nudge capping limits.
• Some app features require requesting custom links from your mobile banking provider to support deep linking.

Troubleshooting & Support

If your deep link testing is unsuccessful:

• Double-check that a relative link is being used and casing is correct.
• Test with and without a leading backslash before the relative link.
• Ensure ‘Deep Link’ has been selected in the Larky portal.
• Ensure the tester's app is updated and permissions are enabled.
• Ensure capping limits have been overridden to ensure delivery.

Need Help?

If you have questions, reach out to us at support@larky.com. We’re happy to assist!