> 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-create-web-property.md).

# How to create web property

Web properties are individual Web Lead instances that provide a unique tracking code. This could be added to a web app or a website. \
\
Each instance is independent of the other. Instances should be created for one project or startup. Say you are working on Murlist, you will have to create just one property for Murlist and add the code on all user-facing websites and web apps owed by Murlist to centralize the leads generated. \
In this case, one instance will be created for <https://murlist.com>, help.murlist.com, support.murlist.com. You get the idea.

To create a web property, go to the [lead manager](https://murlist.com/leadengine/web-leads).

Click on "create new property" as in the picture below:

![Click on create new leads properties.](/files/-MjMdb9M8hz8-42yQAB5)

Give the property a name. This could be anything, it is meant for your identification only.

![](/files/-MjMeH3nOBMrGwxghrtQ)

Add the domains authorized to send leads to this property

![](/files/-MjMeeaZWnksCbHMsgLo)

That's all. Now head over to the [integration guide here](https://help.murlist.com/murlist-lead-engine/web-leads/how-to-integrate-web-leads-pixel) to learn how to add your website to the leads.


---

# 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-create-web-property.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.