AdRoll provides a platform, performance, and services to meet companys' marketing goals while streamlining marketing operation. Solutions technologies for brand awareness, retargeting, and abandoned cart recovery. And the AdRoll Cross-Channel Performance Dashboard displays campaigns holistically so users can analyze performance, run reports, gather insights.
$40
per month
Firebase
Score 8.2 out of 10
N/A
Google offers the Firebase suite of application development tools, available free or at cost for higher degree of usages, priced flexibly accorded to features needed. The suite includes A/B testing and Crashlytics, Cloud Messaging (FCM) and in-app messaging, cloud storage and NoSQL storage (Cloud Firestore and Firestore Realtime Database), and other features supporting developers with flexible mobile application development.
$0.01
Per Verification
Pricing
AdRoll
Firebase
Editions & Modules
Essentials
$12
per month
Growth
$25
per month
Starter
Free
Phone Authentication
$0.01
Per Verification
Stored Data
$0.18
Per GiB
Offerings
Pricing Offerings
AdRoll
Firebase
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
AdRoll
Firebase
Features
AdRoll
Firebase
Ad Network Integration
Comparison of Ad Network Integration features of Product A and Product B
AdRoll
6.8
21 Ratings
8% below category average
Firebase
-
Ratings
Data Transfer
6.721 Ratings
00 Ratings
DSP integration
6.815 Ratings
00 Ratings
Ad Campaigns
Comparison of Ad Campaigns features of Product A and Product B
AdRoll
4.2
44 Ratings
61% below category average
Firebase
-
Ratings
Ad campaign creation
1.143 Ratings
00 Ratings
Ad deployment
8.044 Ratings
00 Ratings
Display advertising
4.041 Ratings
00 Ratings
Ad display and retargeting segmentation
4.044 Ratings
00 Ratings
Sequence targeting
4.026 Ratings
00 Ratings
Ad Reporting & Analytics
Comparison of Ad Reporting & Analytics features of Product A and Product B
Adroll is perfect for companies and situations in which you are trying to retarget customers with specific products. Their platform is perfect for dynamic content on their web and social ads. Also, if you are running multiple campaigns at once then the Adroll platform is perfect when organizing many different campaigns at once. If you are just running one or two social campaigns I feel it is easier to go directly to the source and you can probably leave Adroll out of the mix
Firebase should be your first choice if your platform is mobile first. Firebase's mobile platform support for client-side applications is second to none, and I cannot think of a comparable cross-platform toolkit. Firebase also integrates well with your server-side solution, meaning that you can plug Firebase into your existing app architecture with minimal effort.
Firebase lags behind on the desktop, however. Although macOS support is rapidly catching up, full Windows support is a glaring omission for most Firebase features. This means that if your platform targets Windows, you will need to implement the client functionality manually using Firebase's web APIs and wrappers, or look for another solution.
Analytics wise, retention is extremely important to our app, therefore we take advantage of the cohort analysis to see the impact of our middle funnel (retargeting, push, email) efforts affect the percent of users that come back into the app. Firebase allows us to easily segment these this data and look at a running average based on certain dates.
When it comes to any mobile app, a deep linking strategy is essential to any apps success. With Firebase's Dynamic Links, we are able to share dynamic links (recognize user device) that are able to redirect to in-app content. These deep links allow users to share other deep-linked content with friends, that also have link preview assets.
Firebase allows users to effectively track events, funnels, and MAUs. With this simple event tracking feature, users can put organize these events into funnels of their main user flows (e.g., checkout flows, onboarding flows, etc.), and subsequently be able to understand where the drop-off is in the funnel and then prioritize areas of the funnel to fix. Also, MAU is important to be able to tell if you are bringing in new users and what's the active volume for each platform (Android, iOS).
Attribution and specifically multi-touch attribution could be more robust such as Branch or Appsflyer but understand this isn't Firebases bread and butter.
More parameters. Firebase allows you to track tons of events (believe it's up to 50 or so) but the parameters of the events it only allows you to track 5 which is so messily and unbelievable. So you're able to get good high-level data but if you want to get granular with the events and actions are taken on your app to get real data insight you either have to go with a paid data analytics platform or bring on someone that's an expert in SQL to go through Big Query.
City-specific data instead of just country-specific data would have been a huge plus as well.
We like AdRoll as it's filling a hole in our advertising right now, but it's not our favorite platform for running our online ads. Google and Facebook especially are our favorites, as we can do much more with them than we can with AdRoll, hence the 7 out of 10 rating.
Once tags are given and things are set up, it is fairly easy to utilize the reporting dashboard and check in on your ongoing campaigns. Metrics are simple to follow and can be toggled for specific dates or other qualifiers
I don't use the Firebase UI much, but rather connect it to GA4. GA4 has a great event model but the GA4 UI and analysis capabilities are limited. It's harder to measure product usage type of engagement but if you have the time and resources to leverage the GA4 to BiqQuery export you'll have all the raw event data you'll need for deep analysis, segmentation, and audience activation.
We don't use AdRoll support much, but when we have it's been fine, in line with other advertising platforms where it takes a few days maximum to resolve an issue that you have with them. In general though, the platform is very self sufficient and we do not have to use their support much, which is a good thing.
Our analytics folks handled the majority of the communication when it came to customer service, but as far as I was aware, the support we got was pretty good. When we had an issue, we were able to reach out and get support in a timely fashion. Firebase was easy to reach and reasonably available to assist when needed.
Implementation was easy, as all we needed to do was use Google Tag Manager's built in AdRoll tag type and input our client ID and we were up and running. If you're not using Google Tag Manager, I imagine the implementation would be relatively easy as well, as all that's needed is a basic pixel.
AdRoll is better than Taboola in that the ad creation process. I like how the ads have better retargeting than Taboola. Also, I can make the ads look more elegant and fit our brand more than Taboola. Adroll's analytics are also better than Taboola in my experience. Lastly, Tabool is relatively the same price as Taboola.
Before using Firebase, we exclusively used self hosted database services. Using Firebase has allowed us to reduce reliance on single points of failure and systems that are difficult to scale. Additionally, Firebase is much easier to set up and use than any sort of self hosted database. This simplicity has allowed us to try features that we might not have based on the amount of work they required in the past.
Mixed - while the tool provides an invaluable productivity gain the actual ROI it provides is less certain. We found if used in combination with other revenue analytics it was useful to determine the impact it had on revenue from returning visitors. If data is used on its own the impact on revenue is less quantifiable.
Makes building real-time interfaces easy to do at scale with no backend involvement.
Very low pricing for small companies and green-fields projects.
Lack of support for more complicated queries needs to be managed by users and often forces strange architecture choices for data to enable it to be easily accessed.