Fields do not match pre-existing StitchData integration

[EricSeastrand]

Not sure if this is intentional, but felt I should call it out:
The current StitchData integration for UA does not prefix the fields with ga_.

For example, my pre-existing Stitch integration has these fields:

bouncerate
campaign
date
end_date
fullreferrer
pageviews
region
sessions
sourcemedium
start_date
timeonpage
transactionrevenue

Whereas the dataset created by this tap has fields like:

ga_bouncerate
ga_campaign
ga_date
ga_fullreferrer
ga_pageviews
ga_region
ga_sessions
ga_sourcemedium
ga_timeonpage
ga_transactionrevenue

I think it's actually beneficial to prefix them with ga_ as it makes it easier to differentiate them from the non-ga-native fields like start_date and end_date. Just wanted to make sure this was intentional so I can avoid (or at least anticipate) future re-work with my own integrations.

[isabelleoliveira3000]

@willcodeforfood, the dataset that I created by this tap has fields with prefix ga: instead of ga_ that you mentioned, for example:

ga:sessions
ga:campaign
ga:eventCategory

Could you or anyone please answer me if it has changed from the beginning of the year to today? :)

[EricSeastrand]

I can confirm the same behavior. Though I'm not using this tap directly anymore: we use StitchData to run it for us. So I can't say for sure where : is getting turned into _ (if it's in the tap, or Stitch). In any case, here's what my columns look like in the BigQuery table that Stitch created for us: