GA Custom Reports not syncing

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Ubuntu
  • Memory / Disk: Shouldn’t be relevant
  • Deployment: Docker
  • Airbyte Version: 0.35.62-alpha
  • Source name/version: Google Analytics 0.1.16
  • Destination name/version: BigQuery 1.0.1
  • Step: during sync
  • Description: So, essentially, I set up a simple GA → BQ connection that works perfectly well for all my fetched schemas. I also added a custom report that I added, it looks like this:

[ { "name": "transaction_marketing_source", "dimensions": [ "ga:date", "ga:browser" ], "metrics": [ "ga:sessions" ] } ]

It’s a very very simple one, that I simplified from what I actually wanted, just to confirm that it’s not working. The syncs go through just fine and all the other tables are in BQ, it’s only that there’s no sign of the custom report - what gives? Am I missing something?

Cheers

1 Like

Hey @notsaman,
Could you please share your sync log?

Hey @alafanechere,

here you go:
logs-24.txt (126.0 KB)

It’s odd, it doesn’t even show up in the last step:

2022-04-11 13:00:57 e[42mnormalizatione[0m > 13:00:57  Found 40 models, 0 tests, 0 snapshots, 0 analyses, 537 macros, 0 operations, 0 seed files, 10 sources, 0 exposures, 0 metrics
2022-04-11 13:00:57 e[42mnormalizatione[0m > 13:00:57  
2022-04-11 13:00:58 e[42mnormalizatione[0m > 13:00:58  Concurrency: 8 threads (target='prod')
2022-04-11 13:00:58 e[42mnormalizatione[0m > 13:00:58  
2022-04-11 13:01:00 e[42mnormalizatione[0m > 13:00:59  1 of 10 START incremental model google_analytics_raw_data.devices....................................................... [RUN]
2022-04-11 13:01:00 e[42mnormalizatione[0m > 13:00:59  2 of 10 START incremental model google_analytics_raw_data.pages......................................................... [RUN]
2022-04-11 13:01:00 e[42mnormalizatione[0m > 13:01:00  3 of 10 START incremental model google_analytics_raw_data.traffic_sources............................................... [RUN]
2022-04-11 13:01:00 e[42mnormalizatione[0m > 13:01:00  4 of 10 START incremental model google_analytics_raw_data.daily_active_users............................................ [RUN]
2022-04-11 13:01:00 e[42mnormalizatione[0m > 13:01:00  5 of 10 START incremental model google_analytics_raw_data.four_weekly_active_users...................................... [RUN]
2022-04-11 13:01:00 e[42mnormalizatione[0m > 13:01:00  6 of 10 START incremental model google_analytics_raw_data.two_weekly_active_users....................................... [RUN]
2022-04-11 13:01:00 e[42mnormalizatione[0m > 13:01:00  7 of 10 START incremental model google_analytics_raw_data.weekly_active_users........................................... [RUN]
2022-04-11 13:01:00 e[42mnormalizatione[0m > 13:01:00  8 of 10 START incremental model google_analytics_raw_data.website_overview.............................................. [RUN]
2022-04-11 13:01:06 e[42mnormalizatione[0m > 13:01:06  7 of 10 OK created incremental model google_analytics_raw_data.weekly_active_users...................................... [MERGE (833.0 rows, 205.1 KB processed) in 5.37s]
2022-04-11 13:01:06 e[42mnormalizatione[0m > 13:01:06  9 of 10 START incremental model google_analytics_raw_data.locations..................................................... [RUN]
2022-04-11 13:01:06 e[42mnormalizatione[0m > 13:01:06  5 of 10 OK created incremental model google_analytics_raw_data.four_weekly_active_users................................. [MERGE (833.0 rows, 216.8 KB processed) in 5.68s]
2022-04-11 13:01:06 e[42mnormalizatione[0m > 13:01:06  10 of 10 START incremental model google_analytics_raw_data.monthly_active_users......................................... [RUN]
2022-04-11 13:01:06 e[42mnormalizatione[0m > 13:01:06  4 of 10 OK created incremental model google_analytics_raw_data.daily_active_users....................................... [MERGE (833.0 rows, 216.8 KB processed) in 5.93s]
2022-04-11 13:01:06 e[42mnormalizatione[0m > 13:01:06  6 of 10 OK created incremental model google_analytics_raw_data.two_weekly_active_users.................................. [MERGE (833.0 rows, 216.8 KB processed) in 5.95s]
2022-04-11 13:01:06 e[42mnormalizatione[0m > 13:01:06  8 of 10 OK created incremental model google_analytics_raw_data.website_overview......................................... [MERGE (833.0 rows, 275.4 KB processed) in 6.26s]
2022-04-11 13:01:07 e[42mnormalizatione[0m > 13:01:07  1 of 10 OK created incremental model google_analytics_raw_data.devices.................................................. [MERGE (19.1k rows, 6.7 MB processed) in 7.44s]
2022-04-11 13:01:07 e[42mnormalizatione[0m > 13:01:07  3 of 10 OK created incremental model google_analytics_raw_data.traffic_sources.......................................... [MERGE (27.4k rows, 8.8 MB processed) in 7.93s]
2022-04-11 13:01:11 e[42mnormalizatione[0m > 13:01:11  10 of 10 OK created incremental model google_analytics_raw_data.monthly_active_users.................................... [MERGE (833.0 rows, 216.8 KB processed) in 4.95s]
2022-04-11 13:01:15 e[42mnormalizatione[0m > 13:01:15  2 of 10 OK created incremental model google_analytics_raw_data.pages.................................................... [MERGE (136.7k rows, 57.6 MB processed) in 15.53s]
2022-04-11 13:01:32 e[42mnormalizatione[0m > 13:01:32  9 of 10 OK created incremental model google_analytics_raw_data.locations................................................ [MERGE (219.6k rows, 86.7 MB processed) in 26.95s]
2022-04-11 13:01:32 e[42mnormalizatione[0m > 13:01:32  
2022-04-11 13:01:32 e[42mnormalizatione[0m > 13:01:32  Finished running 10 incremental models in 35.32s.
2022-04-11 13:01:33 e[42mnormalizatione[0m > 13:01:33  
2022-04-11 13:01:33 e[42mnormalizatione[0m > 13:01:33  Completed successfully

So, for an unrelated problem I used this fork by schlattk and here it works. Curiously enough this is on v 34.2. Odd.

Hi! in case it helps, I solved this issue by resetting the schema. Then the new streams from the custom reports appeared and were synced.

Hi there from the Community Assistance team.
We’re letting you know about an issue we discovered with the back-end process we use to handle topics and responses on the forum. If you experienced a situation where you posted the last message in a topic that did not receive any further replies, please open a new topic to continue the discussion. In addition, if you’re having a problem and find a closed topic on the subject, go ahead and open a new topic on it and we’ll follow up with you. We apologize for the inconvenience, and appreciate your willingness to work with us to provide a supportive community.