I’m interested in the raw clickstream data from Google Analytics. We are thinking about updating a fork of the Singer Tap. How would we incorporate that into AirByte?

Hiya. I can walk you through that.

for your own personal use, assuming you have already made the change to the singer tap and published in somewhere that pip can pull it from, all you should need to do is: • updated the version of tap that source-google-adwords is using. you can do this in

airbyte-integrations/connectors/source-google-adwords-singer/setup.py

• run

./gradlew :airbyte-integrations:connectors:source-google-adwords:build

• the output of that will be a docker image that contains you update (

airbyte/source-google-adwords-singer

with the tag

dev

). • from there in the airbyte UI if you point at the

dev

version of the source, airbyte will run using your change.

you re-tag the dev docker image to whatever tag will be memorable to you.

that's how you could get your custom version running for yourself in airbyte.

Thank you!

in terms of whether we would rely on this fork in the "official" airbyte version, i'm not totally sure what we would want to do there yet. we sparingly maintain our own forks of some singer taps so that we don't need to wait for them to upstream fixes. but going too far down the path of forking everything can get a bit confusing. my inclination is to say if there were a lot of people asking for this then we would do it, but if you're the only one then it might not make sense just yet.

does that seem fair?

(i'm figuring this out as i go 🙂 )

That sounds great. We are using this data in Tableau, so our team is very interested in the raw data so they have control over the viz. I think this will be useful for other teams as well.

We also love AirByte and would love to contribute where we can. My whole team is quite skilled in Python. So, we thought we would start with the taps.