# The Universal Integration For static sites, legacy applications, or projects not using a build pipeline, the Universal Script is the most direct method of implementation. This approach utilizes a lightweight JavaScript snippet that loads asynchronously from our global edge network. #### The Script Tag To begin tracking, place the following snippet into the \ section of your HTML document. It should be placed as high as possible to ensure the capture of early page load metrics, but the async attribute ensures it will never block the parsing of your DOM. ``` code Html downloadcontent_copy expand_less ``` #### Attribute Configuration The Universal Script can be configured directly via HTML data attributes. This allows you to control the behavior of the tracker without writing additional JavaScript code. **data-site-id**\ This is the unique identifier for your project. You can find this key in your Signet project settings. It connects the data stream to your specific dashboard. **data-auto-track**\ By default, the script automatically tracks page views. If you wish to manually control when a page view is recorded, you can set this attribute to false and trigger events programmatically. **data-spa**\ If you are building a Single Page Application without a framework specific SDK, setting this attribute to true enables the internal history listener. This ensures that route changes are captured as new page views even when the browser does not perform a full reload. --- # Agent Instructions: 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: ``` GET https://docs.signtoken.vip/3.-implementation/the-universal-integration.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.