> ## 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 Engage

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

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

* **Create a custom filter** with *Engage*
* 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 filter creation

[![](https://storage.crisp.chat/users/helpdesk/website/-/1/c/8/8/1c88b22c9d921e00/2903b3c8-2a2d-4328-8d36-56ffa9_1sxa162.png)](https://downloads.intercomcdn.com/i/o/s22rivig/1777032973/d2d76c8921dd3c775b8025cce5ba/Capture%2Bd-E2-80-99e-CC-81cran%2B2025-10-13%2Ba-CC-80%2B17_33_15.png?expires=1773333000&signature=3fc748cb46ecf4267deb2001ab43ff9dc0cbd4d6bee4e476d8572d9f12b2b300&req=dScgEcl9n4hYWvMW1HO4zfkELlY%2FKZ0g5EcKFtLxl3tPTl%2Bah1fVhw0C2U80%0AY6p6MiAMUJZbxkuVBc0%3D%0A)

On the technical side, a custom filter should be created 👉 https://www.poool.dev/en/docs/engage/javascript/methods#autocreate

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