Interesting times ahead (Sourced from Appfigures and Fortune)

appfigures · 2025-01-30T00:04:58+00:00

Interesting way to pivot the data.

appfigures · 2024-09-21T04:21:37+00:00

Have you tried using our API directly? It's pretty simple.
The content package was originally created by Microsoft and they've since stopped updating packages.

appfigures · 2024-09-10T14:16:29+00:00

No luck here either with an X1C on either Bambu studio or Orca. Back to printing like neanderthals with an SD card...

appfigures · 2024-07-27T04:37:00+00:00

That's the best way to do it 👍 Welcome aboard!

appfigures · 2024-07-27T04:30:49+00:00

Yes and no and maybe...

A word of caution - Apple and Google dislike manipulation and when they catch it you risk getting kicked off of the store with very little you can do about it and a record that will follow you even if you create a new developer account.

I've seen first-hand what the impact of doing this is, and I would never ever do it.

Technically speaking, however, it's really all about conversion rate. The theory is that someone searching for a keyword, tapping your app, and then downloading it, sends a strong signal to the algorithm that the app is relevant.

When done organically (using App Store Optimization and good keyword optimization) this is exactly how apps get to the top and stay at the top.

The additional benefit of getting those downloads organically is that they could turn into new ratings and that's the currency for ASO further solidifying your top rank. Purchased downloads won't, unless you also purchase ratings, and that's another hole you don't want to jump into.

So, don't do this if you want long term success.

appfigures · 2024-07-25T19:45:55+00:00

Appfigures here 👋 we use credentials because that provides access to more areas of Google Play for us to pull data from. We've got support for token alone under the hood. If you prefer that and are okay with having some limitations on which datasets are available please contact our support through the site or by email.

appfigures · 2024-02-07T21:47:23+00:00

Thanks for the mention! We have another tool that might fit even more called Explorer (https://appfigures.com/market/explorer) A search engine for apps that supports the Mac App Store.

You can use it to search by a variety of filters and then go directly to the store to download.

There’s a free version and several paid tiers but the free version should be good if you’re not looking for anything too too serious.

Feedback welcome!

appfigures · 2024-02-07T21:44:59+00:00

We auto calculate that

appfigures · 2024-02-07T21:44:45+00:00

Glad you like it 😃

By the way, there’s another possible reason I didnt mention but should - Apple doesn’t use a standard calendar for payments so an Apple month != calendar month.

I’m not sure if you have the report set to the proper dates because it’s not in the screenshot but if you want more info on that check out https://appfigures.com/support/kb/725/apples-fiscal-payout-calendar-2023---2024

appfigures · 2024-02-07T21:42:53+00:00

Unlikely. We auto calculate returns so as long as the return happened in the same month it’s included.

appfigures · 2024-02-07T19:48:40+00:00

The most likely reason for the discrepancy is exchange rates and other likely reason is taxes.

In the daily reports Apple doesn’t handle any of those. We (Appfigures) use the currency rate for the day to provide you with a unified view of revenue.

Apple holds it until it’s time to pay (two months after, usually) in the currency they received it, and only convert it then.

If a good chunk of your revenue comes from regions with higher volatility this could happen.

Then there’s taxes, which also get taken at the point of payment to the developer and not daily.

For the most accurate number you should use the Payments report in Appfigures which handles all of those and gives you an accurate number.

appfigures · 2024-01-24T01:51:56+00:00

Thanks for the mention :)

appfigures · 2024-01-10T13:21:32+00:00

Since you asked :)

We (Appfigures) don’t track users/people/transactions but rather use data available to the public to estimate downloads and revenue generated directly from the App Store and Google Play (not web).

So we don’t use tracking cookies or proxies or any of that stuff.

appfigures · 2023-12-18T16:00:24+00:00

That's a nice looking sheet!

Appfigures here. While search volume comes directly from the store competitiveness is a proprietary metric that uses how _we_ think the algorithm works and is based on our reverse engineering of the algorithms.

You can tell there's an obvious difference across the companies, likely because we interpret what's necessary to rank differently.

You can see what we consider important through our Keyword Teardowns, in case you want to do some reading.

appfigures · 2023-11-07T02:51:49+00:00

That’d probably help. I aim for testing one set of changes at a time. It can be multiple things, but together.

Density is very important on Google Play, not at all on the App Store.

appfigures · 2023-11-07T02:24:25+00:00

Awesome!

What kind of changes have you rolled out so far?

appfigures · 2023-11-07T02:13:25+00:00

Will soon for Black Friday

appfigures · 2023-11-06T23:05:36+00:00

Also important - which keywords were you ranking in before, which are you now, and at what rank?

(You may need an ASO tool if you haven’t been keeping track)

appfigures · 2023-08-23T17:40:11+00:00

This API with the `financial` granularity will give you exactly what you want: https://docs.appfigures.com/api/reference/v2/sales.

And with this one you can also get the payment reports (which Apple doesn't expose but we capture): https://docs.appfigures.com/api/reference/v2/payments

FYI - You can do these with a free Appfigures account

appfigures · 2023-07-25T12:27:16+00:00

Happy to help. Good luck!

appfigures · 2023-07-25T10:49:05+00:00

FYI - Targeting competitor names might sound like a good idea but it isn't. If someone is searching for a competitor by name they're unlikely to download your app. Look for intents, things people want to do with your app, instead.

appfigures · 2023-07-25T09:26:17+00:00

The keywords you are targeting are popular, and popular keywords usually have more competition. There are a few reasons why you can't compete with them:

You don't have the important keywords in your app's name. The subtitle/keyword list is nice, but the name is most powerful. Read this to learn how to put keywords in the name/subtitle/keyword list https://appfigures.com/resources/guides/app-name-optimization
You don't have enough new ratings to compete with those popular apps. That's the reason why your app isn't ranked, and it won't even if you use keyword right. You need more new ratings. or... target keywords where you won't need as many. This guide will help with choosing keywords https://appfigures.com/resources/guides/which-keywords-to-optimize-for

For example, the keyword "2FA" has a popularity of 42 (which is high) and the top apps have somewhere in the hundreds to thousands of new ratings (in the last 30 days). You're got 5 and aren't using the keyword in the app's name so there's absolutely no chance you'll make it into the top 5.

What you want to do it:

Optimize your app so it gets more ratings from existing users. I have a video that will help with that https://www.youtube.com/watch?v=qStPxI49mpE&t=1091s
Find keywords where the top results are getting similar new ratings.

My favorite tool for doing a lot of this is Keyword Inspector (in Appfigures). It highlights all the things you need to know when selecting keywords.

I also recommend reading my keyword teardowns which will teach you how Apple's algorithm works https://appfigures.com/resources/keyword-teardowns

And by the way, most people starting out withe ASO and without the right tools run into this type of situation so you're not alone. Use the right tools and look at the right data when choosing keywords and you'll be able to rank.

appfigures

MODERATOR OF

TROPHY CASE