I recently added Firebase In-App messaging.
The installation seems to be working fine but I have an issue with testing the messages.
I create a "Campaign" with a test message, and on the state option I get "on_foreground" and "app_launch".
I assume that "on_foreground" means that users will see the message when entering on re-entering the app.
But when I try the test campaign, I don't see any messages on my device. However if I delete the app and reinstall, Then I am able to close/open the app and receive the test message then.
Anyone else having any similar issues ?
Firebase In-App Messaging only retrieves messages from the server once per day. Also, there's a Per-device frequency limit. By default, a campaign is not shown again after it has been impressed or viewed by the user within a day.
If you wish to test campaign on demand without hitting the limit, follow the instructions here.
Related
When trying to create an ad set in FB Ads Manager optimized for app events such as purchases, it does not work. It shows me the error: "App Event Optimization requires both application id and custom event type for promoted object. "
I am already able to track App Installs fine, and I have standard events set up and enabled in my iOS app. What could be going wrong here? My FB analytics don't show purchases even though there have already been a number of them.
I even tried the codeless setup option, and that does not seem to respond.
For anyone facing this issue, just keep tinkering with the Facebook Developer settings until you start seeing the purchase data appearing in FB Ad Manager. I just noticed today that the purchases started tracking, and I did not push a new version of the app recently.
When we started using Fabric we created an ecommerce_purchase event to track and report on all in app purchases.
We then implemented Firebase. We continued to use the ecommerce_purchase event because firebase was not reporting iOS in app purchases yet.
Now Firebase does report "some" of the in app purchases, but not yet all of them (subscription renewals are a large part of our revenue, and not yet handled by Firebase).
The ecommerce_purchase event is still reporting correctly, but our issue is the console now double reports quite a bit due to the revenue numbers automatically combining the ecommerce_purchase event, as well as the firebase automatically tracked in_app_purchase event.
Long story short... is there a way to exclude one of these events from the revenue numbers reported by Firebase in the console?
Thanks!
There's no way to exclude the events in the reporting. What you can do is to export your analytics data to BigQuery and perform custom analysis there. Follow the instructions here to link Firebase to BigQuery.
I need to get monthly uninstall count for iOS using Firebase. I know that for Android, there's app_remove event that I can use even if it's not really accurate, but it's enough for now.
From iTunesConnect or Playstore, they only give user retention data like how many user still use your app after x days, or daily uninstalls, which is not what i'm looking for.
Right now, you can't track app uninstalls on iOS using Firebase Analytics. It's not a trivial change (I think most SDKs do this by keeping track of messages they get back from the APNs feedback service), but I'll put in a feature request on your behalf.
Apple has added the deletion metrics recently by which we can see the number of uninstalls. We can add filters to find uninstalls for geographic range, app versions, by device and so on.
For reference: in iTunes connect app analytics in metrics under usage we can see the deletions.
Link : https://developer.apple.com/app-store-connect/whats-new/?id=iosdeletions
I have created a test app with In-App billing. Uploaded it to google play and sent it to beta testers. When they try to make purchase then they receive Error retrieving information from server. [DF-PPA-10] error.
We tried several accounts that are able to make purchases in Google Play. I did a test purchase with one of these accounts from another app and it works. But we always receive DF-PPA-10 error trying to purchase In-App in our beta tested app from different accounts/phones.
If we use account with expired card or without card then Google Play asks to enter card or PayPal. Once good card is added then we get DF-PPA-10 error.
I faced a similar issue recently. I could make successful purchases with the same card and account but suddenly it started giving me this error.
I am not sure why this should have happened but uninstalling updates for Google Play Store from Settings > Application Manager resolved that error.
See
Google Play Store Error DF-BPA-10 for more details.
We had an app live on the Apple app store for several months and that app did not include Flurry analytics.
We have recently updated the app with a new version and also included Flurry analytics into the App.
The Flurry dashboard is reporting the "New users" correctly when compared to new users iTunes sales and trends report however, iTunes is also reporting several hundered "updates" of the app that have been downloaded - however these are not included in the "New user" count on Flurry.
This means that Flurry is only reporting actual new app downloads and not considering app updates as new users at all?
We are using the Appcelerator module of Flurry.
Please could you help me in understanding if we need to do anything special/extra while integrating flurry SDK into the app to ensure users who take updates of the app are also included in the new users count in Flurry.
A interesting fact.
Try create event with param with universal name (for see count of events in circle in Event Parameters), and send at once from each device.
Then you can take a count of all active users. But if user is reinstall the app, then him can send at secondly, what is bad.
Flurry can’t report updating users as “updating users” because it only just found out about them. As far as Flurry is concerned, all of your users are new, because it hasn’t seen any of them before. When you release a second version with Flurry you will get the correct metrics. (Except, of course, for the hopefully-small minority who are updating directly from your 1.0 release.)
Edit: I think I’ve completely misunderstood your question. I think your mismatch may be caused by the fact that Flurry can only report on users who have launched [the new version of] your app at least once, while iTunes Connect will report all of the new and updating users.