I understand. Deep linking is something specific that would need to be implemented per app, right?
OneSignal has “Additional Data” that can be added when sending a message, I wonder if that can be passed through when the user clicks the notification in some other way, so that the app can receive that little bit of metadata, without having to deal with any URLs or links.
Once the user clicks the notification, they are taken into the app to then see the in-app message, so deep-linking may not be needed as it’s not an external link once the user is within the app, it’s just a button as part of the OneSignal SDK (I think?).
OneSignal has a facility to add a “Custom Action ID” (or URL) for the button of the in-app message.
I was wondering if there’s anything that can be done with this, as this data should already have been pushed into the app from OneSignal, therefore it might be available as a variable?
Well, that is deep linking. @muneer has it right here, @hdawc. We don’t support the feature you are asking about at this time.
That said, we do encourage users to make as robust as possible navigation components or to use the built in navigators. Obviously, this is not the same as deep linking, but for many this has been a suitable solution. Surely, deep linking can help with conversion rates and increase the overall UI. I would suggest that you put this into our github repository as a feature request.
We take our lead of the product from the consumers so… put it there and be heard!