CRM
Most attribution tools treat HubSpot as a place to dump a lead. Attribi treats it as the record of truth in both directions: the campaign, source, and journey that produced a contact are written onto the contact itself where your salespeople already look, and when the deal closes the amount comes back out to Attribi and goes on to every ad platform you have connected. Nothing is exported, re-keyed, or reconciled by hand at month end.
No credit card required · 5-minute setup
Attribi creates 16 properties in their own MTA Attribution group on your Contact object, covering first touch, last touch, the full journey, the landing page, and the click ID. Your reps see where a contact came from without leaving HubSpot.
When someone converts on your site, the contact is matched by email and the attribution properties are written. You choose the behaviour at connect time: create the contact if it is new, or only enrich contacts HubSpot already holds and never create one.
Attribi reads your deals on a schedule and uses HubSpot’s own closed-won flag rather than a stage name, so renaming a stage or running several pipelines does not break it. The deal amount and its own currency come across exactly as HubSpot recorded them.
A deal that closes in HubSpot becomes an offline conversion on every ad platform you have connected, carrying its value and currency. This is the step that lets Google, Meta, LinkedIn, TikTok, Microsoft, and Snapchat report on revenue instead of form fills.
A HubSpot form can drop the ad click ID into the MTA Click ID property with a hidden field. Attribi reads it back off the contact when the deal closes, so the upload can be matched on the click even when no script ever ran on your site.
Authorize HubSpot from the Connections page and pick how Attribi should behave: full, where a converting visitor becomes a contact if HubSpot does not have one, or attribution only, where Attribi never creates a contact and only enriches records you already own.
One button creates all 16 properties and their property group inside your portal. It is safe to click again after fixing a permission problem, because properties that already exist are left alone rather than duplicated.
Paste the deal stage IDs you treat as qualified, which you copy from HubSpot Settings under Pipelines. Closed-won detection needs no setup and runs either way. Leave the qualified list empty and Attribi reports on closed deals only.
Stages Attribi supports for HubSpot.
CRM
Salesforce offline conversion tracking: won Opportunities upload to your ad platforms as revenue, matched on email and phone, using your own stage names.
Ad platform
Google Ads offline conversion tracking: send qualified leads and closed-won revenue from your CRM, so your account sees CRM-verified outcomes, not just form fills.
Ad platform
Meta Conversions API for CRM: send qualified leads and closed-won revenue from your CRM to Meta server side, with hashed email, phone, and Instant Form lead IDs.
No. One button on the Connections page creates all 16 attribution properties, grouped together as MTA Attribution so they are easy to find on the contact record. Nothing has to be typed into HubSpot settings by hand, and clicking it twice is safe because existing properties are skipped rather than duplicated. On a free portal HubSpot may refuse to create custom properties at all; Attribi tells you which one it was blocked on so you can add it manually or upgrade.
Only if you ask it to. Full mode matches by email and creates the contact when HubSpot does not have one. Attribution only mode never creates anything: it looks the contact up by email, enriches the attribution properties if it finds one, and does nothing at all if it does not. Pick the second if your database hygiene rules do not allow an outside tool to create records.
It uses the closed-won flag HubSpot itself keeps on the deal, not a stage called Closed Won, so custom pipelines and renamed stages are handled without configuration. The value uploaded is the deal amount in the deal’s own currency. A deal that is won but has no amount on it is recorded without firing a revenue conversion, because there is no figure to send.
Yes for the outcomes. A HubSpot form can capture the ad click ID into a hidden field, and Attribi reads it back off the contact, so qualified and closed-won conversions upload with click-ID matching and no script anywhere on your site. What you give up is the visit history: without the script there are no page views or multi-touch path, only what HubSpot holds.
The ones you nominate. Attribi asks for deal stage IDs rather than names, because names get renamed and IDs do not, and you copy them from your pipeline settings. If you leave the list empty, qualified detection is simply off and Attribi still reports and uploads closed-won deals.
Updated
Sign up and connect it from the Connections page.
Start FreeNo credit card · Free forever up to 1,000 visitors