> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/onboarding/lead-gen/wordpress-+-hubspot.md).

# WordPress + HubSpot

Describes how to use Blotout for customer funnels between your Wordpress site and HubSpot CRM to power multi-channel attribution

**Does this use case apply to you?**

1. Your site is hosted/implemented using Wordpress with no customizations
   1. See headless docs if you have customizations to ensure all landing pages are covered
2. Your CRM is HubSpot
3. You use paid advertising for lead generation and attribution is broken
4. You are at that scale where signal scaling is critical due to multi channel attribution

**Pre Requisites for your Install:**

1. Be able to install app on Hubspot&#x20;
2. Be ablie to install plug-in on Wordpress
3. Be able to drop code for custom landing pages \[ if applicable ]
4. Ability to get DNS records installed to setup server side


---

# 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.edgetag.io/onboarding/lead-gen/wordpress-+-hubspot.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.
