Connect data sources

Connected data sources are persistent organisation-level connections. UX Robot currently supports Google Analytics 4 and Google Search Console. Heatmaps, sitemaps, and other files belong to a dated analysis and are added there instead.

Before starting:

• Sign in to the Google account that can read the required GA4 property and Search Console site.
• Confirm the GA4 property represents the same website as the UX Robot organisation.
• Confirm Search Console lists the correct domain or URL-prefix property.
• Allow the read-only permissions requested by UX Robot. Removing required scopes can leave the connection incomplete.
• If your organisation restricts third-party apps, ask the Google Workspace administrator to approve UX Robot before connecting.

1. Open the organisation and select Data Sources.
2. Find Google Search Console and select Connect.
3. Choose the Google account with access and approve the requested permission.
4. After returning to UX Robot, choose the correct site when more than one verified property is available.
5. Confirm the selected site shown on the Data Sources page matches the organisation website.

Search Console evidence helps explain organic demand, search intent, content gaps, devices and countries, high-impression pages, click-through performance, and changes between periods. A domain property and a URL-prefix property can contain different coverage, so select deliberately.

1. On Data Sources, find Google Analytics 4 and select Connect.
2. Choose the authorised Google account and approve read-only access.
3. Choose the GA4 property for the organisation. Property names can be similar, so check the account and property identity carefully.
4. UX Robot attempts to retrieve the property’s key events. Review the selected property shown after the connection is saved.

GA4 is the required connected source for running an AI analysis in the current application. It supplies traffic, engagement, events, conversions, device patterns, landing pages, journeys, and other reports scoped to the analysis date range.

If goals should align to a GA4 key event, return to the organisation’s Goals section after connecting and update the goal’s analytics event.

Select Reconnect when a token has been revoked, permissions have changed, the Google account is wrong, or the source displays an error. Complete the Google flow again and reselect the required site or property.

• No sites or properties appear: confirm the chosen Google account has direct access, then reconnect.
• The wrong item was selected: use the source’s choose-site or choose-property action and save the correct option.
• GA4 key events cannot be listed: reconnect to refresh access. You can still correct the property selection before collecting reports.
• Data API error: make sure the Google Analytics Data API is enabled for the relevant Google Cloud project and the account can read the property.

Reconnect before starting a new analysis if the source is in an error or disconnected state. Reports already stored on an older analysis remain part of that historical analysis.