I recently started using Facebook analytics for the iOS apps I create. However, the FB analytics collects a lot of data during the testing periods of my app that I do not want to be included in analytics. Is there any option to clear out all of the stats FB analytics has collected so I can clear out test data before the app goes live in the App Store?
There is no option to do this. You could just ignore the data prior to date X (before your public release) and you should be OK.
Related
I have an a flutter app integrated with Kochava, where Kochava is selected to receive SKAdNetwork data. The app is also setup in facebook so that install campaigns can be run. However, when I select it in campaign manager, I get "The Mobile Measurement Partner app used to configure events for this app doesn't currently support SKAdNetwork events. To run iOS 14+ campaigns for this app, choose a different app event connection for SKAdNetwork in Events Manager.".
In the Events Manager, Kochava is configured as the source of SKAdNetwork events (and the configuration screen is "all green"). Also, on the dashboard I can see "fb_auto_published" app install event from MMP and the app screen shows a date of "last mobile app install" (those are all likely originating from iOS14+ live testing).
I want to avoid integration with Facebook SDK and having Facebook as the recipient of SKAdNetwork data (mainly because it feels like a less clean setup with MMP getting some events and Facebook some - while other networks like Twitter are also integrated).
I have tried replicating this setup under clean ad manager and setting up new app in Facebook (no change - still doesn't work). The Kochava-side configuration has been reviewed by Kochava team and looks good to them. Facebook's business support directs me to developer support but only after "recommended" step of Facebook SDK is completed (which I am a bit reluctant to do).
I'm looking to launch a single web app that works as a PWA for web users and a TWA for users wanting to download it from the Google Play Store. The app includes a yearly subscription so I'll need to implement separate payments methods for the PWA and TWA in order to comply with Google Play policies.
With this being said, is there a way to identify with JS if the user is viewing the PWA vs the TWA app from the play store? Perhaps something unique to check in the global window object?
Or, is it recommended to publish a whole new version of the app used for the TWA to a different URL that only supports the Google Play payment option.
Any info would be great. Thanks in advance.
We have a multiplatform service and we give our users a 30 day trial. A user can sign up on iOS, use the web version and finally do the payment on Android... even if it's weird, its a possible. The database is shared between all platforms
We are using Facebook Ads to generate App installs but we don't know how to do the conversions' attribution properly. The main problem is that if, for example, a user install the app from a Facebook app but he end up paying from the web version we lost track that the origin of this user was the ad.
I would like to know if it's possible to determine using the Facebook SDK, on the first run of the app, if the user comes from a Facebook Ad and in that case I would store that information in our database to do the attribution once the purshase is done. Any ideas?
Many thanks in advance!
Regards!
I would like to integrate Facebook into an iOS application I am building, however it seems there is no way to set up a Facebook 'Native iOS Application' with an iOS application that is not already published and available in the App Store.
When I Set up a Native iOS Application for my Facebook App from my Facebook developer's account it requires that I fill in my App Store ID. However when I submit I get the following error message:
Your iPhone App Store ID is invalid because the iTunes App Store
reports your app as being unavailable for iPhone and iPod touch.
I have set up my application on iTunes Connect, but I have not submitted my binary yet as I am in the process of building it, so I assume that this message is due to it being unavailable on the App Store.
This seems like a catch 22 situation. I can't test my app until its in the App Store but I can't get my app in the AppStore until I have tested (and built) it. How can I test my iOS application with Facebook before release?
I've been there, but the solutions is simple.
Don't fill out the Facebook 'Native iOS Application'!
For testing all you needed is the Facebook appid.
Later on in the Deep Linking portion of the iOS Facebook Tutorial, it also mentions the AppStore ID and that you can use somebody else's ID temporarily to get all the data to save. They just say to make sure you use your own id when you finally do publish the app.
I dont think facebook Native iOS App settings are necessary. I have done facebook login with it in two of my apps and without it in one of my app and all are running well. Here are workaround by me:
Native iOS Facebook SSO won't return to app
If a Tweet is created using the native Twitter API, the Tweet has a "via [my-app]" indication, where [my-app] is a link to the App's home page.
If the same Tweet is created using the new IOS5 Twitter API, the app says "via IOS" and the link points to www.apple.com.
Is there a way to retain my App association when using the IOS5 API without adding a link to the Tweet itself?
If not, can I continue to use the native Twitter API under IOS5 or is this a cause for rejection?
According to the FAQ on the Twitter iOS developer site, this only happens because your app is not yet live in the app store:
If your application is not yet live in the App Store:
The application making the requests must be launched in Apple's App Store in order for the
attribution to display on twitter.com. Note that the iOS5 version of the application must be
live, not just a previous version.
They also have some tips on how to fix this if it still happens after you're live in the app store here: https://dev.twitter.com/docs/ios-frequently-asked-questions
Since the via [my-app] is set in Twitter application configuration I dont think that you can set it via the iOS Twitter API.
Apple will not reject your app for using the Twitter API directly (for example using Sharekit or MGTwitterEngine). At least they did not reject my app which still uses the ShareKit.