I'm running a pay-per-install campaign on iOS an Android. The iOS installs seem to be tracking on the app dashboard, but no Android installs are being reported (there are installs though).
I'm trying to confirm reporting as described here.
You can confirm that the volume of installs is being correctly reported in the Insights section for your app in the App Dashboard under "Mobile App Installs". In addition, in the App Summary Page, after choosing your app, there is a time stamp 'Last Mobile Install Reported" for iOS and Android so that you can confirm that an install is being reported (see image below).
I'm calling AppEventsLogger.activateApp(getActivity(), getString(R.string.fb_app_id)); in my activities as instructed.
I also have the proguard lines to keep the SDK working.
Is there something else I'm missing? Is this a bug on Facebook's end?
It looks like misleading info in the documentation. Tracking was working. Real users are showing up on the dashboard, but my own devices were not.
Related
So, we have an app that has a website (production), an app (production) and a new app (beta).
The problem is that all applications but the recent one are production.
Briefly, the Facebook alert said (regarding the package name that is in beta):
The corresponding URL(s) should return a successful HTTP status code. You can verify this using the Sharing Debugger. - Compliant response codes: 200-299 - Violating response codes: 100-199, 300-399, 400-499, 500-599
We got switched from Live to In Development because of that.
Now, the question is:
What should we do next? What would it happened if we keep our status (dev mode) even with production products? There are not that many options here. We cannot set our app to public until closed beta testing is done.
I hope you all find it useful.
Considering you have the icon, privacy policy, all information requested by Fb and you receive notification above, consider:
If you have plenty other apps (web, android, ios, any) and them all are live. Your Fb app should be live too.
If your brand new app is not yet visible (e.g. beta testing), means basically that all your Fb id should returned to in development (according to Fb. Although, your prod apps will stop working).
So, what you can do is, create a specific app which is in development when the others are live. Or, like in our case, we removed Android on Fb from the website (will turn that on again when beta testing is done) and issue got solved at that moment.
I uploaded an app to internal testing track to the dev console and added a user.
When I go to the app page through the link, it shows (Internal Beta). But the app version I added isn't there. Even though I got a notification that it had been processed and should be live.
So the test user is succesful, and the app was added. But even though it says I am a beta user it doesn't show any app?
Right so I followed the test link to store, but it turns out you can't do that on your phone as it will just get you to the store app which only shows the live version. You need to follow the link on a desktop and send it to your phone from there...
I have created a test build of a GDK Glass app that I want to deliver to a few test users. However the app disappears after a reboot. Logcat shows this:
08-19 18:18:18.256: I/GlasswareSyncAdapter(978): Uninstalling Glassware ID #6DBADA7634397F00 (com.example.demo).
A look at the issue tracker explains that this is caused due to the fact that the MyGlass app didn't install this app and that the app thus isn't linked to the user's account.
Are there any workarounds? With a submission process of over a month how can we get our app tested properly?
The submission process should be less than a month at this point. I suggest that once you think you have things working, you submit the app.
Once submitted, you'll be working with the Review Process Team. They are able to create a whitelist (certainly of accounts, and possibly based on a list you can control through a Google Group) of who will be able to see the app on their MyGlass page. This will also allow you to test the app, including the auth flow, using the actual installation process.
It seems like this issue only occurs when the application you are side loading has been submitted to Google for approval. Just change change the package name of the APK you want to sideload and your problem should be solved.
We have integreated Facebook Mobile App Ads for Installs SDK into our iOS and Android app.
Code for iOS:
Facebook SDK 3.5 (inside function applicationDidBecomeActive)
[FBSettings publishInstall:#"APP_ID"];
Code for Android:
Facebook SDK 3.5 (inside onResume())
com.facebook.AppEventsLogger.activateApp( MyActivity.this, getString( R.string.fb_app_id ) );
Clicks are being reported correctly, but not installs. For the iOS it is OK, but Android shows nothing in Actions column inside Campaign monitor https://www.facebook.com/ads/manage/.
We have checked settings of Facebook app and both Android and iOS have last install date correct on the dashboard in section "Last mobile install reported" (usually 10-20 minutes earlier). It seems like Android just does not show data in the Actions column. I can not estimate cost per action for this app which is very important when planning budget for ads.
There was an error on Facebook side. Now everything works as expected.
as subject,
I want to track Android App install, but I want to track any install and not just from mobile Ads. My question, is it possible?
One particular question is: If I run the development version of my app that in theory, is integrated with Facebook SDK, straight from IDE into an emulator, will I see it reflected in "Last Mobile Install" stats in my dashboard? Because apparently, it didn't. If it's not, is there any way to do this in a debug environment in order to confirm whether I'm using Facebook SDK correctly or not?
For reference, I'm calling this line in my onResume() method:
com.facebook.AppEventsLogger.activateApp(this, getString(R.string.facebook_application_id);
Thanks.
Update: So it's probably not a proper question. I concluded that Facebook recorded mobile installs from Android app based on its attributionId. If this value is null, such as if there's no Facebook app or it's not logged in, the mobile installs is simply not recorded. I think.