Connect HubSpot
Send leads captured on your hosted pages straight into HubSpot, each one carrying the page that produced it, so pipeline can be traced back to the content that created it.
Updated
When someone fills in a form on one of your hosted pages, PingAura captures the enquiry and scores it. Connecting HubSpot sends that person into your CRM, where your team already works, along with a note recording which page they came from.
Knowing the page behind each lead lets you see which content brings in business.
Before you start
You need a HubSpot CRM account. The free tier is enough. You also need HubSpot on your PingAura plan: it is included in Growth and Pro, and in some enterprise plans.
Use your normal HubSpot account, not a HubSpot developer account. Developer accounts hold no CRM data, so there is nothing for PingAura to send leads to.
Connect it
You approve the connection in HubSpot. There is no key to create or paste.
- In PingAura, open Workspace settings → Integrations. Use Categories → CRM to find HubSpot.
- Click + on the HubSpot card.
- Choose the domain this portal is for.
- Choose what happens to leads you have already captured.
- Click Connect HubSpot.
- In HubSpot, choose your account and approve the permissions below.
You land back on the Integrations page with a confirmation. Your leads start going to HubSpot from then on.
Install from the HubSpot marketplace
You can also start from HubSpot. Find PingAura in the HubSpot marketplace and click Install. This opens the PingAura install page, where you:
- Sign in to PingAura if you are not already.
- Choose the workspace and the domain.
- Continue to HubSpot and approve the permissions.
Installing from the marketplace sends only leads captured from then on. To send earlier leads, connect from Workspace settings → Integrations instead.
If your workspace does not have HubSpot on its plan, the install page shows an upgrade link instead of sending you to HubSpot.
Permissions
HubSpot shows these on its consent screen.
| Permission | Needed for |
|---|---|
Read contacts (crm.objects.contacts.read) | Finding an existing contact |
Write contacts (crm.objects.contacts.write) | Creating and updating the contact |
Write contact properties (crm.schemas.contacts.write) | Optional, see below |
You do not need a notes permission.
The first two are required. The third is optional, and HubSpot lets you untick it. With it, PingAura creates two contact properties, PingAura lead score and PingAura source page, so both are filterable in HubSpot. Without it, connecting still works and every lead still arrives with its page recorded on a note. PingAura only ever adds these two properties.
PingAura keeps your HubSpot access encrypted and renews it for you, so you do not need to reconnect on a schedule.
One HubSpot portal connects per domain, so two brands on the same PingAura account can send to two different portals and neither sees the other's leads. To move a domain to a different portal, disconnect it first. If you approve a different portal from the one already connected, PingAura stops and asks you to disconnect first.
Existing leads
Connecting asks whether to send leads you captured before now.
Only leads captured from now on is the default. Nothing already sitting in your PingAura inbox is sent.
Every lead, including ones already captured sends your whole back catalogue. On an established inbox that can be a large number of contacts arriving in HubSpot at once, and it is not something PingAura can undo for you afterwards. Choose it deliberately.
What arrives in HubSpot
Each lead becomes a contact with the email address, name and phone number the person supplied, plus a note containing:
- when the enquiry was captured
- the page title, its URL, and the type of page
- whatever the person wrote in the message field
If someone who is already in your CRM enquires again, PingAura updates the existing contact rather than creating a duplicate.
When it runs
Leads are sent to HubSpot shortly after someone fills in the form, not instantly. The enquiry is always saved in PingAura first, so a HubSpot outage never loses a lead.
If HubSpot is briefly unavailable, PingAura tries again later. If HubSpot refuses a lead, for example because the email address is not valid, PingAura stops trying and shows the reason against that lead.
Seeing whether it worked
The lead inbox shows the CRM state of every lead once a portal is connected:
- In CRM, with the contact created or updated
- Queued, captured and waiting for the next push
- Failed, with the reason from HubSpot on hover
If HubSpot access is removed, for example because someone uninstalled the app in HubSpot, the next time PingAura tries to send a lead the card on the Integrations page says it needs reconnecting. The affected leads wait rather than being discarded. Click Reconnect with HubSpot and they go out.
PingAura also checks each HubSpot connection once a day, so removed access shows up within a day even when no leads are coming in.
Connected earlier with a key
Connections made earlier with a HubSpot key or token no longer send leads and must reconnect with HubSpot. Their card shows Needs reconnecting with a Reconnect with HubSpot link. Leads captured in the meantime wait, and are sent once you reconnect. Pasting a key is no longer offered.
If you disconnect
Contacts already in HubSpot stay there. They are yours, under your own retention policy, and PingAura does not reach into your CRM to remove them. New leads stop being pushed and remain available in your PingAura inbox.
Click Disconnect on the HubSpot card to remove the connection. Uninstalling the app in HubSpot also stops it. The next time PingAura tries to send a lead, the HubSpot card shows that it needs reconnecting.