Skip to main content
Combine AI visibility with website traffic when the project has a connected Google property. Visibility measurements and referral traffic answer different questions and must keep their own dates and units.

​
Check the connection first

Call list_ga4_properties. A response with linked: false means no property is linked to the project. When linked, inspect the returned property, site, and available sync status. Use the IQRush Google Analytics 4 settings to manage the connection; these MCP reading tools do not complete Google authorization or change the link. get_ga4_metadata lists the dimensions and metrics available in the stored data. It does not turn get_ga4_report into a generic Google Analytics query interface.

​
Choose the right read

​
Label the period actually served

The data is stored in snapshots, not fetched live for each request. Date inputs support YYYY-MM-DD and the documented relative values such as 30daysAgo and today. Read resolved_window when present. requested_range and date_range can echo the request without describing the snapshot actually served. Label the report with the returned window and retrieval information, not a date range you assume was fulfilled exactly. If a connected project returns empty Search Console data, inspect gsc_sync_status and gsc_sync_error. A sync failure is not evidence of zero clicks or an unconfigured account.

​
Keep the interpretation specific

A citation is not a visit. An AI-referred visit is not proof that a particular measured answer caused the visit. Product revenue and funnel results depend on the linked property’s ecommerce tracking and available snapshot. Report the observed connection between the datasets as context, without inventing individual-user attribution. The device argument advertised by get_search_console_data is not applied by the HTTP route in this edition. Omit it and do not label the output as device-filtered. This differs from the supported device_category argument on the ecommerce funnel. Next: Report recipes.