Skip to content

Analytics

The Cal-ITP Benefits application, currently live at https://benefits.calitp.org/, uses Amplitude to collect specific user and event data properties to analyze application usage.

Information not collected

The following user attributes are not collected:

  • IP address
  • Designated Market Area (DMA)

See the Amplitude analytics code on GitHub.

User information collected

A combination of default and application-specific custom user properties are collected for each user who visits the Benefits web application.

Default Amplitude user properties collected

The following attributes are collected from the browser of every user who visits the application, provided the browser does not block the tracking library:

User property Description Example value(s)
Carrier The device’s carrier. Verizon
Country Country of the event. This is pulled using GeoIP. United States
City City of the event. This is pulled using GeoIP. San Francisco
Device family Family of the device. Apple iPhone, Samsung Galaxy Tablet, Windows
Device type Specific type of device. Apple iPhone 6, Samsung Galaxy Note 4, Windows
Language Language of the device. English
Library Library used to send the event. Amplitude-iOS/3.2.1, HTTP/1.0
OS Operating system is the name of the user’s mobile operating system or browser. Operating system version is the version of the users’ mobile operating system or browser. iOS 9.1, Chrome 46
Platform Platform of the product. Web
Region Region (e.g. state, province, county) of the event. This is pulled using GeoIP. California
Start version First version of the application identified for the user. 1.0.0
Version Current verison of the application identified for the user 1.0.0

Read more about each property on the Amplitude documentation.

Custom user properties collected

The following custom user attributes are collected when the user performs specific actions on the application, like selecing an eligibility type or transit agency:

User property Description Example value(s)
enrollment_flows Enrollment flows chosen by user  [veteran]
eligibility_verifier How eligibility for flow is verified cdt-logingov
referrer URL that the event came from  https://benefits.calitp.org/help/
referring_domain Domain that the event came from  benefits.calitp.org
transit_agency Agency chosen by the user  Monterey-Salinas Transit
user_agent User’s browser agent  Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36

Event information collected

Information is collected on key user actions on the app, called events. Read about each event on the Amplitude event documentation for Benefits. Each event is categorized within one of four categories: core, authentication, eligibility or enrollment.

Core events

These events track when a user clicks on a link on the application.

  • changed language
  • clicked link
  • viewed page

Read more on each of these events on the Amplitude event documentation for Benefits, filtered by Core.

Authentication events

These events track the progress of a user going through the authentication process of both signing in and optionally signing out.

  • canceled sign in
  • finished sign in
  • finished sign out
  • started sign in
  • started sign out

Read more on each of these events on the Amplitude event documentation for Benefits, filtered by Authentication.

Eligibility events

These events track the progress of a user choosing an enrollment flow and completing eligibility verification.

  • selected enrollment flow
  • started eligibility
  • returned eligibility

Read more on each of these events on the Amplitude event documentation for Benefits, filtered by Eligibility.

Enrollment events

These events track the progress of a user who has successfully verified their eligibility and is enrolling their payment card with the system.

  • finished card tokenization
  • returned enrollment
  • started card tokenization

Read more on each of these events on the Amplitude event documentation for Benefits, filtered by Enrollment.

Key metrics

Various key metrics are collected and analyzed, including:

  • Number of users who successfully completed authentication: Users who started sign in, finished sign in
  • Number of users who successfully verified eligibility: Users who completed the above and selected enrollment flow, started eligibility, returned eligibility with a status of True
  • Numbers of users who successfully completed enrollment: Users who completed all of the above and started card tokenization, finished card tokenization and returned enrollment with a status of success