> For the complete documentation index, see [llms.txt](https://docs.pushpushgo.company/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pushpushgo.company/web-push/integration-script/beacons.md).

# Beacons

Beacons are used to send data about the subscriber's behavior on your website to your PushPushGo account. Thanks to this, we know what subpages they visited and what actions they performed.

PushPushGo offers several strategies for sending beacons to the application. Its choice depends on how your website is built.

<figure><img src="/files/hwPC6UckNbLHwifEaCoX" alt=""><figcaption></figcaption></figure>

**Default**: for pages that reload when an element is clicked

**Hash**: for older SPA pages (Single Page Applications) whose URLs contain "#", e.g. / # / profile /,

**History**: modern SPA pages running on the History API - page reload is not visible as in the default strategy, and there is no "#" sign in the URL

**Visibility change**: detection of an action indicating exiting the page, such as changing the tab, minimizing the browser window. Intended for pages on which, after clicking on a given element, a new tab opens in the browser.

\
All selectors defined on project contain concrete instructions on gathering data from the website and processing it. This is a single piece of information for a beacon.

Each transition on a page, like reloading it, leaving it, or moving to a new subpage, results in sending a beacon with data included in a selector for automation scenario purposes.


---

# 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://docs.pushpushgo.company/web-push/integration-script/beacons.md?ask=<question>&goal=<endgoal>
```

`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.