Customers
Know which pages produced deals, not just forms.
A form submission tells you somebody was interested. HubSpot knows whether they bought. Siteleon carries the page, the search and the campaign behind each enquiry into your CRM, then reads the deal outcome back — so a service page is judged on the work it won rather than the clicks it collected. Your pipeline stays in HubSpot and stays authoritative.
What connects
You connect one HubSpot portal and map the fields that hold the landing page, service and source. Siteleon creates contacts and timeline events, and reads deals; everything else in the portal is left alone.
What data moves, and which way
- Sent: each enquiry as a contact, with the page it came from, the service asked about and the source that brought the visitor.
- Sent: a conversion event on the contact timeline when someone submits a form, starts a chat or books a visit.
- Received: deal stage, amount, close date and owner, matched back to the enquiry that started it.
- Received: lifecycle stage and contact changes your team makes, so Siteleon does not show a lead as new after you have already spoken to them.
What Siteleon can do with it
- See that the maintenance page produced eleven enquiries and four signed contracts while the emergency page produced more enquiries and fewer contracts — and act on the difference.
- Recognise a contact who has enquired before, so your team is told it is a returning customer rather than a fresh lead.
- Route an enquiry to the right HubSpot owner by service and region as it arrives, instead of at the morning meeting.
- Spot a service that closes deals reliably and has almost no content behind it.
Things you could ask for once it is on
- “Which landing pages produced the deals we closed this quarter, and what were they worth?”
- “Assign restaurant enquiries in Valencia to Ana in HubSpot and property-manager enquiries to Luis.”
- “Show me services we regularly win deals for that have no page of their own.”
Setting it up
Four steps, in this order.
- 01Open Integrations, choose HubSpot and connect the portal — use a sandbox first if your team keeps one.
- 02Map Siteleon fields to HubSpot properties, including the properties that hold the landing page and the requested service.
- 03Choose which pipelines and stages count as won, so revenue figures mean the same thing in both systems.
- 04Submit a test enquiry, check the contact, the timeline event and the routing, then switch the connection live.
Permissions
Siteleon asks to read contacts, companies and deals, and to create or update only the contacts and timeline events it produces. It never asks for your marketing email, sequences, templates, workflows or billing, and it does not need write access to deals at all.
Where it stops
HubSpot stays in charge of the pipeline. Siteleon does not move deals between stages, edit amounts, delete records or send marketing email on your behalf. Matching depends on a shared email address or phone number, so a deal created by hand for a customer who never touched the website is not attributed to a page — and should not be. Deal changes arrive on a schedule rather than the instant they happen, so a revenue figure in Siteleon can be a little behind the one in HubSpot.
Customers
Others in this group.
Your business online. Built to adapt.
Start with the site you already have, or create something new. Siteleon helps you build it, understand it and keep improving it as the business changes.
No technical setup · Keep your existing site if you want to · [email protected]