Revenue - Configuration Reference

Enterprise

This endpoint is part of Countly Enterprise. To get access, contact sales or compare versions. Existing customers can reach the support portal with questions.

Overview

This page explains Revenue feature settings and how they affect endpoint behavior. It does not define a standalone public endpoint.

Configuration

Revenue tracking uses app plugin config:

• apps.plugins.revenue.iap_events (Array of event keys)

These event keys are treated as purchase events during user-property updates and paying-user calculations.

Operational Impact

When an incoming SDK event matches configured iap_events and has sum:

• User profile totals are updated (tp, tpc, lp, lpa, purchased).
• Aggregated paying-user counters are updated in time buckets.
• Revenue analytics endpoint (/o/revenue) can report p values and purchase totals.

Best Practices

• Keep event names stable and consistent.
• Ensure purchase events always include valid sum values.
• Normalize currency before sending events when multi-currency sources are used.

Related Endpoints

• Revenue - Analytics

Implementation details

Database Collections

Collection	Used for	Data touched by this endpoint
countly.apps	App configuration and metadata	Stores app-level feature settings and metadata used or modified by this endpoint.
countly.app_users{appId}	Per-app user profiles	Stores user-level properties and profile fields affected by this endpoint.
countly.users	User aggregates	Stores app-level user aggregate counters/metrics read or updated by this endpoint.