> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alesta.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Traffic analytics

> Connect Google Analytics and Search Console, then read Alesta's traffic and search lanes.

Traffic combines two independent Google data lanes:

* Google Search Console for search clicks, queries, positions, and countries;
* Google Analytics for active users, engagement, conversions, channels, sources, and landing pages.

You can connect one or both services. Panels remain visible so the workspace can explain which source is missing and what that source would populate.

## Connect Google services

At the top of Traffic, use the Google service cards:

<Steps>
  <Step title="Connect the provider">
    Select the card for Google Analytics or Google Search Console and complete
    the authorization flow.
  </Step>

  <Step title="Select the correct property">
    If the connection shows **Action needed**, choose the account or property
    that belongs to the workspace domain.
  </Step>

  <Step title="Wait for the connection to settle">
    A new connection can show **Connecting** briefly. The affected lane updates
    when the service is ready.
  </Step>

  <Step title="Check attribution">
    Read the displayed Analytics account, property, or Search Console site URL
    before trusting the values.
  </Step>
</Steps>

## Reporting window

Choose **Last 7 days** or **Last 30 days**. Metrics compare the selected window with the previous equivalent window.

Select **Refresh** only when you want Alesta to ask Google again. The control uses the provider's own quota, so ordinary page focus and polling do not force a fresh provider request.

## Traffic panels

When supported by the connected lanes, Traffic can show:

* a visit-to-search funnel;
* traffic, active users, or search clicks over time;
* **How well you're ranking**, including Search Console totals and top queries;
* **What they did on your site**, including engagement and conversions;
* **Where they came from**, including channels and top sources;
* **Top pages** by active users;
* **Where in the world** by search clicks;
* **How people found you**, when the necessary lane data is available.

The panel title adapts to the readable sources. For example, the chart can show only active users when Analytics is readable, or only search clicks when Search Console is readable.

## Preview shapes are not measurements

An unconnected lane can show a blurred preview behind its **Connect** control. The preview demonstrates panel structure. It is not data about your company and must not be reported as a measurement.

## Partial and provider-limited data

One sub-query can fail while the rest of a lane remains useful. Alesta can show the readable tables and omit unavailable totals. Google can also return cardinality buckets or other limitations that prevent breakdowns from summing exactly to a headline total.

Read the limitation sentence beneath the affected panel. Do not manually force totals to match.

## Disconnect or change a property

Use the provider card or **Settings > Integrations** to change a selected property, reconnect an error state, or disconnect the credential. A disconnected lane no longer receives that provider's private data.

## References

* [Connect an integration](/guides/connect-an-integration)
* [Integrations and permissions](/account/integrations-and-permissions)
* [Connections and missing data](/troubleshooting/connections-and-missing-data)
* [Analytics overview](/workspace/analytics-overview)