ActivationPal

Automated Events in Apps: What SDKs Log

Automated events are app events an SDK records without a tracking call, such as first open, sessions and screen views. They count installs and engagement, not business steps. Add manual events for the steps that lead to revenue.

What are automated events?

An automated event is an event the analytics SDK sends on its own once it is installed. Firebase puts it this way: with the Google Analytics for Firebase SDK you do not need to write any additional code to collect them.

ActivationPal works the same way for two events. Calling configure once at launch sends first_open once per install, and app_open for every new session: a launch, or a return to the foreground after 30 or more minutes in the background. The native Swift SDK and the Flutter package also capture the Apple Ads attribution token at first open and send it as install_attribution.

What Firebase and Mixpanel log automatically

SDKAutomatic eventsControl
Firebasefirst_open, session_start, user_engagement, screen_view, in_app_purchase, app_update, os_update. Android only: app_remove, app_clear_data, app_store_refund and app_store_subscription_cancelScreen tracking can be disabled, which stops the automatic firebase_screen_id and firebase_screen_class parameters
MixpanelApp lifecycle events, through the legacy trackAutomaticEvents optionOff by default in Swift, passed as false in the Android and Flutter setup examples. Mixpanel marks it as not recommended
ActivationPalfirst_open, app_open, install_attributionSent by configure

Firebase defines the main ones like this:

  • first_open: the first time a user launches the app after installing or re-installing it.
  • session_start: when a user engages the app. A session ID and session number are generated with it.
  • user_engagement: when the app is in the foreground for at least one second.
  • screen_view: when a screen transition occurs and the screen name, class or ID differs from the previous one.
  • in_app_purchase: when a user completes a purchase processed by the App Store or Google Play, including an initial subscription.

Limits of automated events

first_open is not a download count. Firebase states it is triggered when the user first uses the app, not when the app lands on the device, so it will differ from the downloads in App Store Connect or Google Play Console.

in_app_purchase does not cover everything. Firebase says it does not measure paid-app purchase revenue or refunds, and that logging the same purchase manually as well can report it twice. Several events, such as app_remove, app_store_refund and app_store_subscription_cancel, exist on Android only.

The larger limit is meaning. A first-open count and a session count say people arrived and came back. They do not say how far anyone got through onboarding or whether they saw a paywall. With 1,000 first opens and 400 completed onboardings, completion is 40%, and no automated event can give you the 400.

When to add manual events

Log a manual event for every step you want to measure that the SDK cannot see:

  • Each onboarding screen and the moment onboarding is completed.
  • Each paywall view, plan selection, purchase and dismissal.
  • Any action that defines activation in your app, such as a first workout logged or a first export.

Firebase lets you log your own events with logEvent, up to 500 different event types. Event names are case-sensitive, so Share_Image and share_image are two events.

In ActivationPal these are explicit calls: onboardingStep, onboardingCompleted, paywallShown, paywallPlanSelected, paywallPurchased, paywallDismissed, and track for your own events.

ActivationPal.onboardingStep(0, id: "goal", answer: "lose_weight")
ActivationPal.onboardingCompleted()
ActivationPal.paywallShown("onboarding")
ActivationPal.paywallPurchased("yearly")
ActivationPal.track("workout_logged", ["type": "run", "duration_min": 42])

The two kinds work together. Every funnel stage counts unique devices from the install cohort, which is defined by the automated first_open, so no stage can exceed 100% of installs. Purchases, trials and renewals arrive server-side from RevenueCat or Superwall webhooks. The full list is in the events docs, and pirate metrics shows how acquisition, activation and revenue stages map to events. For a pre-launch view of what to measure first, see how to launch an app.

How to check what your SDK sends

Run a debug build, use the app for a minute, then send it to the background and look at what arrived.

  • ActivationPal: events flush about every 10 seconds, immediately at 20 buffered events and when the app goes to the background. Debug builds print [ActivationPal] flushed N event(s) in the Xcode console, and each event carries an env of debug, testflight or release. Events appear in the dashboard live feed seconds later.
  • Firebase on iOS: in Xcode choose Product > Scheme > Edit scheme > Run > Arguments, and add -FIRAnalyticsVerboseLoggingEnabled under Arguments Passed On Launch. The console then prints automatic and manual events. The Analytics > Events dashboard updates only periodically through the day, so use the console for immediate checks.
  • Mixpanel: the SDK sends batches every 60 seconds while the app runs and when it moves to the background. Call flush() to send the queue at once.

Frequently asked questions

Are automated events the same as autocapture?

No. Automated events are a fixed list the SDK names and sends, such as first_open or Firebase's screen_view. Autocapture is a separate method that records interactions without you naming them. The autocapture vs manual tracking article covers that method. ActivationPal's other events are explicit calls.

Do automated events count toward my event limit?

In ActivationPal an event is any recorded action or update, including an app open, so app_open counts alongside onboarding steps, paywall views and purchases. Returning users count too, which is why event volume follows total activity rather than installs.

Can I turn automated events off?

In Mixpanel, trackAutomaticEvents is off by default, so you opt in rather than out. In Firebase, you can disable screen tracking, which removes the automatic screen parameters.