You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The preferred method of tracking revenue for a user now is to use `logRevenueV2()`in conjunction with the provided `Revenue`interface. `Revenue` instances will store each revenue transaction and allow you to define several special revenue properties (such as revenueType, productId, etc) that are used in Amplitude dashboard's Revenue tab. You can now also add event properties to the revenue event, via the revenueProperties field. These `Revenue` instance objects are then passed into `logRevenueV2` to send as revenue events to Amplitude servers. This allows us to automatically display data relevant to revenue on the Amplitude website, including average revenue per daily active user (ARPDAU), 1, 7, 14, 30, 60, and 90 day revenue, lifetime value (LTV) estimates, and revenue by advertising campaign cohort and daily/weekly/monthly cohorts.
188
+
The preferred method of tracking revenue for a user now is to use `logRevenueV2()`in conjunction with the provided `Revenue`interface. `Revenue` instances will store each revenue transaction and allow you to define several special revenue properties (such as revenueType, productId, etc) that are used in Amplitude dashboard's Revenue tab. You can now also add event properties to the revenue event, via the eventProperties field. These `Revenue` instance objects are then passed into `logRevenueV2` to send as revenue events to Amplitude servers. This allows us to automatically display data relevant to revenue on the Amplitude website, including average revenue per daily active user (ARPDAU), 1, 7, 14, 30, 60, and 90 day revenue, lifetime value (LTV) estimates, and revenue by advertising campaign cohort and daily/weekly/monthly cohorts.
189
189
190
190
Each time a user generates revenue, you create a `Revenue` object and fill out the revenue properties:
| quantity | Integer | Required: the quantity of products purchased. Defaults to 1 if not specified. Revenue = quantity * price | 1 |
202
202
| price | Double | Required: the price of the products purchased (can be negative). Revenue = quantity * price | null |
203
203
| revenueType | String | Optional: the type of revenue (ex: tax, refund, income) | null |
204
-
| revenueProperties | Object | Optional: an object of event properties to include in the revenue event | null |
204
+
| eventProperties | Object | Optional: an object of event properties to include in the revenue event | null |
205
205
206
-
Note: the price can be negative, which might be useful for tracking revenue lost, for example refunds or costs.
206
+
Note: the price can be negative, which might be useful for tracking revenue lost, for example refunds or costs. Also note, you can set event properties on the revenue event just as you would with logEvent by passing in a object of string key value pairs. These event properties, however, will only appear in the Event Segmentation tab, not in the Revenue tab.
0 commit comments