LinkShare iTunes Affiliate links in an iOS app - iphone

I have an app that aggregates apps from the app store for a specific audience, and I use the iTunes Affiliate program (via LinkShare).
When a user taps the download button, it opens safari with the affiliate link and redirects to the AppStore. That's how I see it happening in other apps as well ("Free App Tracker", for example).
However, while LinkShare counts the clicks, I don't see any "orders", and I know there should be a few.
The clicks count gets updated the same day, while the orders count didn't get updated at all (still 0) for 3 days now.
Do I need to call the url in any specific way? or do LinkShare take their time with orders reports?
Thanks!

LinkShare track the orders in different way: there is the transaction date which is the date when the purchase was done, and then there is the "process" date which is when the transaction has been processed by the LinkShare system.
You can read more about it.

A few notes:
Are the purchases you that know happend via your link happen in the US store?
- The LinkShare program only support the US and CA programs so if the sale was made in another country you won't see any sales data.
iTunes advises that you wait three to five days for your sale to show up. I've seen sales the next day and sometimes they take longer. Typically, however, they are no later then a few days after you get the receipt for the sale.
You can call your link in a way that the redirects are processed in the background. Check out this resource for details - http://developer.apple.com/library/ios/#qa/qa1629/_index.html
Hope that helps.

Related

What stands for CMB in iTunes Connect Sales And Trends?

I want to know that stands for CMB in the iTunes Connect Sales And Trends report, I have looked at the guide and there's nothing specified.
The "iTunes Connect Sales and Trends Guide" (available after clicking on the '?' mark in iTunes Connect) has some information you may have overlooked.
The glossary states that "CMB" is:
Complete My Bundle (CMB)
The action taken by a customer to purchase
the remaining apps in a bundle beyond those already purchased.
From the Sales Report section:
If the transaction involves a “completed” app bundle, this field will
contain a value of “CMB.” App credits for completed bundles will show
a value of “CMB-C.” Otherwise this field is blank.
I saw CMB in itunes report today, when I tried to search for answer, I stumbled upon this question.
Though Linus G. is helpful, I would like to add few more info which I read now in other site.
Bundle Completions (CMB)
A bundle completion occurs when a user that has already purchased an app that's also available in an App Bundle downloads the entire bundle. Because the App Bundle is sold at a discounted rate, several things are recorded for each bundle completion.
Source: https://appfigures.com/support/kb/529/how-are-app-bundles-tracked
Based on above information and few such scenario in my reports today, this is my observation, but I may be wrong.
Example:
1) Single app – “A” costs 1 USD.
2) App Bundle which has apps A + B + C and costs 2 USD.
When a user purchase app A for 1USD and later he purchase app bundle “A+B+C” for 2 USD, then system automatically returns back 1USD(cost of app A) to user.
In itunes report you would see CMB for Bundled App “A+B+C”
and
CMB-C for Single App “A” ( I presume C stands for credit, but not sure).
Hope this would be useful for anyone looking to know what is CMB in itunes reports.
From iTunesConnect's user guide:
If the transaction involves a "completed" app bundle then this field will contain a value of "CMB". App credits for completed bundles will show a value of "CMB-C". Otherwise this field is blank.
Hope that helps :)

Application crash after approved

I got my application approved on app store.
But due to some change in the feed I am using my app is crashing now. What am I supposed to do now?
Giving an update will take 7 days for apple to approve and I will get bad reviews if any one downloads it in between.
What am I supposed to do now?
You could:
Fix the feed.
Remove the app from sale until you fixed the bug and the update is approved.
Remove the app from sale until you fixed the bug and the update is approved and request a speedy review.
To remove a App from sale, go to the Rights and Pricing of that app in iTunnesConnect and set the Availability Date in the future. this will remove the app from sale. Just put the date back to now to make it available again.
You can ask for an expedited review (http://developer.apple.com/appstore/contact/appreviewteam/), if you haven't abused of it yet and have real reasons (as it seems) to ask for it, they will review your App in between 1 and 3 days... :)
If you want to stop selling your App while it is happening, you can go to the Pricing menu in iTunes Connect and remove all the countries available...
You need to submit an expedited review request. From my personal experience I've generally pushed these out within 24 hours. Usually Apple does these as a one time exception, and is supposed to be used once in a great while. I've done 4 total in 2 years. Anyhow, since there is contact information on the website, if users download and contact you reply back that there are pending updates, and will be out shortly.
You could go through pausing delivery of app until ready, etc, etc. Availability can be changed and automated via dates. You can remove from countries available.
Here is link for expedited review. You'll need your App ID and Name, etc.
http://developer.apple.com/appstore/contact/appreviewteam/

Tracking the Reseller of the iPhone -App from inside the App

I have been stuck in a strange situation, according to my requirement, I need to track the resellers of my app, i.e. I will be publishing link of my app in the iTunes-Store on 3 or more different sites(The re seller's sites).
According to my promise which I made to these resellers, I will provide a share of my profit.
So here I have to track from which link did the user came to the APP-Store.
Any suggestions or solutions will be Thankful.
I think the only way to do it will be server-side. Links at your resellers should point to your server, where you log the source of link (resellers web page) and redirect request to AppStore. But you'll have no way of knowing, which of this requests ended up with a purchase.
The only way to do this for real is to get them to become iTunes affiliates and provide reports back to you. They should use the iTunes referral to make the sale (they will get a small cut from Apple) -- Apple will report that back to them, and then they can prove to you that they made a sale, and then you pay based on that.
Reserve the right to audit them -- meaning that they will have to show you the report directly from the iTunes affiliate site.
I assume that iTunes actually tells them what they sold, but you would need to check that.
Another idea (which may or may not make sense based on what your app does) is to make personalized versions of your app for each reseller. If there's some way to incorporate a very simple feature that is personalized (and makes sense), then you can upload the same app multiple times and assume all sales are coming from that reseller.
So, for example, if the app were an exercise tracker, and the resellers were gyms -- you could customize the app for each gym and add their schedule and contact info to it. Then, sell the app as an Excerise Tracker for XYZ Gym and let them promote it and get a cut of sales.

In-app Purchase Loop Hole

OK so have a problem with the whole in-app purchase review process and hope someone can shed some light/experience on it.
We have a project which is a magazine for the ipad. Each issue requires an in-app purchase before it is downloaded. The issues are served from an XML feed when a new one is published.
The problem is, how can we have Apple review an in-app purchase without displaying the new issue. They wont be able to see it in the live binary. If we publish the issue we have to say "unavailable", which looks extremely unprofessional to the customer, until the in-app purchase is reviewed.
We dont want to have to publish a new binary each time a new issue is published as thats a pointless exercise for the customer
Thanks, any suggestions apart from change message to "coming soon" would be apprciated. The only other thought we had is a flag in the app settings which displays "unavailable issues"
If you login to your iOS developer account, you'll find this Getting Started with in App Purchase pdf file, which has information that you'll need in your setting up with your iAP item.
Specifically, I think what you need is an item belongs to the category named Subscriptions. This should solve your problem.
You can use consumable purchases, i.e. right to download 1 article. 5 purchases - 5 articles.
Or, give a user subscription for month or so.
You could always just keep some kind of "sample" issue available for the purposes of the user demoing the software.
That, or a few select pages from the active issue could be specified as "demo pages", as in they would be viewable from a demo version of the software.

How can I find out how much a user has paid for my app inside my app?

After a user purchases an app from the app store, and runs it, is it possible for the app to know how much the user paid for it? Does Apple have any APIs that can access this type of metadata about the actual purchase of an app?
If not, I suppose I could fall back to looking up the country of the user, doing currency conversion rates, and then lookup the price of the app at the time of purchase. That's another thing, is it even possible to know when a user has purchased an app? They could purchase an app, and then not run it for days or weeks, so I cannot assume the date they first launch the app was also the date of purchase.
Any thoughts on how to obtain this information?
This isn't possible through any kind of API. What you can do is have the device send data back to your server on first launch with location and date. This way, you can mark them in your DB as xx paid yy on this date. You know what yy is currently because you run the server and the app page. Make this info accessible somehow on your server, and when you need it in the app, call your servers method to retrieve it.