Collecting and updating data about Google Ads campaigns with auto-tagging in session data tables

If you are using auto-tagging in your Google Ads campaigns, the page URLs contain only the gclid parameter, which stores campaign names, keywords, and other parameters.

In order to automatically retrieve these data from the gclid parameter and upload them to the session data tables “owoxbi_sessions”, you need to set up Google Ads report data collection to Google BigQuery, then connect the resulting dataset to your user behavior data collection pipeline.

Read how to set up report data collection and connect the data to your pipeline in this article.

As a result, the “owoxbi_sessions” tables get values for these fields:

• trafficSource.source: google
• trafficSource.medium: cpc
• trafficSource.campaign
• trafficSource.keyword
• trafficSource.adGroup
• trafficSource.keywordMatchType

The values google/cpc corresponds exactly to the Google Analytics processing flow.

How does OWOX BI update the Google Ads campaign data in the session data tables?

To keep your data consistent and up to date, OWOX BI updates the ad campaigns data in the “owoxbi_sessions” at 7:00 AM, 9:00 AM, 12:00 PM and 15:00 PM daily. Please note that data synchronization is scheduled according to the timezone of your Google Analytics view.

Why my Google Ads campaign data in the “owoxbi_sessions” table doesn’t match data in Google Analytics or simply missing?

If your Google Ads campaign data collection is set up correctly, some discrepancies are still possible. Such situations occur when data in the source table has been updated after the last session data table update has ended.

In this case, data will not be lost. It will get to the “owoxbi_sessions” table during the next update.

NoteIf you use both auto-tagging and manual tagging in your Google Ads campaigns, read this article.