> For the complete documentation index, see [llms.txt](https://help.meltingspot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.meltingspot.io/english/manage-spot/customization/scripts.md).

# Scripts

From this tab, you can add a script that will be applied to the `<head>` of all pages in your Spot!

Here are two examples of how you can use this feature:

1. **Tracking Member Traffic:**\
   Connect tools like Google Analytics, Hotjar, Segment, Amplitude, or Mixpanel to automatically track the pages your members visit and the buttons they click. This will give you deeper insights and analytics about your members' activity.
2. **Displaying Tours and Personalized Banners in Your Spot:**\
   If you use a product tour or communication tool like Intercom, Pendo, or WalkMe, you can set up contextual banners directly in your Spot. This allows you to share announcements, tips, or calls to action at the right moment.

{% hint style="warning" %}
**Note:** This feature is available on certain MeltingSpot paid plans. If you don’t have access to this tab, please contact us.
{% endhint %}

***

#### **Implementation**

From the `Scripts` tab in the `Customisation` settings page of your Spot :&#x20;

1. A section with a free text field allows you to enter your desired scripts.
2. Click the `Save` button to save the script. Be careful: if you leave the page without saving, your changes will be lost.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.meltingspot.io/english/manage-spot/customization/scripts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.