> For the complete documentation index, see [llms.txt](https://cmp.docs.sirdata.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cmp.docs.sirdata.net/en/install/in-a-cms/loading-in-wordpress.md). # Loading in Wordpress First, make sure you have enabled support for the WordPress Consent Mode: * Log in to your account at . * Open your CMP configuration. * Go to the **"Add-ons"** page. * Enable the **"WP Consent API connector"** option. * Save and publish your changes.

Make sure to activate the [WP Consent API](https://wordpress.org/plugins/wp-consent-api/) addon in your WordPress account. ## Then, 2 methods, via the plugin or directly in the source code 👍 **A) Via the Sirdata CMP extension** 1. **Download the plugin** {% embed url="" %} 2. **In Wordpress select “Add an extension”** in the Extensions section

3. **Select “Upload extension”**, “Choose file” and import the extension zip. Finally, click “Install”

4. Once the installation is complete, **click on “activate extension”**

5. **The Sirdata plugin is activated** on your Wordpress, all that remains is to configure it

**B) Directly in the source code of your template** Here are the steps to copy/paste the Sirdata CMP tag into the header of your WordPress website. 1. Select "Theme Editor" in the "Appearance" section:

2. In your active WordPress theme, select the theme header (file: header.php): Select header.php.

3. Paste the code snippet of the CMP just above the tag:

4. Save the modification of the file:

That's it! Your Sirdata CMP is now deployed on your WordPress 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://cmp.docs.sirdata.net/en/install/in-a-cms/loading-in-wordpress.md?ask=&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.