Data Issues

Use this page when a report is empty, a number looks wrong, or a section asks you to change a setting. Each heading is the message or problem you see.

"No … synced for this range yet"

You may see one of these messages on the Analytics screen or the Unified Dashboard:

• "No landing page data synced for this range yet."
• "No device data synced for this range yet."
• "No traffic data synced for this range yet."
• "No Search Console data synced for this range yet."
• "No Search Console page data synced for this range yet."

Why it happens: Prism has no synced data for the dates you picked. This happens when a source was just connected, when the range is older than the history Prism loaded, or when the module is switched off for the project. A module that is switched off is not synced.

How to fix it:

1. Pick a shorter, more recent range, such as 28 days.
2. Open System→Integrations & MCP and check that the card shows ● Connected with "synced through" a recent date.
3. If you just connected, wait for the first sync. It loads up to 180 days of history.

What to check next: if the connector card says "No syncs yet", the first sync has not run. See Data sync schedule.

The newest days look low

Why it happens: Google needs time to finish its numbers. Prism's data runs through two days ago. Report date ranges end three days before today, so the newest day shown is complete. If a recent day comes back empty, Prism retries it for up to 5 more days.

How to fix it:

1. Wait one or two days. The numbers fill in.
2. Compare whole periods, such as 28 days against the preceding 28 days.

What to check next: see Data sync schedule for when Search Console and GA4 sync each day.

"No synced data in this range"

Why it happens: This is the tooltip on a date preset that is greyed out. Every preset is trimmed to the dates that have synced. If no synced data falls inside a preset, Prism disables it.

How to fix it:

1. Pick a different preset, or click Custom and choose synced days.
2. In the calendar, only synced days can be clicked.

What to check next: if no presets work, check your connection on the Integrations screen. Also see Date ranges and Compare.

GA4 and Search Console numbers do not match

Why it happens: GA4 sessions and Search Console clicks come from separate tracking systems. They use different attribution windows, bot filtering and consent handling. Prism shows them side by side for context, not as one count.

How to fix it:

1. Nothing is broken. Expect a gap between sessions and clicks.
2. Compare GA4 numbers with GA4, and Search Console numbers with Search Console.
3. When you check Prism against Google's own tools, use exactly the same dates.

What to check next: read Reading charts and Understanding metrics.

A list does not add up to the total, or I see "(not set)"

Why it happens: Search Console hides some queries and pages for privacy. Prism takes the Search Console total and subtracts every known row. What is left is shown as (not set). This way the totals match Search Console. The row only appears when it is at least 1.

How to fix it:

1. Nothing is broken. Add the (not set) row to the list to reach the total.
2. On the Keywords Breakdown tab, read the coverage bar. It shows what share of clicks come from known keywords.

What to check next: read (not set) explained.

"No branded keyword pattern yet"

The full message is "No branded keyword pattern yet — add one in settings to split keywords into Branded and Non-branded." On the Root Cause tab, the All queries / Branded / Non-branded toggle is also greyed out with the tooltip "Configure a branded keyword pattern in Settings first".

Why it happens: Prism needs a branded keyword pattern to tell brand searches apart from the rest. A branded keyword is a search that includes your brand name.

How to fix it:

1. In Advanced Analytics, click Settings. This opens Category Builder.
2. Open the Branded Keywords tab.
3. Type your pattern, for example techmagnate|tech magnate|techmagnet. Use | between spelling variants.
4. Click Save. You see "Saved".

What to check next: see Branded keywords.

"Your branded keyword pattern uses syntax the keyword database can't run"

The full message is "Your branded keyword pattern uses syntax the keyword database can't run (e.g. lookbehind). Simplify it in settings to see this split."

Why it happens: Your pattern is a valid regex, but it uses advanced parts, such as lookbehind, that the keyword database cannot run.

How to fix it:

1. Open Settings → Branded Keywords.
2. Remove the advanced parts. Use a simple list of words joined with |.
3. Click Save and reload the Keywords Breakdown tab.

What to check next: matching is not case-sensitive, so you do not need separate upper-case and lower-case versions.

"Turn on Compare…" messages

You may see:

• "Turn on Compare to see period-over-period movers."
• "Turn on Compare to see movers." (also "…decay.", "…new URLs.", "…trajectory.")
• "Turn on Compare (date picker, top right) to see what went up and down this period."
• "Turn on Compare (date picker, top right) to see period-over-period hits and misses."
• The tooltip "Turn on Compare to see this list" on a greyed-out keyword list.

Why it happens: These sections compare two periods. Compare is switched off, so there is no second period.

How to fix it:

1. Open the date picker at the top right of Advanced Analytics.
2. Switch on Compare.
3. Pick Preceding period, Same period last year or Custom.
4. Click Apply.

What to check next: see Date ranges and Compare.

"Last synced N days ago — too stale to show as a current dashboard"

Why it happens: On the Unified Dashboard, a ranking module card hides its data when the last sync is older than 45 days. Old numbers would give a wrong picture of today.

How to fix it:

1. Ask your project admin to check the tracking project in Project settings in the Client panel.
2. Check that it has keywords and a Sync Frequency set.

What to check next: if the card says "No ranking data has synced yet for this project.", the tracking project has not produced data yet. See Unified Dashboard.

"Not enough data points for this range yet."

Why it happens: A chart needs several days of data to draw a line. Your range is too short or has too few synced days.

How to fix it:

1. Pick a longer range, such as 28 days or 90 days.
2. Check that the source is connected and has synced.

What to check next: similar messages include "Not enough data in range to plot a trend." and "No trend data for this range."