> 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-+-calltrackmetrics.md).

# WordPress + CallTrackMetrics

Describes how to use Blotout Edgetag for customer funnels between your site and HubSpot CRM to attribute all of the paid channels (Meta, Google, etc) across your site and HubSpot as a zero code funnel

**Simple check for "who should applies for this use case"**

1. Your site is hosted/implemented using Wordpress
2. Your crm is [CTM](https://www.calltrackingmetrics.com/) \[ Call Tracking Metrics ]
3. You use paid advertising for lead generation
4. You are struggling with attribution; to ad platforms and to your CRM

**Pre Requisites for your Install:**

1. Authority to perform install as agency of record or the brand itself
2. Access to DNS record to build out Server Side; or have the right person who can get this done
3. Access to install a Wordpress plug-in to your site; or have the right person who can get this done
4. Access to CTM  to to capture Lead State change; or have the right person who can get this done


---

# 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-+-calltrackmetrics.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.
