No script required
Plenty of teams cannot add another script. The site is locked behind a tag-manager review, the landing pages are owned by someone who guards page weight, or legal has had enough of consent banners. Attribi runs in a CRM-only mode for exactly those cases: your existing forms already collect what is needed, Attribi reads the leads and the revenue out of your CRM, and the qualified and closed-won outcomes go up to your ad platforms with nothing installed on your website.
No credit card required · 5-minute setup
Most attribution tools cannot do anything until their script is live, because the product assumes it owns the touchpoint data. If your site is on a change freeze, or the marketing team does not control the template, or the tag manager needs a security review, the tool sits unused until the quarter turns.
Every additional third-party tag is another line in the cookie banner, another entry in the processing register and another thing to explain in a vendor review. Teams that have already been through that once are reluctant to do it again for a reporting tool.
Your forms already write to your CRM. Your sales team already marks deals won there. The information required to tell an ad platform that a click became revenue is sitting in a system you already trust, and duplicating its collection on the front end feels like the wrong answer.
Your existing form, whichever builder it uses, writes the ad click ID into a hidden field on the record it creates. Attribi creates the fields for you on HubSpot, Salesforce, Zoho and Pipedrive; on Freshsales and LeadSquared you create them once by hand. Nothing is added to the page itself.
New records become leads in Attribi, matched to an existing lead where one exists so nothing is duplicated. Each lead carries whatever identified the click, plus the contact details hashed for matching, and shows in the leads list marked as having come from your CRM.
When a record reaches a stage you count as qualified, or a deal is marked won, the outcome uploads to every ad platform you have connected, with the deal value attached on close. Your ad reporting then shows the outcomes your CRM confirmed, from a site with no attribution script on it.
Both stages upload to all six connected ad platforms from CRM stage changes alone. The form-fill stage is the one that needs the script, because that event happens in the browser and there is nothing in a CRM-only setup to observe it.
Email and phone are hashed and sent with every upload, and all six ad platforms accept a conversion matched on hashed contact details. Nothing depends on a cookie surviving, on a browser storage API, or on the visitor returning in the same session.
Where your form captured the ad click ID into the field Attribi provisions, that click ID is read back at revenue time and used for matching. Live for HubSpot, Zoho, Pipedrive, Freshsales and LeadSquared.
Sixteen attribution fields are created on your contact or lead record, so your salespeople see first touch, last touch, campaign and the full journey path on the record they already work in, without opening Attribi.
A CRM-only setup has no anonymous visitors and no multi-touch journeys, so Attribi shows one synthesised touch per lead and marks the account as having limited attribution rather than presenting a single-touch path as if it were a full one.
Planned, not live today. Listed so you can see what this does not do yet, before you sign up.
Not yet available. Salesforce revenue is matched on email and phone only. The click-ID field is created on the Salesforce lead, but a won opportunity resolves through its contact, which does not carry lead fields, so the click ID is not read back. The fix is a named follow-up in the code, with no date committed.
Not yet available.
Closing the loop
Send qualified leads and closed-won revenue from your CRM to Google, Meta, LinkedIn, TikTok, Microsoft and Snapchat, automatically, with no spreadsheet uploads.
Privacy and data handling
Exactly what Attribi stores, what it hashes before anything reaches an ad platform, and the two privacy capabilities it does not have yet.
CRM
HubSpot ad attribution in both directions: campaign data is written onto the contact your reps already read, and closed deal revenue is pulled back out.
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.
Data source
Shopify multi-touch attribution: paid orders reach Attribi straight from your store with their real total, then upload to your ad platforms as revenue.
Yes. Connect your CRM and your ad platforms and Attribi runs from CRM data alone: leads are read from your CRM, and qualified and closed-won outcomes upload to your ad platforms matched by hashed email and phone, or by an ad click ID your existing form captured into a CRM field. Nothing is added to your website.
Three things. Anonymous visitors are invisible, because nothing observes a visit that never becomes a record. Multi-touch journeys are not reconstructed, so attribution is effectively single-touch and the Truth Gap comparison does not apply. And the initial form-fill conversion does not upload to your ad platforms; qualified and closed-won do.
Your existing form puts it there. Attribi creates a pair of hidden fields on your CRM record, you add matching hidden inputs to the form you already use, and the click ID travels with the submission like any other field. The setup guide has per-builder instructions for the common form tools.
It is live for HubSpot, Zoho, Pipedrive, Freshsales and LeadSquared. For Salesforce the field is created and populated but is not read back at revenue time, so Salesforce deals match on email and phone; that is a known limitation with a fix on the roadmap. Odoo matches on email and phone as well.
Yes, and nothing has to be undone. Adding the script starts recording real visits and multi-touch journeys from that point, and the CRM path keeps working exactly as before. Leads that arrived through the CRM stay marked as such, so you can tell the two populations apart in your reporting rather than having them silently merge.
Updated
Connect your ad platforms and your CRM, and read the answer from your own account.
Start FreeNo credit card · Free forever up to 1,000 visitors