Branch

Name: Branch
Brand: Branch

Branch is a mobile measurement and deep-linking platform that creates and manages deep links, attributes cross-platform marketing performance across paid/owned/organic channels, and provides dashboards and APIs for campaign and conversion reporting.

Est 2013|Valuation $4B|Raised $667.3M|82 Ref Customers

LinkedIn 78K|Web traffic 192K|FTEs 512|HQ Mountain View, California, US

MarketsMarketing Automation Platforms Marketing Attribution Mobile Attribution (MMP)

Published Oct 14, 2026

01Common complaints

Consider alternative vendors when: - Automated identity provisioning via SCIM/JIT is a firm requirement for identity lifecycle management. - Fully transparent, self-serve pricing and frictionless onboarding are primary procurement constraints; other vendors publish clearer starting points. - The technical stack relies heavily on Expo/FlutterFlow and the organization cannot tolerate potential integration instability; require a proof-of-concept before committing. - Independently validated attribution accuracy benchmarks are required for regulated or financial decisioning; vendor-published ROI metrics and claims lack disclosed methodologies in the reviewed materials.

Deal disqualifiers (poor fit)

Organizations that require SCIM/JIT provisioning as a mandatory feature (documented as not supported in vendor SSO docs).
Buyers needing fully transparent, self-serve pricing with minimal sales involvement.
Teams with limited engineering bandwidth or those relying on third-party wrappers with known community-reported integration issues; such teams should validate compatibility before committing.

Documented limitations

SCIM/JIT provisioning: Not supported per vendor SSO documentation.
SSO migration: Vendor documentation notes a migration to Auth0-backed SSO and deprecation timelines for previous methods; organizations should assess operational impacts and migration requirements.

Commonly reported issues (unofficial)

Framework-specific integration issues reported in community threads (e.g., FlutterFlow, React Native Expo) related to initialization, link routing, and attribution.
Variability in customer support experience, ranging from limited responsiveness to satisfactory outcomes according to public reviews.

Why some customers leave / churn reasons (from reviews)

Recurring reasons appearing in reviews and community posts include:

Concerns about measurement accuracy.
Variability in customer support responsiveness, particularly for onboarding.
Implementation friction in specific frameworks (Expo / FlutterFlow reports of unreliable behavior).
Limitations in link governance and link-level reporting.

02Why they buy

Differentiating capabilities (validated or partially validated)

- Deep linking as a core capability: multiple reviews and product descriptions confirm deep linking is a primary use case and value. - Combined cross-platform attribution: vendor messaging emphasizes reporting across paid, owned, and organic channels in a single view. - Substantial presence on review platforms: a large number of reviews and a high average rating on G2 indicate broad public usage, though this should be interpreted alongside negative reviews and context.

Areas where competitors may be stronger

Public security and compliance disclosures: some competitors publish more explicit references to certifications and compliance documentation.
Public entry-level pricing clarity: competitors provide clearer pricing entry points for self-serve buyers.
Data residency and hosting transparency: some competitors document data center locations and residency options.

03Field reports

Review platform signals (ratings, volume)

G2: well rated on G2 with a notable number of reviews on the platform at the time of review.
Capterra: Listing and mixed review excerpts were present; summary indicators on listing pages should be interpreted cautiously.
Trustpilot: Very small sample on Trustpilot at the time of review.

Direct quotes (positive and negative)

From public review platforms (quotes preserved as provided by reviewers): G2 – positive example: - “Branch is a very good option for generating deep links on the go, supports custom urls too.” - Likes: “SDK is easy to integrate… Configuration is simple.” - Dislikes: “Customer Support doesn't help much… There is no way to check report by particular link.” G2 – very negative example: - Title: “Decent product, terrible customer service.” - Like: “strong pricing model… large feature suite.” - Dislike: “The customer service was easily the worst we have experienced… struggled to get them on a call… onboarding support was not available… support agents were quite dismissive.” Capterra – mixed examples: - “Worked most well, but numbers never seemed right” - Pros: “reporting of link clicks… organizes them.” - Cons: “hundreds of links got really confusing… the number clicks never seems correct… switched to another service… click totals seemed… more reasonable.” - “Branch Review” - Pros: “The ability to direct different device users to appropriate landing pages is awesome.” - Cons: “not very intuitive & is iron-fisted.” Reddit – community complaints (integration/reliability): - FlutterFlow subreddit thread: “it’s never worked… screen gets stuck… Create share links does nothing… there’s definitely something wrong with it.” - React Native subreddit thread: “many… not attributed correctly, especially… Google Ads… not being tracked reliably… Branch SDK with RN expo… too much pain.” Trustpilot – pricing/billing complaint (single-review sample): - “Scammy and Abusive… implies there is a self service tier… only choose from paid plans… immediately want your card details… ignored and finally gaslighted.”

Why customers choose Branch (patterns)

Across vendor messaging and public reviews, commonly cited reasons for selecting Branch include:

Deep linking capability (routing users into the correct in-app context).
Cross-platform attribution for web-to-app and omni-channel journeys.
Consolidated dashboards for measuring paid and organic channel performance.

Vendor-published outcome metrics (treat cautiously)

Branch's marketing materials present outcome metrics such as reductions in fraudulent installs, significant revenue growth, and improvements in retention.

Critical evaluation: These figures are vendor-published and are presented without methodology, baseline definitions, or representative sample details in the materials reviewed. Treat such metrics as illustrative rather than predictive for an individual buyer's ROI.

Named testimonials (vendor site)

Vendor-published testimonials include quotes from executives at several customers referencing improved connectivity and integration across experiences.

Critical evaluation: These testimonials are vendor-provided and typically highlight positive outcomes without detailed context on implementation effort, cost, or counterfactual comparisons. Procurement teams should request case study details, underlying data, and implementation notes when using these materials to inform decisions.

04Best fit

Company size

Common fit: mid-market to enterprise mobile apps where mobile revenue or user engagement justifies an MMP and investment in instrumentation.
Small apps may use Branch, but TCO and integration overhead should be evaluated relative to simpler deep-linking options or combined solutions with lower operational overhead.

Industries / verticals

Media & entertainment, commerce/retail, subscription apps, marketplaces, and fintech are common verticals seen in vendor examples and MMP usage patterns.

Roles and personas

Decision makers: Head of Growth, Performance Marketing lead, Mobile Product leader, Marketing Ops, Data/Analytics leader.
End users: UA managers, lifecycle/email marketers, product analysts, and engineers responsible for SDK integration and link routing.

Qualification criteria (good fit)

Requirements include web-to-app and omni-channel measurement (beyond paid install attribution).
High volume of campaigns requiring deep-link routing across email/SMS/QR/social.
Capacity to invest in implementation and QA across devices and browser contexts.

05The pitch

What the product does (objective value proposition)

Branch is a B2B mobile measurement and linking platform typically used by mobile growth, product, and marketing teams to: - Create and manage deep links / “universal” links that route users to the appropriate in-app screen (or fallback web/app store destinations). - Attribute and measure marketing performance across paid, owned, and organic channels (with emphasis on cross-platform journeys: web → app, email → app, QR → app, etc.). - Provide dashboards and exports/APIs for campaign performance and user conversion funnels. In practice, Branch is commonly evaluated as a mobile measurement partner (MMP) combined with deep linking infrastructure.

Target market and positioning

Branch targets mobile-first and omni-channel brands running campaigns across ads, email, web, social, SEO, affiliates, and QR codes. The vendor markets a combined deep linking and attribution solution and highlights the ability to provide a centralized reporting view across channels.

Get a comprehensive analysis of Branch including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 14, 2026

01Common complaints

Consider alternative vendors when:

Automated identity provisioning via SCIM/JIT is a firm requirement for identity lifecycle management.
Fully transparent, self-serve pricing and frictionless onboarding are primary procurement constraints; other vendors publish clearer starting points.
The technical stack relies heavily on Expo/FlutterFlow and the organization cannot tolerate potential integration instability; require a proof-of-concept before committing.
Independently validated attribution accuracy benchmarks are required for regulated or financial decisioning; vendor-published ROI metrics and claims lack disclosed methodologies in the reviewed materials.

Deal disqualifiers (poor fit)

Organizations that require SCIM/JIT provisioning as a mandatory feature (documented as not supported in vendor SSO docs).
Buyers needing fully transparent, self-serve pricing with minimal sales involvement.
Teams with limited engineering bandwidth or those relying on third-party wrappers with known community-reported integration issues; such teams should validate compatibility before committing.

Documented limitations

SCIM/JIT provisioning: Not supported per vendor SSO documentation.
SSO migration: Vendor documentation notes a migration to Auth0-backed SSO and deprecation timelines for previous methods; organizations should assess operational impacts and migration requirements.

Commonly reported issues (unofficial)

Framework-specific integration issues reported in community threads (e.g., FlutterFlow, React Native Expo) related to initialization, link routing, and attribution.
Variability in customer support experience, ranging from limited responsiveness to satisfactory outcomes according to public reviews.

Why some customers leave / churn reasons (from reviews)

Recurring reasons appearing in reviews and community posts include:

Concerns about measurement accuracy.
Variability in customer support responsiveness, particularly for onboarding.
Implementation friction in specific frameworks (Expo / FlutterFlow reports of unreliable behavior).
Limitations in link governance and link-level reporting.

02Why they buy

Differentiating capabilities (validated or partially validated)

Deep linking as a core capability: multiple reviews and product descriptions confirm deep linking is a primary use case and value.
Combined cross-platform attribution: vendor messaging emphasizes reporting across paid, owned, and organic channels in a single view.
Substantial presence on review platforms: a large number of reviews and a high average rating on G2 indicate broad public usage, though this should be interpreted alongside negative reviews and context.

Areas where competitors may be stronger

Public security and compliance disclosures: some competitors publish more explicit references to certifications and compliance documentation.
Public entry-level pricing clarity: competitors provide clearer pricing entry points for self-serve buyers.
Data residency and hosting transparency: some competitors document data center locations and residency options.

03Field reports

Review platform signals (ratings, volume)

G2: well rated on G2 with a notable number of reviews on the platform at the time of review.
Capterra: Listing and mixed review excerpts were present; summary indicators on listing pages should be interpreted cautiously.
Trustpilot: Very small sample on Trustpilot at the time of review.

Direct quotes (positive and negative)

From public review platforms (quotes preserved as provided by reviewers):

G2 – positive example:

“Branch is a very good option for generating deep links on the go, supports custom urls too.”
- Likes: “SDK is easy to integrate… Configuration is simple.”
- Dislikes: “Customer Support doesn't help much… There is no way to check report by particular link.”

G2 – very negative example:

Title: “Decent product, terrible customer service.”
- Like: “strong pricing model… large feature suite.”
- Dislike: “The customer service was easily the worst we have experienced… struggled to get them on a call… onboarding support was not available… support agents were quite dismissive.”

Capterra – mixed examples:

“Worked most well, but numbers never seemed right”
- Pros: “reporting of link clicks… organizes them.”
- Cons: “hundreds of links got really confusing… the number clicks never seems correct… switched to another service… click totals seemed… more reasonable.”
“Branch Review”
- Pros: “The ability to direct different device users to appropriate landing pages is awesome.”
- Cons: “not very intuitive & is iron-fisted.”

Reddit – community complaints (integration/reliability):

FlutterFlow subreddit thread: “it’s never worked… screen gets stuck… Create share links does nothing… there’s definitely something wrong with it.”
React Native subreddit thread: “many… not attributed correctly, especially… Google Ads… not being tracked reliably… Branch SDK with RN expo… too much pain.”

Trustpilot – pricing/billing complaint (single-review sample):

“Scammy and Abusive… implies there is a self service tier… only choose from paid plans… immediately want your card details… ignored and finally gaslighted.”

Why customers choose Branch (patterns)

Across vendor messaging and public reviews, commonly cited reasons for selecting Branch include:

Deep linking capability (routing users into the correct in-app context).
Cross-platform attribution for web-to-app and omni-channel journeys.
Consolidated dashboards for measuring paid and organic channel performance.

Vendor-published outcome metrics (treat cautiously)

Branch's marketing materials present outcome metrics such as reductions in fraudulent installs, significant revenue growth, and improvements in retention.

Named testimonials (vendor site)

Vendor-published testimonials include quotes from executives at several customers referencing improved connectivity and integration across experiences.

04Best fit

Company size

Common fit: mid-market to enterprise mobile apps where mobile revenue or user engagement justifies an MMP and investment in instrumentation.
Small apps may use Branch, but TCO and integration overhead should be evaluated relative to simpler deep-linking options or combined solutions with lower operational overhead.

Industries / verticals

Media & entertainment, commerce/retail, subscription apps, marketplaces, and fintech are common verticals seen in vendor examples and MMP usage patterns.

Roles and personas

Decision makers: Head of Growth, Performance Marketing lead, Mobile Product leader, Marketing Ops, Data/Analytics leader.
End users: UA managers, lifecycle/email marketers, product analysts, and engineers responsible for SDK integration and link routing.

Qualification criteria (good fit)

Requirements include web-to-app and omni-channel measurement (beyond paid install attribution).
High volume of campaigns requiring deep-link routing across email/SMS/QR/social.
Capacity to invest in implementation and QA across devices and browser contexts.

05The pitch

What the product does (objective value proposition)

Branch is a B2B mobile measurement and linking platform typically used by mobile growth, product, and marketing teams to:

Create and manage deep links / “universal” links that route users to the appropriate in-app screen (or fallback web/app store destinations).
Attribute and measure marketing performance across paid, owned, and organic channels (with emphasis on cross-platform journeys: web → app, email → app, QR → app, etc.).
Provide dashboards and exports/APIs for campaign performance and user conversion funnels.

In practice, Branch is commonly evaluated as a mobile measurement partner (MMP) combined with deep linking infrastructure.

Target market and positioning

Get a comprehensive analysis of Branch including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →