> For the complete documentation index, see [llms.txt](https://globalimpact.gitbook.io/untitled/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://globalimpact.gitbook.io/untitled/marketing-and-testing-opportunities-tools-tips/collecting-data-trial-outcomes/reconciling-fb-ga-reports.md).
# Reconciling FB/GA reports
Facebook's Ad Manager and Google Analytics often report results that seem to have discrepancies. Below, one particular case, and possible explanations.
## What is going on 'in our latest trial'?
## 
## 
* Facebook: We have 50k+ unique impressions, and 1335 clicks
* Google Analytics records only 455 page views, 403 users
* And only about 20 doing any sort of Engagement like scroll or click (if we read it correctly)
#### **1. Where do the other 600 clicks end up? Ad blockers? Do they click the ad and shut down before the page comes up?**
> **JS:** main reasons \[DR: slightly edited\[
>
> \
> 1\. "Do they click the ad and shut down before page comes up?" Yup! Closing the page before the redirect fully loads. Facebook will be as generous as possible with their click reporting.
>
> 2\. ... If a user clicks on the FB ad twice within 30 minutes, then Google Analytics would record that only as a single user and a single session.
>
> 3\. If a user has JavaScript disabled or doesn’t accept cookies, then Google Analytics doesn’t track.
Leticia at Facebook: can be mistaken clicks, this is common.. need a pixel to fix this ..., can change it to 'landing page view'
>
#### 2,. How is it possible that 455 people come to the page and only 20 (under 5%) of them actually even do anything on the page?
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://globalimpact.gitbook.io/untitled/marketing-and-testing-opportunities-tools-tips/collecting-data-trial-outcomes/reconciling-fb-ga-reports.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.