> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.poool.fr/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Detecting Google Discover Traffic for Access

Detecting visitors coming from **Google Discover** allows you to offer a more relevant experience, better suited to their reading context: more direct content, a lighter paywall, or a personalized message, for example.

It is possible to know if a user comes from Google Discover in order to:

* **Set up a specific context** in *Access*
* And therefore **adapt the rendering** based on the traffic source

# Retrieving the Information

Google does not provide very transparent information about visits coming from Discover.  
Currently, the following method is **the best available solution** to try to identify these users, even if it is **not 100% reliable**:

```
function detectGoogleDiscover() {
  const ref = document.referrer || "";
  const ua = navigator.userAgent || "";
  const isGSA = ua.includes("GSA/");
  const isIOS = /iPhone|iPad|iPod/.test(ua);
  const isAndroid = ua.includes("Android");
  const isCriOS = /CriOS\//.test(ua);

  return (
    ref.startsWith("android-app://com.google.android.googlequicksearchbox") || 
    (isGSA && isAndroid && ref === "https://www.google.com") ||            
    (!ref && isGSA && isIOS) ||                                               
    (isCriOS && isIOS && ref === "https://www.google.com")                  
  );
}
```

This method provides a usable signal to detect the majority of Discover visits, but it does **not guarantee complete detection** for all users.

# Pass the information to Poool

Once the information is detected, you can pass it to Poool and create the corresponding targeting in your Dashboard.

## Custom context creation

[![](https://storage.crisp.chat/users/helpdesk/website/-/c/c/8/1/cc81b08ea7515800/c6d3045a-2b18-4524-9632-3ca5e7_1upe5l4.png)](https://downloads.intercomcdn.com/i/o/s22rivig/1777032977/f9e20b67002a86d8f227a493a801/Capture-2Bd-E2-80-99e-CC-81cran-2B2025-10-13-2Ba-CC-80-2B17_32_52.png?expires=1773333000&signature=cca71744f35b5d2102636fe32593c76f12a4a125c5e46431ec112838b70d10f1&req=dScgEcl9n4hYXvMW1HO4zfM6zrn6lIORkuvwc9gZwsuQt5BLUyZRJGmJyxzA%0ABKYYVgf4opMZobIeN7w%3D%0A)

On the technical side, you should create a custom context 👉 https://www.poool.dev/en/docs/access/javascript/configuration#context

This approach remains **the best current solution** to identify Discover traffic and use it effectively in *Access*, allowing you to **adapt the user experience** based on the acquisition source.