Event Reference (v1) / App Events
App Subscribe / app_subscribe
Measures when a user creates a new subscription to a recurring product/service - Software-as-a-Service (SaaS), being a common business model.
We break our own rules here by using "app" in instead of "application". The word "application" can be confusing for certain industries like recruitment where an "application" carries much different meaning (e.g. job application) than a software application. The term "App" is more commonly used in the context of software applications which is what this event is meant to measure.
It may make sense to measure this with a separate e-commerce event. Certain adtech/martech platforms (e.g. GA4/Meta) have specific schemas and requirements for measuring e-commerce transactions. Custom event names like app_subscribe are often easier to understand in the context of a subscription billing model than something like purchase which is more product focused.
You will likely need the help of a product team to implement this event properly. This event is sometimes triggered by a user action in an application - and sometimes is processed in a pure offline environment (such as through a CRM and payment gateway directly).
-
- Name
- Event Name Required
- Value
- event: app_subscribe
-
- Name
- Plan Optional
- Type
- plan: string
- Description
The plan the user subscribed to. For example, if your application offers a basic, pro, and enterprise plan you would pass an appropriate value depending on what plan was subscribed to.
- E.g.
pro
-
- Name
- Billing Frequency Optional
- Type
- billing_frequency: string
- Description
The frequency at which the user will be billed. For example, if your application offers monthly, quarterly, and annual billing you would pass an appropriate value depending on what frequency was selected.
- E.g.
annual
-
- Name
- Includes Trial Period Optional
- Type
- includes_trial_period: boolean
- Description
Whether the sign up includes a free trial or evaluation period.
- E.g.
true
-
- Name
- Value Optional
- Type
- value: number
- Description
A generic numeric value that can be used for any purpose. Most commonly used to assign a monetary value to an event or interaction.
- E.g.
100
-
- Name
- Predicted Lifetime Value Optional
- Type
- predicted_ltv: integer
- Description
An estimated value of how much revenue the user will generate over their lifetime as a customer. This value is typically calculated based on historical data and is used to inform marketing and sales strategies.
- E.g.
2500