Import payments

To send payments to MyTracker, use the following methods:

• customRevenue and customRevenueBatch for custom revenue
• googlePlayProductTransaction, googlePlaySubscriptionTransaction and googlePlaySubscriptionToken for Google Play in-app purchases and subscriptions
• appStoreProductTransaction, appStoreSubscriptionTransaction, and appStoreSubscriptionReceipt for App Store in-app purchases and subscriptions

Google Play payments

MyTracker can track in-app purchases and subscriptions automatically (see the Revenue tracking section). But if the automatic tracking is not enough, or there are problems, you can upload payments using the S2S API.

Let's consider some examples of using S2S API methods:

Example 1 — Import historical data on purchases

When MyTracker has no data on in-app purchases, for example, made before MyTracker SDK integration, use the method googlePlayProductTransaction.

Example 2 — Import historical data on subscriptions

When MyTracker has no data on subscriptions, for example, made before the MyTracker SDK integration:

1. Import historical data using googlePlaySubscriptionTransaction
2. Enable tracking of future renewals using googlePlaySubscriptionToken

Example 3 — Track active subscriptions

If MyTracker does not track a subscription automatically (for example, subscription made before the MyTracker SDK integration):

1. Import historical data using googlePlaySubscriptionTransaction
2. Enable renewals tracking using googlePlaySubscriptionToken

Example 4 — Import data after configuring a verification

If you took a while to add the verification key to MyTracker, and as a consequence, did not verify the first payments:

1. Ensure you add Google Play credentials to MyTracker.
2. Import lacking purchase data using googlePlayProductTransaction
3. Import lacking subscription data using googlePlaySubscriptionTransaction
4. Enable subscription tracking using googlePlaySubscriptionToken

Example 5 — Import data after tracking failure

When MyTracker has no data on purchases and subscriptions due to a failed update to the app and a broken tracking setting:

1. Import lacking purchase data using googlePlayProductTransaction
2. Import lacking subscription data using googlePlaySubscriptionTransaction
3. Enable subscription tracking using googlePlaySubscriptionToken

If you retransmitted data or loaded previously tracked transactions, there will be no error because MyTracker removes duplicates

googlePlayProductTransaction

Use the googlePlayProductTransaction method to send Google Play in-app purchases.

To verify a transaction, use one of the following parameters:

• token — MyTracker will send a purchase confirmation request to the Google Play API. If the payment is valid, MyTracker will classify the purchase as a verified transaction; if not, the transaction will be saved as unverified.
• isVerified — MyTracker classifies the purchase as a verified transaction by default.

If you pass neither token nor isVerified, or pass both parameters at once, the purchase confirmation request will not be processed.

Import historical data on purchases in chronological order, otherwise, the information on the first payments will be distorted.

End-point: https://tracker-s2s.my.com/v1/googlePlayProductTransaction/?idApp=XXX

Required parameter: a user identifier customUserId and/or one of the device identifiers: instanceId, gaid, androidId, appSetId (transactions will be related to the user and/or the device), eventTimestamp, as well as parameters from the table below.

* — required parameter.

googlePlaySubscriptionTransaction

Use the googlePlaySubscriptionTransaction method to send Google Play subscription transactions.

Import historical data on subscriptions in chronological order, otherwise, the information on the first payments will be distorted.

End-point: https://tracker-s2s.my.com/v1/googlePlaySubscriptionTransaction/?idApp=XXX

Required parameters: a user identifier customUserId and/or one of the device identifiers: instanceId, gaid, androidId, appSetId (transactions will be related to the user and/or the device), eventTimestamp, as well as parameters from the table below.

* — required parameter.

googlePlaySubscriptionToken

Use the googlePlaySubscriptionToken method to send information about an active subscription. Based on the passed subscription ID, MyTracker will detect the latest renewal and track future renewals automatically.

All future subscription payments will be are related to the device and user that you specify in the method

We recommend you pass the subscriptionPeriod parameter. With this parameter, MyTracker will be able to calculate the time of the latest renewal, and in the future, will be able to time renewals even if Google Play delays data. Without subscriptionPeriod, the latest renewal and all further renewals will be logged at the moment of data receipt from Google Play.

End-point: https://tracker-s2s.my.com/v1/googlePlaySubscriptionToken/?idApp=XXX

Required parameter: a user identifier customUserId and/or one of the device identifiers: instanceId, gaid, androidId, appSetId (transactions will be related to the user and/or the device), as well as parameters from the table below.

* — required parameter.

App Store payments

MyTracker can track in-app purchases and subscriptions automatically (see the Revenue tracking section). But if the automatic tracking is not enough, or there are problems, you can upload payments using the S2S API.

Let's consider some examples of using S2S API methods:

Example 1 — Import historical data on purchases

When MyTracker has no data on in-app purchases, for example, made before MyTracker SDK integration, use the method appStoreProductTransaction.

Example 2 — Import historical data on subscriptions

When MyTracker has no data on subscriptions, for example, made before the MyTracker SDK integration:

1. Import historical data using appStoreSubscriptionTransaction.
2. Send the receipt for the active subscriptions using appStoreSubscriptionReceipt.

Example 3 — Track active subscriptions

If MyTracker does not track a subscription automatically, for example, subscription made before the MyTracker SDK integration, import subscription data using appStoreSubscriptionReceipt.

Example 4 — Import data after configuring a verification

If you took a while to add the verification key to MyTracker, and as a consequence, missed some of the renewals:

1. Ensure you add App Store credentials to MyTracker.
2. Import lacking subscription data using appStoreSubscriptionTransaction.
3. Enable subscription tracking using appStoreSubscriptionReceipt.

Example 5 — Import data after tracking failure

When MyTracker has no data on purchases and subscriptions due to a failed update to the app and a broken tracking setting:

1. Import lacking purchase data using appStoreProductTransaction.
2. Import lacking subscription data using appStoreSubscriptionTransaction.
3. Enable subscription tracking using appStoreSubscriptionReceipt.

If you retransmitted data or loaded previously tracked transactions, there will be no error because MyTracker removes duplicates

appStoreProductTransaction

The appStoreProductTransaction method is in beta testing. If you have any questions, please contact our support team

Use the appStoreProductTransaction method to send App Store in-app purchases. All uploaded payments will be saved in MyTracker as verified transactions.

Import historical data on purchases in chronological order, otherwise, the information on the first payments will be distorted.

End-point: https://tracker-s2s.my.com/v1/appStoreProductTransaction/?idApp=XXX

Required parameters: a user identifier customUserId and/or one of the device identifiers: instanceId, idfa, iosVendorId (transactions will be related to the user and/or the device), eventTimestamp, as well as parameters from the table below.

* — required parameter.

appStoreSubscriptionTransaction

The appStoreSubscriptionTransaction method is in beta testing. If you have any questions, please contact our support team

Use the appStoreSubscriptionTransaction method to send App Store subscription transactions.

Import historical data on subscriptions in chronological order, otherwise, the information on the first payments will be distorted.

End-point: https://tracker-s2s.my.com/v1/appStoreSubscriptionTransaction/?idApp=XXX

Required parameters: a user identifier customUserId and/or one of the device identifiers: instanceId, idfa, iosVendorId (transactions will be related to the user and/or the device), eventTimestamp, as well as parameters from the table below.

* — required parameter.

appStoreSubscriptionReceipt

The appStoreSubscriptionReceipt method is in beta testing. If you have any questions, please contact our support team

Use the appStoreSubscriptionReceipt method to send information about an active subscription. Based on the passed receipt, MyTracker will send a request to the App Store API, get historical subscription transactions and track future renewals automatically.

All in-app purchases and subscriptions from the receipt will be related to the device or/and user that you specify in the method

End-point: https://tracker-s2s.my.com/v1/appStoreSubscriptionReceipt/?idApp=XXX

Required parameters: a user identifier customUserId and/or one of the device identifiers: instanceId, idfa, iosVendorId (transactions will be related to the user and/or the device), as well as parameters from the table below.

* — required parameter.

Custom revenue

Custom revenue involves other payment transactions that cannot be sent as ads revenue, in-app payments, or subscriptions. For example, it may be offline purchases or WeChat payments. In other words, it is any revenue for which there is not yet another mechanism for collecting data.

You can send custom revenue only via S2S API, using customRevenue and customRevenueBatch methods.

customRevenue

Use the customRevenue method to send data on a custom payment. It may be any payment that could not pass to MyTracker as ad revenue, an in-app payment, or a subscription. Like an offline purchase or a payment via WeChat Pay. For details, please refer to the Revenue tracking section.

End-point: https://tracker-s2s.my.com/v1/customRevenue/?idApp=XXX

Required parameters: a user identifier customUserId and/or one of the device identifiers instanceId, lvid, gaid, androidId, idfa, iosVendorId (transactions will be related to the user and/or the device), eventTimestamp, as well as parameters from the table below.

* — required parameter.

customRevenueBatch

Use the customRevenueBatch method to send batch data. This method is similar to customRevenue but allows you to send more than one payment.

End-point: https://tracker-s2s.my.com/v1/customRevenueBatch/?idApp=XXX

Required parameters:

Parameters

All parameters are passed in the request body in JSON format.

Limit on the maximum size of imported data — 10Kb.

Example query

HTTP POST request:

curl https://tracker-s2s.my.com/v1/customRevenue/?idApp=666 \
–k –X POST --header "Authorization: aaaaaAAAaaa01aaaaaaa1aaAAA11a" \
-d '{"customUserId": "1", "idTransaction": "order1234",
"currency": "USD", "total": 1.99, "eventTimestamp": "1580213208",
"instanceId": "00000000-0000-0000-0000-000000000000"}'

Status codes