> For the complete documentation index, see [llms.txt](https://help.murlist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.murlist.com/murlist-lead-engine/web-leads/how-to-integrate-web-leads-pixel.md).

# How to integrate web leads pixel

To get started with The Web Leads, you will have to complete these two steps.

* Create a web property.
* Add the pixel to your app.

### Create a web property

To learn more about web property and how to create one, follow the guide [here](https://help.murlist.com/murlist-lead-engine/web-leads/how-to-create-web-property).

### Add the pixel to your web app or website.

Upon creation of web property, a unique tracking pixel will be generated. You can see it by clicking on the setup details as in here:

![Click on setup details](/files/-MjM_kqFLF48aRcsbgCJ)

Next, copy the pixel:

![copy the Murlt's web leads tracking](/files/-MjMaEcxdL77219n-Zvc)

The next step is to add this to **the head tag** of your website or web application.

That is all.&#x20;

N.B: The default pixel looks like this:

```
<script async defer data-domain="engine.murlist.com" src="http://engine.murlist.com/yourId" />
```

But can also be implemented this way:

```
(function(m,u,r,l,i,s,t){
           m[r]=m[r]||function(){(m[r].q=m[r].q||[]).push(arguments)};
            s=u.createElement(l);s.async=1;s.src="http://engine.murlist.com/"+i;
            t=u.getElementsByTagName(l)[0];t.parentNode.insertBefore(s,t);
        })(window, document, "murlist", "script", "yourId")
```

Replace "yourId" in the sample code above with the web lead property's ID you wish to integrate.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.murlist.com/murlist-lead-engine/web-leads/how-to-integrate-web-leads-pixel.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
