Skip to main content
To homepage To homepage
Solved

GA4 -- Multiple Properties

  • October 21, 2024
  • 4 replies
  • 59 views
M
Starter
Forum|alt.badge.img

Hi,

 

I'm currenty developing the GA4 connector in TimeXtender. With some other tips and tricks of other posts it was quite simple to create the connection.

 

At this moment I have 7 different properties from where all data should be loaded. I've read multiple posts but haven't found a solution to extract data dynamically over a list of properties. 

 

Current setup:

  1. CData Connector -- Google Analytics
    1. In this connector I can filter on property ID.
  2. TimeXtender -- v6xxxx + ODX
  3. Creating managed Queries to filter the relevant data from [GlobalAccessObject]. But haven't found a property id in this list. 

 

I think that currently the only option is to create for each property one connection. Or has someone found another solution?

Best answer by andrew.gebhard

Hi @Maarsen,

It should be possible to create query tables for each property within one data connection where you specify the property as a field in the query, i.e. ‘where propertyid = xxx’. However, you would need to manage a separate query table for each table and property that you want to extract. For this reason, I believe the best solution is to treat each property as a separate data connection. Unfortunately, there is no way to export or sync the selection template, so you'll have to manage selected tables separately for each property. 

Using the REST data source you might be able to achieve this, but it would require a lot of work to remake the API calls from the CDATA for Google Analytics provider in the REST data source. CDATA prepares some tables and views ahead of time that you can simply select, instead of building complex API calls for each piece of information you want to gather. 

TL;DR 
It seems you're on the right track. 

Kind regards,

Andrew

View original
Did this topic help you find an answer to your question?

4 replies

Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Thomas Lind
  • Community Manager
  • 1017 replies
  • October 23, 2024

Hi Maarsen

I would usually use the query explorer, but it seems to have been discontinued. 

Alternatively you can if I remember connect to GA as it was a REST API. So if that is available, it could do stuff like this.

Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

Hi @Maarsen are you able to test using a REST data source? please let us know if you have any follow up questions

M
Starter
Forum|alt.badge.img
  • Maarsen
  • Author
  • Starter
  • 2 replies
  • October 29, 2024

Well at this case I have created 7 data sources with property Id as one of the parameters. So haven't checked out the REST.

andrew.gebhard
TimeXtender Xpert
Forum|alt.badge.img+2
  • andrew.gebhard
  • TimeXtender Xpert
  • 64 replies
  • Answer
  • November 4, 2024

Hi @Maarsen,

It should be possible to create query tables for each property within one data connection where you specify the property as a field in the query, i.e. ‘where propertyid = xxx’. However, you would need to manage a separate query table for each table and property that you want to extract. For this reason, I believe the best solution is to treat each property as a separate data connection. Unfortunately, there is no way to export or sync the selection template, so you'll have to manage selected tables separately for each property. 

Using the REST data source you might be able to achieve this, but it would require a lot of work to remake the API calls from the CDATA for Google Analytics provider in the REST data source. CDATA prepares some tables and views ahead of time that you can simply select, instead of building complex API calls for each piece of information you want to gather. 

TL;DR 
It seems you're on the right track. 

Kind regards,

Andrew

Reply


Most helpful members this week

Terms and ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings