Duplicated events from Fabric stream into Firebase-> Google Big Query streaming - firebase

We've noticed, that in raw Google Big Query (gbq) data from firebase appeared duplicates. After a short investigation it seemed obvious, that problem is caused by Fabric - same events differed by a value of a firebase_event_origin field (app|fab). I've found no answer how to stop events from fabric stream in GBQ Firebase import.
Have anyone solved this problem already?
Image:

Well, that happen to be easy - our coder set up an integration between Fabric and Firebase. So, to stop receiving Firebase events you just should go to Firebase console settings, open 'Integrations' pane and proceed to 'Fabric'. There you just need to turn off option 'Send Fabric events to Google Analytics for Firebase'.
screenshot

Related

Events not logged in firebase console

I just don't know what to do anymore. I have a React-Native app and I'm trying to use Firebase Analytics to log Events in the app. I'v followed the entire installation of https://rnfirebase.io/ and https://rnfirebase.io/analytics/usage. Having done that I'v tried to log an Event but I can't see it in Firebase.
What left me completely baffled is that activating the app for Debug View mode with -FIRDebugEnabled in XCode worked. I could send an Event on the app and see it on the Debug View console in Firebase. When I deactivated the Debug mode WITHOUT ANY CHANGE only -FIRDebugDisabled in XCode the app did not send any Events to the Events console. I don't get any error there is no way to know what is happening. I have no idea of what I need to do or how to fix it.
Maybe some configuration inside the GoogleServices-Info.plist? Something inside the Scheme in XCode?
What should I do?
EDIT: I´v read a lot of answers here. Just to clarify the Events names are not a problem (no spaces or more than 40 chars) and I´v filtered Today and all posibles filters.
Unlike the DebugView, Firebase doesn’t display data in real time. There’s an intended delay before the analytics data is logged on your Analytics dashboard. The initial data logged usually takes up to 24 hours to display and 3-4 hours delay for the succeeding data. For additional information about it, you can refer to this blog post.

How can you prevent fake events in firebase analytics

I've recently set up Firebase Analytics with my website. I was beginning to add some events to be logged and realized any arbitrary event could artificially be called. I could just go into my browser's console and run the command firebase.analytics().logEvent('some_fake_event').
If you know a website is using firebase analytics, what's to stop you from simply spamming fake events into your console? The website owner's analytics would become fairly screwed up. Also, firebase mentions that there's a 500 event-type limit. One could also run firebase.analytics().logEvent('fake_event_1'), firebase.analytics().logEvent('fake_event_2'), etc. Oops, the website owner can't create any more new (legitimate) event types.
What is in place to prevent this?
The logEvent method will be available once you rely on standard firebase SDK. The only way to prevent this would be to obfuscate the library you're using.

How to store firebase analytics data offline for more than 72 hours?

I am using Firebase for analytics and I have enabled firebase persistent storage which helps to send the analytics events to firebase when the device comes online but the limitation is it only sends 72 hours data to Firebase analytics.
I want firebase to get at least offline analytics data of the last 10 days.
Can I achieve this by storing this analytics event in core data when the device is offline and send this event to firebase when the device is connected to the internet?
Or is there any alternative way to achieve this?
I only want to send the event name and timestamp of the event.
You can probably do something to store the events locally, but it'll be finicky and error prone.
When storing the events yourself and then submitting them when the device is online, I see many potential problems. Off the top of my head:
There is no API to track the lifecycle of Firebase's built-in purging of analytics event. So you have a decent chance of events being logged twice.
You can't backdate the events, so any events you fire upon reconnecting are going to show up as having happened then.
You're likely going to miss events that Firebase logs automatically. You could probably compensate, but at that point you're almost building your own Analytics solution.
Honestly that is some of the potential problems, and you're likely to encounter many more. I'd seriously consider if the effort is really worth it, or if you'd be better off picking another solution.
Some solutions that come to mind:
Log your own events directly to BigQuery. Then merge then with Firebase's exported Analytics events, and deduplicate the results.
Pick an analytics provider whose API meets your requirements directly.

New Google Analytics property not capturing traffic

Hell,
We have a production prperty for google analytics and out IOS and Android Apps are recording the events and data.
I am trying to create a test property in order to use it in the test environment, how ever that does not seem to work. here is what I have done:
1. Created a new prperty under the production account
2. Created Streams for Ios, Android and Web
3. Cannot find the Tracking Id for the new property. Sme places I have read it is in the format
UA-AccountId-PrpertySlnumnber. I have tried that but not result.
4. Some places suggested to use the measurementid (G-xxxxxxxx) available in the web Stream and I used that but still it wont work.
However if I use PROD tracking Id in the code, it perfectly works. Am I missing anything? Any guidance will really help.
(Added as answer because low reputation doesn't allow comment)
Can you clarify if this is what is occurring?
Production property with production tracking ID shows data
Test property with test measurementID does not show data
Test property with test tracking ID (tracking ID not found)
Or did you mean Test property with Production tracking ID shows data?
Based on this, it sounds like your properties are not replicates. Are they both the same type of property? I would suggest going through the instructions on Google with both properties side-by-side.
See further info below:
https://www.blog.google/products/marketingplatform/analytics/new-way-unify-app-and-website-measurement-google-analytics/
https://support.google.com/analytics/answer/7372977
https://support.google.com/analytics/answer/9304153
https://support.google.com/analytics/answer/9303323
A couple things to consider.
Have you setup the firebase console correctly?
Are the data being sent out correctly? You can check this in your network calls.
Is there a lot of data being tracked already in your current environment (Staging or dev)? Google analytics perform sampling on the data when there's too much data coming in. I think it's 1 million data points per day. It does 1% sampling on our production app.
I think my mistake was I was trying to create a new google analytics for firebase property but was not connecting it to the firebase.
The reason behind is I was trying to accomodate it with the older Google Analytics SDK implementation and I was not finding any documentation which said no it is mot possible.
Now, I created properties connected them through google firebase projects and enabled analytics with them. In my xamarin app I used Xamarin.Firebase packaged to get it working.

Subscribe to iCloud calendar on Google

I am trying to subscribe to an iCloud calendar on my Google calendar. I am really open to any methods, but here is the one that seems most likely to work. See instructions to build proxy calendar. The problems is that when I try to subscribe to this proxy calendar (using both webdav://... and _http://...), I get the error message "Settings Error--Could not fetch the url." I know the file should work because I was able to use it in Outlook. Any idea on how to fix this, or a completely different alternative that I have not found?
So, the problem fixed itself the next day. I assume this is because Google cached the error and was not going to bother fetching the calendar again. So I guess this was a non-issue.

Resources