Common Doubts and possible Bugs & errors

Clear answers to common doubts, possible bugs or data issues

Solve your doubts
Common doubts or possible errors & bugs
Can't find the solution?
Report not accesible

The Issue

You try to open a dashboard or tool, but the screen remains blank or shows a "Permission Denied" message.

Possible Cause

You are likely logged into your browser with a different email address than the one you used to register for Clevertrek. Access permissions are strictly tied to your registered account.

Possible Solution

Ensure your browser's primary profile or active session matches your Clevertrek registration email. If you use multiple accounts, try opening Clevertrek in an Incognito window and logging in with your registered email to bypass browser profile conflicts.

Connector not showing my accounts

The Issue

When trying to link a source (Google Ads, Search Console, etc.), your specific accounts or properties do not appear in the dropdown list.

Possible Cause

You are not logged into your browser with the Google account that has access to those platforms. For other platforms, the authorized email might not match your active session.

Possible Solution

Ensure your browser session is logged into the specific account that holds the permissions for your data sources.

Pro Tip

We strongly recommend unifying all your platform permissions under a single email address to avoid conflicts and ensure a seamless connection across different tools.

Connection Error Displaying Chart or Data

The Issue

A specific chart fails to load, showing a "System Error" or a connection failure message instead of your data.

Main & Most Common Cause

API Rate Limit Exceeded. This happens when too many requests are sent to the platform (Google/Meta) in a short time. It is the most frequent reason for data not displaying.

Secondary Causes

Ongoing Updates:

Platforms refresh data periodically; accessing a report during this process can cause temporary glitches.

Free Connector Limits:

Some connectors have tighter restrictions on how much data they can fetch at once.

The Quick Fix (Highly Recommended)

Change the date range by just one day (forward or backward) in the date picker. This forces the system to bypass the saturated cache and trigger a fresh, successful data call. This usually fixes the issue instantly.

Alternative Solutions

If the date trick doesn't work, close the tool and wait 5–10 minutes for the API limit to reset. For persistent errors, try opening the report in a new session.

Charts Error When Applying a Filter

The Issue

The dashboard works perfectly until a specific filter is applied, at which point the charts display an error or show no data.

The Cause

This is usually caused by a filter combination that is technically impossible to generate on a specific platform. For example, demographic dimensions (Country, Age, or Gender) often conflict with granular data like Keywords or Search Terms due to privacy and API restrictions.

Platform Specifics

In Google Ads, filtering by specific "Conversion Types" while cross-referencing very detailed elements like "Search Terms" can also trigger these conflicts.

Possible Solution

In these cases, there is no technical "fix" other than finding an alternative path to the information by simplifying the filter layers.

Need Help? If you are struggling to find a specific data view, please don’t hesitate to contact us; we can help you find the best way to visualize your metrics.

Different Result for the Same Metric

The Issue

You notice slight discrepancies in the same metric (e.g., Conversions or Spend) when comparing two different charts or tables within the dashboard.

Usually the Main Cause

This is usually due to how platforms group data by time intervals. Since different data sources or charts might process time zones differently, a "Yesterday" range might capture slightly different data points when viewed in isolation versus when it is part of a "Last 30 Days" range.

Secondary Factors

Differences can also arise from attribution windows or whether a chart is configured to show "Event Time" versus "Conversion Time."

Possible Solution

There is no technical "fix" other than understanding the data context and focusing on trends. Slight variations are normal in multi-platform reporting.

The Pro Trick

To force the data to align, try extending the date selector by one day (e.g., setting the end date to "Tomorrow"). This often forces the API to reconcile the time zone overlap and synchronize the daily totals across all charts.

Different Result from the Source Platform

The Issue

You notice that the data in Clevertrek does not perfectly match what you see directly inside the native platform (e.g., Google Ads or Meta) at a specific moment.

The Cause

This is primarily due to data latency and time zone synchronization. Platforms like Google and Meta can take 24–48 hours to fully finalize conversion data, so numbers may align at certain times of the day but show slight discrepancies at others.

Data Aggregation Discrepancies

If the difference is significant, there is likely a discrepancy in how data is aggregated between the source platform and the data connector. This is especially common with relative metrics like averages (e.g., CPC or CTR).

The Clevertrek Solution

To solve this, we do not use the pre-aggregated averages provided by the data sources. Instead, we define our own formulas directly within the charts to ensure calculations are accurate based on raw totals, providing a more reliable result.

The Pro Trick for small differences

To help reconcile daily differences, try setting the end date in the selector to "Tomorrow". This often forces the system to bridge the time zone gap and fetch the most recent data available.

Need an Audit?

If discrepancies remain large, please contact our support team so we can investigate the specific connection.

Doubts / Errors about a Calculations

The Issue

A calculated metric (like a custom Index, ROAS, or average) doesn't seem to match your manual expectations or appears unusual.

Technical Cause

This can sometimes stem from incorrect data aggregation. While we strive for perfect reconciliation with every platform, data structures can be complex, and there is always room for improvement in how variables are combined.

Conceptual Differences

It’s important to note that some metrics may use moving averages or specific calculation logic that differs from "standard" static views. This doesn't mean the data is incorrect, but rather that it offers a different perspective or "concept" of performance that may require a new way of interpretation.

Our Commitment

We are constantly refining our formulas. If you feel a calculation isn't reflecting reality or you have questions about the logic behind it, please contact us. Your feedback helps us improve the accuracy of the entire community.