Why MIQAS and Google Analytics differ

Comparing MIQAS with Google Analytics is healthy, and the first thing to know is what every attribution platform tells its users: sessions, users, and page views will almost never match, by design. The two tools measure with different rulers. Here is each difference, plainly.

1. Different definitions for the same words

GA4's "active user" requires an engagement signal and its event count mixes page views with scrolls, clicks, and video plays. MIQAS counts page loads as page views and any visitor who loaded a page as a user. Same visitor, different arithmetic.

2. Consent banners and ad blockers

Google Analytics runs as a third-party script: visitors who decline the cookie banner or browse with an ad blocker are invisible to it. The MIQAS pixel is first-party and unaffected, so over the same period MIQAS typically counts more visitors than GA, not fewer.

3. Different data start dates

A "Last 30 days" window only compares fairly when both tools were collecting for all 30. If the MIQAS pixel was installed mid-window, its totals cover only the days since installation while GA shows the full month. Check each tool's first day of data before comparing totals.

4. Filters and exclusions

MIQAS deliberately excludes app and admin pages from marketing traffic; GA setups often exclude specific IP addresses (an office, a founder's laptop). Each exclusion moves one tool's numbers and not the other's.

Where the two SHOULD agree: revenue

Traffic metrics are definitional; money is not. Orders and revenue in MIQAS come from your store itself, so they reconcile to the riyal against your platform's own reports. That is the number to trust and compare; it is also why every attribution platform anchors truth to backend sales rather than sessions.