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

# Diagnose missing traffic data

> Check the source, collection state and URL scope before interpreting an empty traffic report.

Use this guide when Traffic is empty, a source needs attention, or two Projects appear to show the same visits. A connection can be configured before any data arrives.

## Start with the source

Open the correct Project and **Traffic → Setup**. When sources are missing, the toolbar button reads **Connect N sources**, with the number still to connect.

| What you want to measure | Source to check |
| - | - |
| Visits attributed to AI referrals | Google Analytics or the Videntic pixel, according to the report |
| Google search queries and clicks | Google Search Console |
| Live visits collected by the website pixel | Videntic pixel |
| Requests from AI crawlers | Cloudflare or server logs |

AI Visibility comes from measured AI responses, not these visit sources. A crawler request does not prove a human visit or a citation.

## Google is connected, but the report is empty

If Setup shows **Needs attention** and asks you to choose a property, follow [Google traffic data](https://docs.videntic.com/integrations/google-traffic.md). Analytics 4 and Search Console each need their own property selection. Ask the property's administrator for access if the right property is missing.

After saving the selection, check the source's **Last synced** time and any error. Let a running sync finish. If it failed, resolve the displayed problem before using **Sync now**. Reconnect only when authorization needs restoring. Then check the report's date range and URL scope against the property you selected.

## The pixel is installed but waiting for its first visit

Setup can show **Needs attention** while the pixel card says **Waiting for first visit**. Installation alone does not establish that a visit was collected.

1. Open the pixel's Developer guide and confirm the installation is for this Project and the intended host.
2. Make a test visit to that site and grant statistics consent through its normal consent controls. Nothing is collected before consent is granted.
3. Return to the pixel card. **Collecting** and a received visit show that collection has started. If it still waits, ask the website developer to check the installation and consent signal using the Developer guide. Do not bypass visitors' consent choices.

If the card says **Off**, review the setup before enabling collection. Do not interpret an inactive pixel as evidence of no visits.

## You cannot use Cloudflare

For a site behind Cloudflare, use [the Cloudflare connection](https://docs.videntic.com/integrations/cloudflare.md). Otherwise choose **Use server logs** in the AI bot source setup. Ask the hosting administrator or developer whether they can forward crawler request logs to the supplied log-drain address; this requires access to server logs.

Save the address securely before leaving the setup step: it is shown only once. Follow the displayed forwarding instructions. Use one crawler source for the site, rather than forwarding the same requests through both sources.

A log-drain connection can appear connected as soon as its address is created. Ask the developer to confirm that requests were forwarded, then check for received crawler activity. If none has arrived, do not conclude that no crawlers visited. The browser pixel cannot replace server-side crawler logs.

## Two Markets show the same traffic

Check the selected Google properties and saved URL scope in each Project before comparing them. A shared property can include several markets. Confirm that the paths you intend to compare are actually included in each scope; a Project's Market does not by itself split a shared property's visits.

Pixel measurements use their own collection view: they respect the saved URL scope but do not follow the report's date and report filters. Check the period shown in that view before comparing totals.

## Expected result and escalation

You have identified the source and checked evidence that it is receiving data, or identified a setup problem for the source administrator to resolve. Return to [investigating traffic](https://docs.videntic.com/playbooks/traffic/investigate.md) only when the source, period and scope match the question.

If it still fails, email [info@videntic.com](mailto:info@videntic.com) with the Project, source, selected property or host, date range, URL scope, visible status and last sync or test-visit time. Include the error text, but no passwords, tokens or log-drain addresses.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.