Discussions

Ask a Question
Back to All

FAQ October 2022

(edited)

This is our monthly post with Frequently Asked Questions from our customers. Hope this article will be useful for you all!

  • Do you have the opportunity to see in real time the number of installs per day? Or at least the day before?
    Installs can be viewed in the Conversion chart Instal-> Trial or Instal -> Paid, there is a table showing the number of installs by day at the bottom of the page.

  • Hi! I am getting error with const { paywalls, products } = await adapty.paywalls.getPaywalls()
    AdaptyError {"adaptyCode": "noProductsFound", "code": 1001, "localizedDescription": "No In-App Purchases were found.",}
    Hi there! We have a useful guide on how to handle "adaptyCode": "noProductsFound" in our documentation: https://docs.adapty.io/docs/ios-sdk-error-handling

  • Is it i possible to send events from Adapty to Slack?
    Unfortunately, it is not possible at the moment. There’s an issue with the Slack’s workaround which does not allow sending events to it.

  • Does Adapty let you see how ad traffic is performing in terms of ROI?
    We only track user’s subscriptions events, so you can see new subscriptions or revenue, filtered by attribution parameters. Yet we are not tracking your money spending, so we do not have metrics like ROI.

  • We have just went through all adjust integration steps from your documentation, but events failed to reach adjust without a reason. Could you please advice?
    As far as I can see, your profiles do not have adjust device ID, that is why we are receiving that error. You can find an information on how to get adjust device ID in the article for Adjust Documentation:
    https://help.adjust.com/en/article/gather-device-ids-android-sdk

  • My google play console shows me this warning:
    You are using the InAppProduct API to manage subscriptions, which is no longer updated. Start using the ew Subscriptions API to get new features including multiple base plans and offers, as well as prepaid plans.
    Could you please advice?
    This issue here might appear, because we are not supporting billing library v5 for android at the moment. So, if you want to fix this problem, you should use previous versions of the billing library.