fallback link, can I know where the user is coming from ?

Asked on October 20, 2016 in Technical.

I’ve set up branch to work with only one link, and it works perfectly in safari.

In Chrome I have to resend the user to the app using branch’s deepview javascript code. which works. but doesn’t know anything about where the user is coming from.

is there any way to get this information in branch in the web ?

 

GETAWAY — Developer
3 Answer(s)
Answered on October 20, 2016.

Hi! I’m not certain I understand the specific problem you’re describing, because I am not aware of a situation in which you would need to ‘resend the user to the app’ from Chrome. It may be more helpful if you can provide more detail and examples.

That said, you could check out the Branch web SDK. This will let you get the link information back on the web to use for whatever it is you’re trying to do.

Branch — Developer
Answered on October 20, 2016.

Hi Abauer,

Thanks for the fast response, to describe the problem . I implemented branch links in our app by following the example for the iOS SDK.
The implementation is as the following:
1- open app using universal link.

2- fall back to our web page if couldn’t”t open the app.

This lead to having the links working in safari on iOS.
But in chrome/gmail the universal link is never called because according to this post: http://disq.us/p/19z7vc9 the webview needs to be initialized first before calling another universal link.

Now I did that too, in our fallback page, I added the javascipt example code to open a branch link and it works perfectly. the app always opens after going to the fallback page if the app is installed.

Now the problem is, this fallback page doesn’t seem to know anything about the sender (no extra headers or any info) to know what was the source of the URL ie where is the user coming from.

So is there anyway for this page to know this info ? or should I just create one fall back page per url and create multiple urls ?

GETAWAY — Developer
Answered on October 20, 2016.

Ahh, makes sense now.

Are you using the deepview() and deepviewCta() calls on your fallback page? If so, you could create one fall back page per URL as you mentioned. The other approach is to set the make_new_link option to false when configuring your deepview call. This should make the page re-use the link data from whatever link drove the user to your fallback page in the first place. You can see an example of this here.

Branch — Developer