Dynamic Yield is presented as an AI-powered Experience Optimization platform that delivers individualized experiences at every customer touchpoint: web, apps, email, kiosks, IoT, and call centers. The platform’s data management capabilities provide for a unified view of the customer, to allow the rapid and scalable creation of highly targeted digital interactions. Marketers, product managers, and engineers use Dynamic Yield for: Launching new personalization…
N/A
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.
Much more optimization possibilities. Deeper and automatic analysis of tests, product recommendations, email widgets and much more. VWO is the chimpanzee and Dynamic Yield the human.
Firebase
No answer on this topic
Best Alternatives
Dynamic Yield
Firebase
Small Businesses
Bloomreach - The Agentic Platform for Personalization
Score 8.9 out of 10
Visual Studio
Score 8.7 out of 10
Medium-sized Companies
Bloomreach - The Agentic Platform for Personalization
Score 8.9 out of 10
Visual Studio
Score 8.7 out of 10
Enterprises
Bloomreach - The Agentic Platform for Personalization
For us, it is well suited for personalization. Since we are hospitality brand, we have different rooms sales inclusion based on different segmentation like Mem or Non-mem, Global or UAE, we have to personalize our landing pages accordingly so that we show the relevant information to relevant audience. The inactivity pop up box and newsletter signup popups work good for us. It does not work well in some scenario like Dynamic Yield offers built-in analytics focused on campaign and test performance, but it’s not a replacement for tools like GA4, Adobe Analytics. It lacks deep funnel tracking or complex reporting capabilities.
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.
Provide fantastic support, both in relation to strategy/best practice and troubleshooting.
An easy to use interface, as a user who is relatively new to Dynamic Yield I find that it is an intuitive platform to use.
The ability to segment and drill down on data allows for really specific insights which, whilst not necessarily being leveraged on a testing basis, can be super valuable from a greater marketing perspective.
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).
Brand templates could need complex CSS/custom code.
We'd like to see a little "i" next to specific labels, which elaborates on what is meant. For example, when I hover over "Dynamic allocation," I get something like "An advanced form of A/B testing where the best-performing variations receive higher traffic."
Jargon (for example, for audience targeting) can be overwhelming for new users; therefore, clearer, user-friendly explanations are needed.
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.
implementation took a long time but also, DY has really proven that they are transforming and adapting their platform to be more user friendly and the right technology choice for their brand or company
Setting up strategies, audiences, and experiences is simple and fast. It is incredibly easy to modify the appearance of your site and optimize every aspect with the Dynamic Yield Personalizations. However, while the data visualization on an experience level is easy to modify and analyze, exporting the data in meaningful ways is time consuming.
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.
Overall, the support is very good. If you are a partner (my case), they assign you a customer success manager, that helps a lot. Also, there is a technical person to provide support to the partners, again a great help.
My only "complain" is that with some complex issues, the support may delay in providing you with a solution. Sometimes that can cause some tension with your client.
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.
Dynamic Yield provides far more capability and ready-to-go templates for small-medium sized businesses, as well as decent API implementation for businesses who want to have a deeper integration. The ease of implementation and faster time-to-market is why we chose Dynamic Yield.
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.
Most tests have had a positive impact on either revenue or conversion rate - quite often in double digits.
Dynamic Yield has also helped us to stop some particular initiatives through direct interaction with the customer base via questionnaires or by a test proving negative quicker than rolling out a permanent feature.
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.
