Chatbot Analytics in Mobile Apps: Funnels, Conversions, A/B Tests

TRUETECH is engaged in the development, support and maintenance of iOS, Android, PWA mobile applications. We have extensive experience and expertise in publishing mobile applications in popular markets like Google Play, App Store, Amazon, AppGallery and others.

Development and support of all types of mobile applications:

Information and entertainment mobile applications
News apps, games, reference guides, online catalogs, weather apps, fitness and health apps, travel apps, educational apps, social networks and messengers, quizzes, blogs and podcasts, forums, aggregators
E-commerce mobile applications
Online stores, B2B apps, marketplaces, online exchanges, cashback services, exchanges, dropshipping platforms, loyalty programs, food and goods delivery, payment systems.
Business process management mobile applications
CRM systems, ERP systems, project management, sales team tools, financial management, production management, logistics and delivery management, HR management, data monitoring systems
Electronic services mobile applications
Classified ads platforms, online schools, online cinemas, electronic service platforms, cashback platforms, video hosting, thematic portals, online booking and scheduling platforms, online trading platforms

These are just some of the types of mobile applications we work with, and each of them may have its own specific features and functionality, tailored to the specific needs and goals of the client.

Showing 1 of 1All 1734 services
Chatbot Analytics in Mobile Apps: Funnels, Conversions, A/B Tests
Medium
~3-5 days
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_mobile-applications_feedme_467_0.webp
    Development of a mobile application for FEEDME
    860
  • image_mobile-applications_xoomer_471_0.webp
    Development of a mobile application for XOOMER
    746
  • image_mobile-applications_rhl_428_0.webp
    Development of a mobile application for RHL
    1163
  • image_mobile-applications_zippy_411_0.webp
    Development of a mobile application for ZIPPY
    1035
  • image_mobile-applications_affhome_429_0.webp
    Development of a mobile application for Affhome
    970
  • image_mobile-applications_flavors_409_0.webp
    Development of a mobile application for the FLAVORS company
    563

Chatbot Funnels and Conversions: Analytics in Mobile Apps

Many apps implement chatbots, but without analytics, they remain a black box. You don't know how many users complete the funnel, where they drop off, or which scenario converts best. We solve this by embedding detailed analytics directly into the app. Our engineers configure event collection, build funnels, and calculate conversions so you can see every user step and improve the bot in time.

Why Chatbot Analytics Is Critical for Mobile Apps?

Without analytics, you're flying blind. Drop-off points stay hidden, and budget spent on developing new scenarios goes to waste. Analytics gives answers: which scenario retains users, where they get stuck, and which steps lead to the goal. With these data, you can iteratively improve the bot, boosting conversion 2-3 times. Example: one of our clients after implementing analytics increased lead conversion by 140% in a month.

Chatbot Funnel: From Logging to Visualization

A funnel is a sequence of steps (states) in a scenario. User starts the bot → sees greeting → answers qualification question → clicks transition button → leaves contact → receives offer. On the backend, each event is logged with user_id, conversation_id, step_name, timestamp. The funnel is built by aggregation: count of unique users who reached each step.

-- Example funnel aggregation
SELECT
    step_name,
    COUNT(DISTINCT user_id) as users,
    LAG(COUNT(DISTINCT user_id)) OVER (ORDER BY step_order) as prev_step_users
FROM conversation_events
WHERE bot_id = $1 AND created_at BETWEEN $2 AND $3
GROUP BY step_name, step_order
ORDER BY step_order;

Conversion per step = users / prev_step_users. The mobile app receives ready funnel data via API.

Funnel Visualization

Classic funnel — descending horizontal bars. Bar color encodes step conversion: green for >70%, orange for 40-70%, red for <40%. This immediately highlights bottlenecks.

// Flutter — custom funnel widget
class FunnelChart extends StatelessWidget {
  final List<FunnelStep> steps;

  @override
  Widget build(BuildContext context) {
    final maxUsers = steps.first.users;
    return Column(
      children: steps.map((step) {
        final widthFraction = step.users / maxUsers;
        final conversion = step.conversionFromPrev;
        return Padding(
          padding: const EdgeInsets.symmetric(vertical: 2),
          child: Column(
            crossAxisAlignment: CrossAxisAlignment.start,
            children: [
              Text(step.name, style: Theme.of(context).textTheme.labelMedium),
              Row(
                children: [
                  Expanded(
                    child: FractionallySizedBox(
                      widthFactor: widthFraction,
                      child: Container(
                        height: 36,
                        decoration: BoxDecoration(
                          color: _conversionColor(conversion),
                          borderRadius: BorderRadius.circular(4),
                        ),
                        alignment: Alignment.centerRight,
                        padding: const EdgeInsets.only(right: 8),
                        child: Text(
                          '${step.users} (${(conversion * 100).toStringAsFixed(1)}%)',
                          style: const TextStyle(color: Colors.white, fontSize: 12),
                        ),
                      ),
                    ),
                  ),
                ],
              ),
            ],
          ),
        );
      }).toList(),
    );
  }

  Color _conversionColor(double conversion) {
    if (conversion > 0.7) return Colors.green;
    if (conversion > 0.4) return Colors.orange;
    return Colors.red;
  }
}

Metrics, Dashboard, and A/B Tests

Besides the funnel, the chatbot analytics dashboard includes several blocks.

Operational Metrics (for selected period)

  • Total new conversations
  • Average conversation duration
  • % conversations handed over to operator
  • % conversations with no user response (dropped after first bot message)

Conversion Metrics

  • Target events (depends on bot: submitted application, left contact, clicked offer button)
  • Conversion by channel: Telegram vs. WhatsApp vs. Web Widget

Retention

  • How many users returned to the bot after 7 days, 30 days

Period is selected via date picker — last 7 days / last 30 days / custom range. Custom range on mobile uses showDateRangePicker (Flutter) or UICalendarView (iOS 16+).

Scenario Comparison (A/B)

If the bot runs A/B test scenarios, we show parallel funnels. Table: rows — funnel steps, columns — variant A and variant B with conversion per step. The cell with the better result gets green background.

Step Variant A Variant B
Start 1,240 (100%) 1,198 (100%)
Qualification 890 (71.8%) 956 (79.8%)
Offer 320 (35.9%) 412 (43.1%)
Application 98 (30.6%) 145 (35.2%)

With analytics, conversion is 2-3x higher than without. Our clients report ROI on analytics investment within 3-6 months, yielding significant budget savings.

How We Ensure Data Accuracy?

We use proven backend solutions: server-side event logging with unique session ID and timestamps. To eliminate duplicates, we deduplicate by (user_id, conversation_id, step_name). Data is transferred to the mobile app via REST API with aggregated metrics, reducing client load. The entire pipeline is covered by unit and integration tests — over 5 years of experience ensures reliability.

What's Included in the Work and How We Do It

  • Dashboard with key metrics and period switch
  • Funnel visualization with color-coded conversion
  • Breakdown by channel (Telegram, WhatsApp, Web)
  • A/B variant comparison table
  • Drill-down: tap on funnel step → list of users who stopped at that step
Details on drill-down

When tapping a funnel step, we display a list of users who did not proceed to the next step. For each, we show ID, last action timestamp, and channel. This allows analyzing behavior of specific segments.

Work Process

  1. Analysis: study bot scenarios, define key events and goals
  2. Design: develop logging schema and API for mobile app
  3. Implementation: configure backend, write visualization widgets in Flutter/Swift/Kotlin
  4. Testing: verify funnel accuracy and calculation correctness
  5. Deployment: deploy dashboard in the app, train the team

Timelines and Cost

Basic integration with dashboard and funnel takes 5-7 business days. Cost is calculated individually after requirements analysis. Project assessment is free — contact us. ROI on analytics investment is 3-6 months due to conversion increase.

Get a consultation: reach out to discuss your chatbot. Request a free audit of your bot.

Mobile App Analytics: Firebase, Amplitude, AppsFlyer and Attribution

Our team regularly encounters projects where analytics is already "set up" but yields no real insights. A typical example is a startup with 50k DAU: tracking dozens of events without a single answer to the question "why don't users reach payment?". In two weeks we built a basic funnel and found that 70% of users drop off at the phone number verification screen. After fixing the bug, retention increased by 12%. The takeaway: analytics should start with specific questions, not tracking everything indiscriminately.

Why Event Taxonomy is the Foundation of Mobile App Analytics?

Firebase Analytics, Amplitude, Mixpanel — technically similar. The difference lies in what you put into them. A common mistake: events like screen_view, button_tap_1, button_tap_2 without context. A month later, no one remembers what button_tap_2 means.

Proper taxonomy: object + action + context. product_viewed, checkout_started, payment_completed with parameters product_id, category, price, source. This allows building funnels, cohort analysis, and retention without additional tracking.

We document the naming convention in a tracking plan — a document (Google Sheet or Amplitude Data Catalog) describing every event, its parameters, and triggering conditions. The tracking plan is synced with the analytics team before development begins, not after. This approach ensures that data remains interpretable months later and doesn't become a dump. Experience from 50+ projects confirms: without a tracking plan, analytics maintenance costs increase 2-3 times due to rework.

What Should You Choose for Mobile App Analytics: Firebase, Amplitude, or Mixpanel?

The table below highlights key differences between the three popular platforms. Choice depends on budget, traffic, and tasks.

Criteria Firebase Analytics Amplitude Mixpanel
Free limit Unlimited (Spark plan) Up to 10M events/month Up to 1K MTU/month (Special)
Data latency Up to 24 hours (standard) Minutes (real-time) Minutes (real-time)
Funnels and cohorts Basic funnels, limited count Deep funnels, Journeys, cohorts Funnels, Retention, Insights
BigQuery export Yes (free, raw data) Yes (subscription) Yes (Enterprise)
Session Replay No Yes (iOS/Android SDK) No
Ad integration Google Ads (native) Via Universal Links Via partners

Firebase Analytics — free, deep integration with Google Ads, BigQuery export for raw data. Limitations: data latency up to 24 hours, limited funnels. For startups with Google Ads traffic, it's the first choice.

Amplitude — product analytics focused on cohorts and user journeys. Journeys (formerly Pathfinder) shows actual paths between events — not assumed funnels but real routes. Session Replay records sessions for UX analysis. The free tier up to 10M events/month is enough for most products at launch.

Mixpanel — close to Amplitude, stronger in real-time segmentation. Insights, Funnels, Retention cover 90% of product analysts' tasks.

How to Solve Multi-Channel Attribution with AppsFlyer?

Knowing where a user came from is a separate task. Firebase Attribution works only within the Google ecosystem. For multi-channel attribution (Facebook Ads, TikTok, Apple Search Ads, programmatic), an MMP (Mobile Measurement Partner) is needed.

AppsFlyer is the market leader. OneLink — universal deep link working on iOS and Android, correctly attributing installs from any channel. Protect360 — built-in fraud protection (fake installs, click injection on Android). Adjust and Branch are competitors with similar features. Branch excels in deep linking; Adjust is popular in gaming.

According to Apple, with iOS 14.5, apps must obtain user permission via ATT before collecting IDFA for tracking. AppsFlyer uses probabilistic matching (IP + user agent + timing) for these users — accuracy is lower but better than nothing. SKAdNetwork and Privacy Preserving Attribution provide aggregated data from Apple with a 24-72 hour delay.

How to Set Up Crash Analytics to Not Miss Bugs?

Firebase Crashlytics is the standard for crash reporting. It automatically groups crashes by stack trace, shows affected users %, and sends velocity alerts when crash rate increases by more than 10% per hour.

Important: symbolication. On iOS, .dSYM files must be automatically uploaded with each build — via Fastlane upload_symbols_to_crashlytics or Xcode Cloud built-in. Without symbols, crashes in Crashlytics appear as memory addresses. This happens more often than expected when switching to a new CI — in one project with 500k users, we found that 40% of crashes remained unsymbolicated due to a missing CI/CD step. After automation, bug response time dropped from 3 hours to 15 minutes.

For React Native and Flutter, @sentry/react-native and sentry_flutter provide additional context: breadcrumbs, network requests before the crash, Redux/Provider state.

Below is a comparison of popular crash analytics tools to choose according to your needs.

Criteria Firebase Crashlytics Sentry Instabug
Free limit Unlimited (Spark) 5k events/month 250 MAU
Grouping By stack trace + parameters By fingerprint By stack trace + metadata
Symbolication Automatic (via file) Automatic (via CLI) Automatic
Velocity alerts Yes (by % change) Yes (by count) Yes (by threshold)
Extra context Logs, Keys, Custom Keys Breadcrumbs, User, Tags User steps, network requests
Price Free (in Firebase) Paid plans available Paid plans available

Environment Setup

Three environments with separate Firebase projects: dev, staging, production. Mixing analytics from test sessions and production is a common mistake that skews all metrics. On iOS via GoogleService-Info.plist per scheme, on Android via google-services.json in each flavor folder.

Timelines: basic analytics with Firebase + Crashlytics — 3-5 days. Full tracking plan + Amplitude/Mixpanel with funnels and cohorts — 2-3 weeks. Attribution via AppsFlyer with deep linking and fraud protection — 1-2 weeks. Cost is calculated individually based on integration complexity.

What Is Included in Our Work

As part of analytics implementation, we provide:

  • Development and approval of a tracking plan with product and marketing teams.
  • SDK integration (Firebase, Amplitude, Mixpanel, AppsFlyer) considering your stack (Swift/Kotlin/Flutter/React Native).
  • Setup of funnels, cohorts, dashboards, and alerts.
  • Automation of symbolication and .dSYM upload via Fastlane.
  • Documentation of events and parameters.
  • Team training on the analytics platform.
  • Two weeks of post-release support and tracking adjustments.

Our experience: 7 years of analytics implementation and over 80 successful projects in mobile development. We guarantee data correctness and transparency at every stage.

Contact us for a consultation on setting up analytics for your app. Request an audit of your current analytics — and we will show you which metrics you are losing.