Manage subscription data

Warning:

Adjust no longer offers subscription recording for new customers. If you are already set up with subscription recording, reach out to your dedicated Technical Account Manager or support@adjust.com.

You can view your aggregated subscription data in Datascape. To analyze your user-level data, you can set up raw data exports.

Here, you’ll learn how to manage your subscription events, and set up callbacks and cloud storage uploads.

Subscription events

In Adjust you can measure seven main subscription events. For each subscription event, you can use a subtype to get more insight into your user data.

Subscription event	Description
Activation	User activates the subscription product for the first time.
First conversion	User does not cancel the subscription when the free trial or the free paid offer ends; converting them into a subscribed user.
Entered billing retry	When a trial has expired and is not cancelled (user did not unsubscribe the product) and if no billing issue happens, the subscription event becomes one of the following: converted_trial, converted_offer, or renewed_subscription.
Renewal	User successfully renews the subscription.
Cancellation	Transaction is not renewed at the end of the subscription period, because the user unsubscribes or the billing retry renewal fails.
Renewal from billing retry	User successfully renews the transaction after a billing issue is resolved.
Reactivation	A user who subscribed through a trial, offer, or subscription, then cancelled it, then reactivated it.

Subscription event subtypes

Subscription event	Subscription event subtypes	Description
activation	`initial_subscription`	User triggers first (paid) subscription in app
	`initial_trial`	User triggers the first free trial in app
	`initial_offer`	User triggers first (paid) offer in app with a discounted price
first_conversion	`converted_trial`	User did not cancel the subscription when the free trial ended, converting them into a subscribed user
first_conversion	`converted_offer`	User did not cancel the subscription when the first paid offer ended, converting them to a full-paying subscribed user
entered_billing_retry	`trial_in_retry`	Trial expired but renewal wasn't successful due to a billing issue. For instance: the user did not cancel when the free trial period ended, however due to an issue with the payment source they could not be charged
	`offer_in_retry`	Offer expired but renewal wasn't successful due to a billing issue. For instance: the user did not cancel when the offer period ended, however due to an issue with the payment source they could not be charged
	`subscription_in_retry`	Subscription expired but renewal wasn't successful due to a billing issue. For instance: the user did not cancel when the free subscription period ended, however due to an issue with the payment source they could not be charged
renewal	`renewed_subscription`	Successful subscription renewal
cancellation	`failed_trial`	Trial not renewed at the end of the trial period
	`failed_offer`	The first paid offer was not renewed at the end of the offer period.
	`failed_subscription`	Subscription not renewed at the end of its time period
	`failed_trial_from_retry`	Trial is not converted after the billing retry fails
	`failed_offer_from_retry`	Offer is not converted after the billing retry fails
	`failed_subscription_from_retry`	Subscription not renewed after the billing retry fails
renewal_from_billing_retry	`converted_trial_from_retry`	When the billing retry on a trial is successful and the trial is converted
	`converted_offer_from_retry`	When the billing retry on an offer is successful and the offer is converted
	`renewed_subscription_from_retry`	When the billing retry on subscription is successful and the subscription is renewed
reactivation	`reactivated_subscription`	A user who subscribed through a trial, offer, or subscription, then cancelled it, then reactivated it.

Set up subscription callbacks

Using callbacks, you can send user-level data directly to your servers—seconds after Adjust records the event.

Adjust automatically records the following subscription events.

Subscription activation
Subscription first conversion
Subscription entered billing retry
Subscription renewal
Subscription cancellation
Subscription renewal from billing retry
Subscription reactivation

When you include the {subscription_event_subtype} placeholder in your callbacks, you can receive subtypes for each subscription event. These offer greater insight into your user data.

Subscription placeholders

For a more granular look at your users’ behavior, you can add the following placeholders to your callbacks.

Placeholder	Description	Content + example value
`{subscription_event_type}`	Which of the 7 event types an action is.	activation first_conversion renewal
`{subscription_event_subtype}`	See the subscription event subtypes table for more details	initial_subscription failed_trial renewed_subscription
`{subscription_purchased_at}`	Unix timestamp of any valid purchase.	1571608922
`{subscription_expiration_time}`	Unix timestamp of the expiration of a valid subscription. The data can be in the past or future.	1571608922
`{subscription_cancelled_at}`	Unix timestamp from when the subscription stops being valid. Cannot be later than the expiration_time. If the subscription transaction fails and cannot be resolved, the value returned will be the expiration_time of the failed transaction. No value shows in the expiration_time placeholder.	1571608922
`{subscription_transaction_id}`	The value of a valid transaction. Failed transactions return no value. If there is a billing problem, the current transaction ID is returned.	230000687036600
`{subscription_original_transaction_id}`	The first transaction ID of the product subscription chain.	230000687036600
`{subscription_expired_transaction_id}`	The previous valid transaction ID - if it's the first transaction, this returns an empty value. If it’s a failed transaction, this returns the previous valid transaction ID.	230000687036600
`{subscription_environment}`	Which environment the subscription purchase happened in.	sandbox production
`{subscription_product_id}`	The subscription product type within the app.	com.product.id
`{subscription_sales_region}`	The region code of the Apple store account's registered location; Google’s region code is based on the device's physical location.	us
`{subscription_store}`	Which store the subscription purchase was triggered from.	appleappstore googleplaystore

Global callbacks

Global callbacks provide a full list of data points from all activities that Adjust records.

If you already have global callbacks set up in AppView, add our subscription event placeholders to your existing callback URL.

For a full overview of how to create global callback URLs, follow our guide here. Or, edit your callback URL using our template and example below.

Example

http://callbackserver.com/adjust_global?app_id={app_id}&app_name={app_name}&app_name_dashboard={app_name_dashboard}&app_version={app_version}&app_version_raw={app_version_raw}&app_version_short={app_version_short}&store={store}&tracker={link_token}&tracker_name={link_name}&first_tracker={first_link}&last_tracker={last_link}&last_tracker_name={last_link_name}&outdated_tracker={outdated_link}&network_name={network_name}&campaign_name={campaign_name}&adgroup_name={adgroup_name}&creative_name={creative_name}&impression_based={impression_based}&is_organic={is_organic}&rejection_reason={rejection_reason}&click_referer={click_referer}&click_time={click_time}&click_time_hour={click_time_hour}&impression_time={impression_time}&impression_time_hour={impression_time_hour}&conversion_duration={conversion_duration}&engagement_time={engagement_time}&engagement_time_hour={engagement_time_hour}&installed_at={installed_at}&installed_at_hour={installed_at_hour}&install_finish_time={install_finish_time}&install_begin_time={install_begin_time}&referral_time={referral_time}&created_at={created_at}&created_at_milli={created_at_milli}&created_at_hour={created_at_hour}&reattributed_at={reattributed_at}&reattributed_at_hour={reattributed_at_hour}&attribution_updated_at={attribution_updated_at}&time_to_uninstall={time_to_uninstall}&idfa={idfa}&idfv={idfv}&gps_adid={gps_adid}&android_id={android_id}&adid={adid}&activity_kind={activity_kind}&revenue={revenue}&currency={currency}&subscription_event={subscription_event_type}&subscription_event_subtype={subscription_event_subtype}&product_id={subscription_product_id}&sales_region={subscription_sales_region}&transaction_id={subscription_transaction_id}&expired_transaction_id={subscription_expired_transaction_id}&original_transaction_id={subscription_original_transaction_id}&subscription_store={subscription_store}&subscription_start={subscription_purchased_at}&subscription_end={subscription_expiration_time}&subscription_cancelled={subscription_cancelled_at}&environment={subscription_environment}&callback_parameter={publisher_parameters}

Subscription callback

Subscription callbacks send a single callback for all seven subscription-based events.

Example subscription callback URL

http://callbackserver.com/adjust_subscription?app_id={app_id}&app_name={app_name}&app_name_dashboard={app_name_dashboard}&app_version={app_version}&app_version_raw={app_version_raw}&app_version_short={app_version_short}&store={store}&tracker={link_token}&tracker_name={link_name}&first_tracker={first_link}&last_tracker={last_link}&last_tracker_name={last_link_name}&outdated_tracker={outdated_link}&network_name={network_name}&campaign_name={campaign_name}&adgroup_name={adgroup_name}&creative_name={creative_name}&impression_based={impression_based}&is_organic={is_organic}&rejection_reason={rejection_reason}&click_referer={click_referer}&click_time={click_time}&click_time_hour={click_time_hour}&impression_time={impression_time}&impression_time_hour={impression_time_hour}&conversion_duration={conversion_duration}&engagement_time={engagement_time}&engagement_time_hour={engagement_time_hour}&installed_at={installed_at}&installed_at_hour={installed_at_hour}&install_finish_time={install_finish_time}&install_begin_time={install_begin_time}&referral_time={referral_time}&created_at={created_at}&created_at_milli={created_at_milli}&created_at_hour={created_at_hour}&reattributed_at={reattributed_at}&reattributed_at_hour={reattributed_at_hour}&attribution_updated_at={attribution_updated_at}&time_to_uninstall={time_to_uninstall}&idfa={idfa}&idfv={idfv}&gps_adid={gps_adid}&android_id={android_id}&adid={adid}&revenue={revenue}&currency={currency}&subscription_event={subscription_event_type}&subscription_event_subtype={subscription_event_subtype}&subscription_product_id={subscription_product_id}&subscription_sales_region={subscription_sales_region}&subscription_transaction_id={subscription_transaction_id}&subscription_original_transaction_id={subscription_original_transaction_id}&subscription_store={subscription_store}&subscription_purchased_at={subscription_purchased_at}&subscription_expiration_time={subscription_expiration_time}&subscription_environment={subscription_environment}&callback_parameter={publisher_parameters}

Set up cloud storage uploads

With cloud storage uploads, you can automatically export your subscription event raw user data to cloud storage on an hourly basis.

View our full list of supported subscription event types here.

Note:

If you already have Amazon S3 or Google Cloud Storage set up in AppView, when you record subscriptions with Adjust you automatically receive cloud storage uploads for your subscription events. You still need to add subscription-related placeholders to your CSV definition to see these specific data points.

To get set up, add the subscription placeholders you want to include to your CSV definition. Read more about formatting your CSV definition.