Destination
Sometimes the honest answer to a reporting question is a spreadsheet. Attribi appends a row to a Google Sheet you choose every time someone converts on your site, carrying the visit history behind that conversion rather than just the form fields. It is a one-way export and not a CRM connection: nothing is read back out of the sheet, and revenue does not appear in it.
No credit card required · 5-minute setup
When a visitor converts on your site, Attribi appends one row to your sheet with the timestamp, visitor id, email, phone, how many touchpoints that person had, and how many separate sessions they took. Rows are appended, so nothing you have already written is overwritten.
Each row carries the first, second, third from last, second from last, and final touch, each with its source, medium, campaign, content, term, click ID, click ID platform and referrer. That is 46 columns, which is enough to rebuild most of a path in a pivot table.
You choose the spreadsheet and the specific tab through Google’s own file picker rather than pasting an id. Attribi requests per-file access, so the permission it holds covers the sheet you selected and nothing else in your Drive.
Authorize Google Sheets from the Connections page. Attribi asks only for permission to the files you open with it, so the consent screen does not request access to your Drive as a whole and you are not granting a blanket read of everything you own.
The file picker lists your spreadsheets; pick one, then pick the tab within it. A dedicated sheet works better than a tab that already has formulas below the data, because Attribi appends to the first empty row and does not rearrange anything.
Attribi writes data rows only, never a header row, so put your own headings in row one if you want them: timestamp, visitor, email, phone, touch count, session count, then five groups of eight touch columns. From then on rows arrive as conversions happen.
Stages Attribi supports for Google Sheets.
Destination
An attribution webhook integration that POSTs signed lead, qualified and closed-won events to your endpoint, so you can send attribution anywhere.
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.
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.
No. The sheet receives one row at the moment a lead is captured and is never revisited. When that person is later marked qualified or closed won, Attribi updates its own records and uploads conversions to your ad platforms, but it does not go back and add a row or a value to your spreadsheet. If revenue in a spreadsheet is what you need, export it from the Attribi reports instead, or send it to your own system through the outbound webhook, which does fire on all three stages.
It is an export of leads captured on your website, not of everything Attribi holds. A lead that exists only because Attribi found it in your CRM never passes through the conversion path that writes to the sheet, so it will not appear. Anonymous visitors who never converted are not in there either. Think of it as a running log of conversions with their journeys attached rather than a mirror of the database.
Forty-six columns. First the timestamp, the visitor id, the email, the phone, the number of touchpoints and the number of sessions. Then five blocks of eight columns, one block each for the first touch, the second touch, the third from last, the second from last, and the final touch. Every block holds source, medium, campaign, UTM content, UTM term, click ID, the platform that click ID belongs to, and the referrer. A visitor with more than five touches has the middle of their journey summarised rather than exported.
Only the file you picked. The connection requests per-file access rather than full Drive access, which means Google grants Attribi permission to the specific spreadsheet you selected through the picker and nothing else. Other files, other spreadsheets and anything shared with you stay invisible to it. Disconnecting from the Connections page removes the stored token.
No. If the same visitor submits again and Attribi recognises it as the same conversion, the second submission is folded into the existing lead and no new row is appended. That keeps a sheet usable for counting without a deduplication step of your own. Genuinely separate conversions from the same person do get their own rows.
Updated
Sign up and connect it from the Connections page.
Start FreeNo credit card · Free forever up to 1,000 visitors