Starter
For freelancers and small teams.
$ 24 /mo
Billed monthly · cancel anytime
Platforms3
Accounts10
Used by the world's leading companies
Available metrics
Available dimensions
What our customers say about us.
After three years of use, Catchr has become essential for both our teams and our clients. So far, it has been our best solution for compiling and analyzing data from different advertising platforms. It’s easy to set up, and the customer service is responsive and excellent.
With Catchr’s automated API, we can finally collect and centralize all advertising data, connect it with booking information, and calculate the real ROAS for our restaurant clients. It gives them full visibility, more autonomy, and the ability to optimize campaigns to maximize ROI.
The solution is a real game changer, providing optimal time savings for our data reporting. The major strength of the solution is their highly responsive and professional support.
Create a Branch connection in Catchr using the Branch Key and Branch Secret for the app you want to report on. Select the available app connection, then open the Catchr connector in Looker Studio to create your data source. Start with Date and Install or Open counts for a short period, and compare them with the same app and event definition in Branch.
Catchr exposes counts for installs, reinstalls, opens, clicks, impressions, commerce events, content events, lifecycle events and custom events, among others. Available dimensions include event name, app version, operating system, country and last-attributed-touch information. These are aggregate reporting fields, not a raw user-level event export. Choose the event family that matches your measurement question.
No. The current Catchr connector reads total event counts from Branch analytics. A user can generate several opens or other events, so the total should not be labelled unique users. Compare against the same count type in Branch. If your dashboard requires deduplicated people, use an appropriate unique-user calculation from a source that supplies it rather than renaming an event count.
Yes, where Branch supplies the attribution details. The catalog includes last-attributed-touch campaign, advertising partner, ad set, ad and channel fields. Start with a campaign or partner breakdown and add detail gradually. Some partners do not support every reporting dimension, so a blank field is not automatically evidence that the connector lost the event.
Check the app, dates, time zones, attribution windows and count definitions first. Branch and self-attributing ad networks can credit different interactions, and privacy restrictions can limit the information available for matching. A difference in install counts also affects cost per install. Follow Branch’s discrepancy guidance when comparing reports, rather than assuming every gap is an extraction error.
Commerce Event is an event count in this connector. It can cover different commerce actions, so use Name to isolate the event you intend to measure, such as PURCHASE when that is how your app tracks purchases. The current extraction does not request the Branch revenue aggregation. Do not label the commerce-event count as revenue or use it as the numerator of ROAS.
Yes. Add a source such as Google Ads or Facebook Ads to the same report. Use consistent campaign identifiers, dates and currencies, and aggregate each source to the same level before blending. Keep Branch-attributed events distinct from the ad platform’s own conversions; adding both together can count the same outcome twice.
Our team is always here to answer any questions you may have about our data connector.
