Missing events_ table in BQ/Firebase link

[asya_z]

Hello, dear community!

I linked Firebase to BQ 9 days ago 

I use BigQuery streaming export.

So far I have only 3 tables in the table list: events_intraday, pseudonymos_users, users.

But what about events table? Where is it?

I found this regarding an events_intraday table - "This table is deleted at the end of each day once events_YYYYMMDD is complete." And this "You should query events_YYYYMMDD rather than events_intraday_YYYYMMDD so you're querying a stable dataset for the day."

But I still don't have this events_YYYYMMDD. 

How could I fix it? Maybe I did something wrong while setting the connection? I would appreciate any help! 

[ms4446]

There are a few possible reasons why you might not be seeing the events_YYYYMMDD table in your BigQuery dataset:

1. Your Firebase project is not generating any events: If your app hasn't logged any events after linking Firebase to BigQuery, then the specific events_YYYYMMDD table won't be created.
2. Delay in data processing: Even with events being logged, it can take up to 24 hours for data to be processed and appear in BigQuery.
3. BigQuery streaming export is not enabled: If you haven't enabled BigQuery streaming export, events will be exported to BigQuery once a day. This means you'll see a delay in events appearing, but the events_YYYYMMDD table should still be created the day after events are logged.

To troubleshoot this issue:

1. Verify Event Generation: Check the Firebase Analytics DebugView to ensure your Firebase project is generating events.
2. Wait for Data Processing: Allow up to 24 hours for data to be processed.
3. Enable BigQuery Streaming Export: If you want near real-time data in BigQuery, enable streaming export by following the instructions in the Firebase documentation.

If you've tried the above steps and still don't see the events_YYYYMMDD table, consider contacting Firebase support for further assistance.

In the meantime, you can query the events_intraday table for data from the current day. However, remember that this table is deleted at the end of each day.

[asya_z]

Thank you a lot!

All 3 steps are resolved. They don't seem to be a reason.

I wonder, maybe it's necessary to choose both Daily and Streaming options in the Export Settings? (I've chosen only Streaming)

[ms4446]

No, it is not necessary to choose both "Daily" and "Streaming" options in the Export Settings. If you select both options, your events will be sent to BigQuery in real-time (Streaming) and will also be part of the daily batched export (Daily). However, this doesn't mean your events will be duplicated; it just affects the method and timing of the export.

The "Daily" export is a scheduled export that runs once per day, while the "Streaming" export sends data to BigQuery in real-time.

If you're only interested in real-time data, you can select just the "Streaming" option. If you want a daily batched export of your data, choose the "Daily" option.

In your case, seeing only the events_intraday table suggests you've enabled the "Streaming" option. The data in this table should be moved to the events_YYYYMMDD table at the end of the day. If you're not seeing this behavior, enabling the "Daily" export might be a workaround, but it's not the root solution.

To enable the "Daily" export, go to the Firebase console, click on the Analytics tab, then click on the Settings gear icon and select "Export settings". Under the "Daily export" heading, check the box next to "Enable daily export".

After enabling the "Daily" export, it might take up to 24 hours for the events_YYYYMMDD table to appear in your BigQuery dataset.

[asya_z]

Thank you.

It still hasn't appeared. 

So far I'm using * instead of the specific date in the name of the table in a FROM statement to query all days data. 

[ms4446]

If the events_YYYYMMDD table still hasn't appeared even after enabling both the "Daily" and "Streaming" options and waiting for more than 24 hours, there might be an underlying issue with the Firebase to BigQuery integration for your project.

Using the wildcard * in the table name (e.g., events_*) in the FROM statement is a valid approach to query data across all days. This is especially useful when you want to aggregate data over multiple days. However, this approach assumes that the events_YYYYMMDD tables exist in the first place.

Here are some additional steps you can take to troubleshoot:

1. Check Firebase Analytics Data: Ensure that your app is indeed sending events to Firebase Analytics. You can verify this by checking the Firebase Analytics dashboard to see if events are being logged.

2. Verify BigQuery Permissions: Ensure that the Firebase project has the necessary permissions to export data to the linked BigQuery dataset.

3. Re-link Firebase to BigQuery: As a last resort, you can try unlinking Firebase from BigQuery and then re-linking them. This might reset any potential issues with the integration.

4. Check for Errors in Firebase Console: Go to the Firebase console and look for any notifications or error messages related to BigQuery integration.

In the meantime, if you're only seeing the events_intraday table, you can continue to query this table for the current day's data. However, remember that this table is meant to be temporary and is deleted at the end of each day, so it's not a long-term solution.

[dhanista_vardha]

Hi Asya_z

We are facing similar issue, could you let us know how did you resolved it 

[asya_z]

Hey!

I still only have the 'events_intraday_' table, and not the 'events_' table.

However, the 'events_intraday_' seems to act like a folder containing tables for the past 325 days (and this number increases by 1 every day). It turned out to be enough for me to query any time period within that date range.