Branch Deep Linking & Attribution

My main use case for Branch is mostly for deferred deep linking and deep linking, and for our referral module, we use Branch to divert the users that we targeted through certain promotion banners so that they land on the module in our app through which we can better monetize our app.

For example, in our app we have a referral program and we ask users to refer certain modules in our app to different users. They share a particular link with other users, and when they click that particular link, basic information about which client, which app, and which user generated that link is captured. When the other user clicks on that link, the journey is not broken and we can move and provide certain monetization or certain referral rewards to our primary users.

I have something else to add about my main use case for Branch: we land that user in that particular module for which it improves the user experience.

The best features Branch offers in my experience are perfect for our use case, and since on iOS we cannot track users after they have installed the app, we can have a seamless experience of the user's first install journey and the tracking data that Branch provides is also very excellent.

The tracking data feature helps my team because with other certain campaigns that we run, we can easily track which particular campaign provides us better return on our investment and from which particular campaign we can convert free users to paid users. This type of tracking data is useful because Branch is able to provide it very efficiently.

Branch is easily supported on various platforms, and it works seamlessly across Android, iOS, and web apps. A single solution for different platforms works together easily, like a Jigsaw puzzle.

The impact of Branch on my organization has vastly improved our rate of return on our investment in the campaign department, so the user acquisition cost has drastically been reduced since we have started using Branch.

Branch can be improved as customer support is not that great, and it takes time to get a response from them. The debugging documentation and the documentation part can be improved.

I would add more about the needed improvements, specifically that the documentation should be enhanced in addition to their customer support.

There are other improvements needed for Branch that come to my mind regarding minor enhancements.

I have been using Branch for two years.

Branch is stable in my experience, and I have not noticed any downtime or issues.

Branch's scalability is quite capable of handling higher traffic loads, and we have not faced any difficulty in that matter.

Customer support for Branch is not that great, as I mentioned earlier, and it takes time to get in connection with their customer support.

I previously used a different solution before Branch. Earlier we tried implementing Firebase, which worked for some time but then user metrics were not great. We switched to AppsFlyer but ultimately settled on Branch.

I have seen a return on investment with Branch. As I mentioned, it has drastically improved our user acquisition cost and money was definitely saved, usually around a ballpark figure of twenty percent of the money saved on user acquisition cost.

My experience with pricing, setup cost, and licensing for Branch was not handled by me as it was done by the product team, but as far as I know, they were quite competitive from the market rates.

Before choosing Branch, I evaluated other options.

My advice to others looking into using Branch is that they can try Branch as it is a great way to handle deep linking and deferred deep linking part of their application and they can definitely improve user experience using the capabilities of Branch.

I have additional thoughts about Branch before we wrap up: it is a great tool to improve user experience and complete the user journey from installation to their first app launch. I would rate Branch an eight out of ten overall.

My main use case for Branch is deep linking and its referral feature.

Deep linking with Branch helps in our app because we have a feature of referral, allowing users to refer other users and earn reward points. For that, I use the referral links and also utilize deep linking.

In my opinion, the best features Branch offers are the deep link and the referral flow.

I find the deep link and referral flow to be the best features because they have the best approach to implementation. When comparing Branch to alternatives like AppsFlyer and Firebase, Branch is more reliable and easy to use.

Branch has positively impacted our organization by bringing huge changes regarding referrals; users come to our apps, and we have increased our user base. While I cannot share exact numbers, we have around a 20% increase in our user base since using Branch.

To improve Branch, there is an area for improvement in debugging and interruptions. When we have any error in deep linking, debugging locally takes time, and if we are not getting a referral or facing issues, that can be a disadvantage.

I have been using Branch for about two years.

In my experience, Branch is stable.

Branch's scalability is good; it can handle growth easily in our organization.

I have not required customer support yet, so I have not interacted with their support team.

Before Branch, I was using Firebase and for some time attempted to implement AppsFlyer, but after a while, someone recommended Branch, and that is why I switched to Branch.

We have not seen a return on investment from using Branch in terms of permissions; the upper management and accounting management hold those permissions.

I evaluated AppsFlyer as an option before choosing Branch.

My advice for others looking into using Branch is that if someone wants to implement referral and deep link capabilities, Branch is a good option based on my understanding and what we have tried. Branch is better than other solutions. For referral and deep linking purposes, Branch is the best option. I would rate this product an 8 out of 10.