We constantly publish updates to our documentation, which may not yet be available in your language. For the most current information, use the English version.

for Marketers

Subscription callbacks

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

Adjust records the following subscription events:

Activations
(iOS only) Billing retry
Cancellations
Discounted offers
Expirations
Grace periods
(Android only) On Hold
(Android only) Paused

Price accepted
(iOS only) Price declined
Reactivations
(iOS only) Refunds
Renewals
Renewals from Billing Retry
Revoked
Trials started

Subscription events

Previous version of subscriptions

Recommended placeholders

Placeholder	Description	Example
`{subscription_event_type}`	Grouped, derived from subtype.	`activation` `first_conversion` `renewal`
`{subscription_event_subtype}`	See the subscription event subtypes table for more details. This is available only on the previous version of subscriptions. If you have upgraded to the latest version of subscriptions, do not use this.	`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`

Note:

If placeholder data is not available, it will be dropped from the callback.

Callback example

Callback URL with placeholdersUnencoded (Do not use as is)

Callback URL populated with values

https://mynetworkserver.com/mobile_attribution?gps_adid={gps_adid}&idfa={idfa}&tracker_name={link_name}&app_name={app_name}&activity_kind={activity_kind}&created_at={created_at}&reattributed_at={reattributed_at}&reattributed_at_hour={reattributed_at_hour}&subscription_event={subscription_event_type}&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 example (Previous version of Subscriptions)

Callback URL with placeholdersUnencoded (Do not use as is)

Callback URL populated with values

https://mynetworkserver.com/mobile_attribution?gps_adid={gps_adid}&idfa={idfa}&tracker_name={link_name}&app_name={app_name}&activity_kind={activity_kind}&created_at={created_at}&reattributed_at={reattributed_at}&reattributed_at_hour={reattributed_at_hour}&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}

Other recommended placeholders

We also advise that you include the following placeholders in all callback URLs. These placeholders will ensure that you always receive basic information that you can use to identify the app, link, data point, and device to which the rest of your callback data belongs.

Placeholder	Description	Example
`{gps_adid}`	Google Play Store advertising ID (Android only)	38400000-8cf0-11bd-b23e-10b96e40000d
`{idfa}`	ID for advertisers (iOS only)	8C6CBCOD-5F43-4765-A6E6-84DFF3D24707
`{idfv}`	ID for vendors (iOS only)	CCB300A0-DE1B-4D48-BC7E-599E453B8DD4
`{adid}`	Adjust device ID	18546f6171f67e29d1cb983322ad1329
`{tracker}`	Adjust link token	abc123
`{tracker_name}`	Current link name as defined in Campaign Lab	Network1%3A%3AChristmas%3A%3AReindeers%3A%3A320x70_en
`{app_name}`	Name of the app	MyApp
`{activity_kind}`	This will allow you to determine the data point: impression, click, install, rejected install, rejected reattribution, session, reattribution, uninstall, reinstall, reattribution reinstall, updated attribution, in-app event, or ad spend (`cost_updated`)	rejected_reattribution
`{created_at}`	The timestamp for when the data point occurred	1404214665