Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How does branch.io handle situations where multiple devices may have the same fingerprint?

Tags:

ios

branch.io

I am looking at using branch.io to support a flow in my app whereby an existing user can invite a friend to use the app by sending them their personalized invitation link. The person clicking the link would be sent to the App Store to download the app, and upon doing so and then opening it, they would be prompted to add the link owner as a friend. I'm curious how this would work in situations where many people in the same GPS location are inviting each other to the app. Does anyone have experience with this or know how branch handles this scenario?

like image 841
eric Avatar asked Feb 24 '15 00:02

eric


People also ask

How does Branch io works?

When users click a Branch link, they open that webpage, and we get pinged. We use matching to detect your users' device, operating system, and browser, and combine that with cookies to either remember or check whether they have the app installed. Then we can redirect them for an optimal experience.

How does branch IO deep linking work?

Branch's deep links store contextual information about where a user wants to go, where the link was clicked, who originally shared the link, and an almost unlimited amount of custom data. This empowers you to build powerful personalization features to provide users better experiences and happier, stickier users.

How does Branch SDK work?

How does it work? When a user lands on a page with the Branch Web SDK initialized, the SDK makes a request to specific Branch endpoints ( v1/open and v1/pageview ). A cookie is stored in local storage with data that will be used to initialize a Journeys banner (if applicable).


1 Answers

I'm a developer at Branch. Good question, and one we've been asked a number of times now. In general, out in the real world, mismatches are very, very rare as people aren't typically on the same wifi with the exact same phone and OS version, so most people aren't concerned. Additionally as people click links across our network, we remember that user using a cookie. Then, if someone clicks the link again for your app, we don't guess anymore and can deep link with 100% accuracy from prior history. So, as people use the service, the linking gets even closer to 100% in aggregate.

Your concern centers around the potential for mismatching. If the clicking user gets taken the app store (since they don't have the app installed), there is a slight chance of a mismatch when the data gets passed through because we match the browser fingerprint to the device fingerprint by comparing IP, OS, OS version, phone model and time. If two phones match in all those parameters and click the link at the same time and then immediately begin app sessions after installing, there is a risk of mismatch.

We have an option that will not match an app session and pass parameters if there are two or more, matching, outstanding fingerprints. This will basically protect against the case of a potential mismatch of multiple clicks. You can enable it by setting Link Type to Unique on the Dashboard's Link Settings screen, at the bottom under "Advanced Settings."

like image 84
st.derrick Avatar answered Oct 23 '22 20:10

st.derrick