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.
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. Read more on how to manage subscription data.
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)
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.
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)