> For the complete documentation index, see [llms.txt](https://safary-1.gitbook.io/safary-doc-2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://safary-1.gitbook.io/safary-doc-2.0/connect-data/add-safary-script.md).

# Add Safary script

## How Does Safary script work? 

Safary script consists of a simple script tag that you put either in your main web app's root head tag as a child or in your Google Tag Manager. Once you do that -> BOOM! We are already starting to collect data from your website such as wallets that have connected to your web app. For a better overwiev of the users behaviour, you should start setting up events. Check out: [Setup Events](/safary-doc-2.0/connect-data/setup-events.md)

## How Does Safary Collect Wallets? 

See the list of supported wallets :

<details>

<summary>Supported wallets 🔑</summary>

* Metamask
* Coinbase wallet
* Wallet connect (and all compatible wallets)
* Phantom&#x20;
* Solflare
* Trustwallet
* Fuel &#x20;
* Fuelet&#x20;
* Argent (Starknet)
* Braavos (Starknet)
* Keplr&#x20;
* OKX&#x20;
* Rabby
* Gnosis Safe
* Bitcoin wallets
* Cosmos Wallets

</details>

<details>

<summary>Supported networks 📡</summary>

*For all full experience in Safary, supported wallet connexion, balance, and assets*

* Ethereum (connexion + balance + assets)&#x20;
* Solana&#x20;
* Bitcoin&#x20;
* Polygon
* Cosmos
* Binance
* Berachain (Connexion only)
* Starknet (Connexion only)
* Fuel (Connexion only)
* Osmosis Chain
* Aptos

</details>

## Why does my wallet not appear?&#x20;

A wallet won't appear in the following cases:

* After connection wallet A to your app, the user switches to wallet B inside his wallet. Only Wallet A will be shown as "connected"

&#x20;


---

# 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://safary-1.gitbook.io/safary-doc-2.0/connect-data/add-safary-script.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.