Copy everything in the box and paste it into your AI tool, Claude, Cursor, ChatGPT, Windsurf, any of them. It creates the pixel, gets the snippet into your site’s <head>, adds the privacy paragraph and switches it on.
Set up GetLeads website visitor identification on my site, the people browsing my website, identified and enriched, instead of bouncing anonymously. **Four moves:** create the pixel, get the snippet into my site's `<head>`, add the privacy disclosure, switch it on. You have MCP tools for all of it except the second, which is the only part that is real work. --- ## 1. Before anything else, check GetLeads is connected This is your first move, ahead of reading my site, asking me questions, or touching any code. Look at your own tools for the GetLeads MCP, and if they are there, call `list_website_pixels`. It is free, it takes a second, and it tells you both things at once: that the tools exist and that they are authenticated. **If you have no GetLeads tools at all**, stop and say this to me, in these words: "Hey, if you wanna start identifying the contact details of buyers on your website, you need to make a getleads account first." Then give me two links and nothing else: a free account at https://app.getleads.io, and once I am in, the connect prompt at https://getleads.io/mcp-setup-prompt to hook you up to it. Do not create anything, do not research my site, do not start on the snippet. None of the rest of this is doable until the tools are live. If I am new to GetLeads entirely and want to see what it does first, point me at https://getleads.io/onboarding-get-first-leads. **If the GetLeads tools are there but the call comes back unauthorised or asking me to sign in**, I have an account and the connection has just dropped. Don't send me off to sign up again. Tell me to reauthenticate, https://getleads.io/mcp-setup-prompt has the exact step per client. **If the GetLeads tools are there but the website pixel ones are missing**, you are connected with an API key rather than by signing in, and the pixel tools are not on that connection yet. Don't hunt for them. Tell me to set the pixel up in the app at https://app.getleads.io/live-leads?tab=visitors, and help me with the parts you can: finding my `<head>`, putting the snippet in, and the privacy paragraph. **If `list_website_pixels` returns cleanly**, say nothing about any of this and carry straight on. ## 2. Work out what you are Check your own instructions for your product name. If there isn't one, check your tools instead: **can you read and write files on this machine and run shell commands?** - **Yes** (Claude Code, Cursor, Windsurf, VS Code with an agent extension, Cline, Zed, Codex), you can install this yourself, if my website's source is on this machine. **Ask before assuming the repo you are sitting in is my website.** - **No**, you'll walk me through it. ## 3. Create the pixel Ask for the domain if you don't have it, one per pixel. Call `start_website_visitor_tracking`. That returns the install snippet. It does not make anything live yet. If I run several sites, say so now: an account holds as many pixels as I want and there is no per-domain charge, so putting it on all of them costs nothing extra. ## 4. Get the snippet into my `<head>` **If you can edit the site yourself**, work out what framework it is built on, research the right place to put it inside the `<head>`, and put it there. One insertion, don't reformat anything else. Show me the diff, and tell me it only goes live when I deploy. **If you can't**, ask me what the site is built on. Once I answer, research and find the steps to get to the correct menu names, and give them to me, including whether I have to publish for it to take effect. Menu names move, so if what you told me doesn't match what I'm seeing, look it up again rather than insisting. **One check worth doing:** if you can fetch a URL, load my homepage after I publish and confirm the snippet is in the returned HTML. That catches the two usual failures, pasted in the wrong box or saved but never published. **Do not try to test whether it is identifying anyone**, identification runs on a schedule against real traffic, so a fresh pixel legitimately shows nothing and a "test" proves nothing. ## 5. The privacy disclosure Identifying visitors has to be disclosed in my privacy policy. Either **add it yourself**, or if I don't have a privacy policy, tell me I need to add one and get me to confirm I have. Once I confirm, move on. GetLeads supplies the wording, with a placeholder for the email address data requests go to. That address is mine. Then call `configure_website_pixel` with the domain and `privacy_confirmed: true`, once I have actually confirmed, not to move things along. ## 6. Ask about the webhook Ask whether I want identified people pushed somewhere automatically. If I do, pass `webhook_url` in the same call. If I don't, skip it, destinations can be set later from the Leads section, and stalling the setup over one is a waste. ## 7. Switch it on, and explain the money here **Now**, not earlier. Say it plainly: - **$0.125 per newly identified lead**, taken from a prepaid wallet balance. No subscription, no per-seat fee, no per-domain fee. A repeat visitor is not billed again. - **Auto top-up has to be on before the pixel can go live.** That is a hard requirement, and it is the single most common place this stalls. Call `complete_website_pixel_setup` with the domain. **If auto top-up is off, that call hands back a top-up link, give it to me** and explain it in one line: a prepaid balance the per-lead charges come out of. Then call it again once I've done it. When it returns live, setup is over. Tell me I can add as many other websites as I want, at no extra cost. ## 8. What happens next Identification runs on a schedule from now on, so don't expect names in the next five minutes. People arrive via `list_website_visitor_leads`, and `export_website_visitor_leads` gets them out in bulk. Per person: name, title, work email, LinkedIn URL, and their company's name, domain, industry, size and region, plus which page they were on and when. Then offer me the obvious next thing rather than stopping dead, the people it finds are prospects, and you already have the tools to research them, find their colleagues, or draft the outreach. --- **Three things not to claim.** Never tell me what percentage of my traffic will be identified, nobody has measured that for my site. Never tell me visitors can opt out at a link; there isn't one, and the data-request address in the disclosure is mine. Never say it's live until `complete_website_pixel_setup` says so.
$0.125 per newly identified person, no subscription and no per-site fee. What it does and what you get back: getleads.io/website-visitors