Sorry, we don't support your browser.  Install a modern browser

Data Studio Connector More Robust#467

I’m using the AI Search Watcher connector in Data Studio (Looker Studio) for a client monitor. It works with your default template, but we’ve hit the following issues:

Charts fail unless every field is included. Removing columns from the template table, or building a scorecard with a single metric, gives “Data Set Configuration Error – an invalid or unexpected column was received in the data returned from the community connector” (Error ID: 2cc52c83). It looks like the connector returns all columns whatever the chart requests.

A blank To Date breaks the data source. Charts only load once To Date is set explicitly. It would help if a blank value defaulted to the latest check.
Numeric fields are typed as dimensions with no default aggregation. Visibility, Position, Score, Citations Count and the Overall fields all come through as dimensions with aggregation “None”. In a scorecard, Overall Visibility was summed across rows, giving 295, a meaningless figure.

There’s no Date dimension. Dates are only set through the From Date / To Date parameters, so report-level date range controls and “compare to previous period” don’t apply. Comparison date ranges seemed to trigger errors rather than returning empty results.

Date ranges before tracking began cause errors instead of returning no data. For example, a report set to the previous quarter, before the monitor’s first check.
Selecting ChatGPT as the model caused errors in some charts, while “All models” and AI Overviews returned values.

The documentation could be clearer. It would help to document which parameters are required, the date format (YYYY-MM-DD) and the valid Model values. Some field names in the guide don’t match the connector (for example “# of Citations” vs “Citations Count”). It would also help to say clearly that the Looker Studio authentication token is different from the API token, as they’re easy to confuse.

Could you confirm whether these are known issues, and whether a fix is planned, particularly for issue 1, so that charts can request only the fields they need?

Many thanks,
Kezia Bibby
Kezia Bibby Digital Consulting

an hour ago