> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/get-started/general/difference-between-the-sdk-script-and-html-code-snippet.md).

# Difference between the SDK script and HTML code snippet

The SDK script loads the Didomi SDK for comprehensive consent management, while the HTML code snippet embeds specific Didomi widgets directly into a webpage.

In a PMP context, both the SDK script and the HTML code snippet are used together to ensure proper functioning.

* **SDK Script**: Loads the core Didomi SDK, which is essential for managing user consents and preferences. This script ensures that the necessary libraries and functionalities are available.
* **HTML Code Snippet**: Embeds specific widgets (or preference center) into the webpage. It works in conjunction with the SDK script to render the necessary components at the designated locations within the HTML structure.

Together, they enable comprehensive functionality and proper integration of the preference management platform into your website


---

# 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://docs.didomi.io/get-started/general/difference-between-the-sdk-script-and-html-code-snippet.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.