GA connector: update dimensions/metrics mid way
Hi everybody,
We are trying to streamline our GA connectors at the minute. This could entail adding some new dimensions to existing datasets or swapping dimensions.
I have done a test on a GA dataset to swap device category for date, and it did not work. The connector allowed me to do the change, but the new run did not change anything. The device category column became null, but the date column did not appear. This does not bode well for the streamlining we are trying to do.
Any idea guys? @jaeW_at_Onyx ?
Thank you very much for your help.
Best Answer
-
I would take a very careful read of all the settings.
To support customers with highly segmented GA datasets and retain multi-year history while minimizing throttling / Google enforced API rate limits, Domo implemented partitioning.
In a nutshell Partitioning means "just update new data as it comes along." It is possible that your settings are using Partitioning, and therefore, when you reran your connector with new settings it did not replace your full history and instead added the new column to the dataset (with NULL for historical data) and just checked for new data.
For experiments sake, try setting up a new GA connector in with the settings you want to confirm you can get the desired results.
If the experiment works, use the new connector in your ETLs OR revisit the existing connector to see if there's a way to force a reset of the data.
If you're confident there's a bug in the product, support@domo.com can help!
Jae Wilson
Check out my 🎥 Domo Training YouTube Channel 👨💻
**Say "Thanks" by clicking the ❤️ in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"0
Answers
-
I would take a very careful read of all the settings.
To support customers with highly segmented GA datasets and retain multi-year history while minimizing throttling / Google enforced API rate limits, Domo implemented partitioning.
In a nutshell Partitioning means "just update new data as it comes along." It is possible that your settings are using Partitioning, and therefore, when you reran your connector with new settings it did not replace your full history and instead added the new column to the dataset (with NULL for historical data) and just checked for new data.
For experiments sake, try setting up a new GA connector in with the settings you want to confirm you can get the desired results.
If the experiment works, use the new connector in your ETLs OR revisit the existing connector to see if there's a way to force a reset of the data.
If you're confident there's a bug in the product, support@domo.com can help!
Jae Wilson
Check out my 🎥 Domo Training YouTube Channel 👨💻
**Say "Thanks" by clicking the ❤️ in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"0 -
Hi @jaeW ,
Thank you for your reply!
I'll check the settings you mentioned and will test things out.What you said around the partitioning could also explain why i cannot get historical data on brand new connectors. I can only get the day before, it cannot do historical data pulls... It shows the option for 30, 60 or 90 days but it never works.
I'll try this out and will come back to you.
Thanks again.
0
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.6K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 2.9K Transform
- 102 SQL DataFlows
- 626 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 754 Beast Mode
- 61 App Studio
- 41 Variables
- 693 Automate
- 178 Apps
- 456 APIs & Domo Developer
- 49 Workflows
- 10 DomoAI
- 38 Predict
- 16 Jupyter Workspaces
- 22 R & Python Tiles
- 398 Distribute
- 115 Domo Everywhere
- 276 Scheduled Reports
- 7 Software Integrations
- 130 Manage
- 127 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 11 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 110 Community Announcements
- 4.8K Archive