Google Sheets
Overview
Section titled “Overview”Each lead Signals receives is appended as a row in a spreadsheet Signals creates in your Google Drive. Leads land in a file the team can already filter, sort, comment on and share, without anyone needing a Studio login to see them.
It is the destination teams reach for when a CRM is either absent or too heavy for the job: a small sales team working a list, a marketing team tracking campaign response, a handover between two groups that both live in a sheet.
A sheet is a working surface rather than a system of record. If the leads need to be queried, joined or retained for years, send them to a database or file destination and keep the sheet for the working copy.
Supported sources
Section titled “Supported sources”Sources supported by Google Sheets
| Category | Supported |
|---|---|
| Lead generation |
Prerequisites
Section titled “Prerequisites”- A Google account with permission to create files in the Drive location you intend to use.
Authentication
Section titled “Authentication”In Studio, open Destinations, find the Files category, and click the Google Sheets tile. This connector uses single sign-on.
- Click Sign in and choose the Google account you want to deliver into.
- Grant the requested permissions.
The connection runs as the account you authenticate with. If that person leaves or loses access to the Drive location, delivery stops, so pick an account whose access will outlast the campaign.
Configuration
Section titled “Configuration”Integration type and connection
Section titled “Integration type and connection”Select the Integration Type, which is the lead generation source the leads come from. The options are Meta Lead Ads, Snapchat Lead Generation Ads, TikTok Lead Ads, LinkedIn Lead Ads and Google Forms. Then select the lead ads connection name you want to deliver from, and give the instance a name. The instance name is yours to choose and does not have to match anything.
Spreadsheet configuration
Section titled “Spreadsheet configuration”Name your spreadsheet. You do not choose where it goes: Studio creates the location for you and shows it on screen as the file path, in the form Google Drive, then Datahash, then the lead ads connection name.
So a connection reading a lead form called DummyForm puts its spreadsheet in Google Drive / Datahash / DummyForm. As new leads arrive they are appended to that spreadsheet automatically. Click Finish.
Manage instance
Section titled “Manage instance”One connection writes one spreadsheet. To deliver a second source, or into a second spreadsheet, add another instance with a different spreadsheet name. To change an existing one, open Destinations, go to the Google Sheets category, select the connection, click the edit icon in the top right, update the values and click Finish. Clicking Cancel leaves the previous configuration running.
Data & identifiers
Section titled “Data & identifiers”Leads are delivered as submitted. Personal data is not hashed on this destination, because the system receiving it is your own and the point is that people and applications can read it.
Sheets coerces values as it writes them, which is the most common cause of quiet data damage here. A phone number with a leading zero is read as a number and the zero disappears, long numbers become scientific notation, and anything resembling a date is reformatted to the sheet locale. Format those columns as Plain text once the spreadsheet exists.
Once a row is written, retention and access are governed by the sheet’s sharing settings and your Google Workspace policy, not by Signals.
Which fields arrive is decided by the lead form on the connected source, so a field you need that is not appearing has to be added there.
Verify delivery
Section titled “Verify delivery”Open the spreadsheet after the first leads arrive. Confirm rows are appending, that each value is in the right column, and that the row count matches what the source produced.
Check the identifiers specifically. Phone numbers and postcodes are where coercion shows up, and a column can look fine at a glance while having lost a leading zero on every row. There is no match quality on this destination; the equivalent check is completeness.
Best practices
Section titled “Best practices”- Format phone number and postcode columns as Plain text as soon as the spreadsheet is created. This prevents most data problems on this destination.
- Authenticate with an account that will outlast the campaign. A connection running as someone who has left stops the day their access is removed.
- Keep sharing tight and review it periodically. A sheet link is a full copy of personal data to anyone who holds it.
- Archive to a new spreadsheet on a schedule. Performance degrades well before the cell limit, and a slow sheet is the usual reason teams abandon one.
Troubleshooting & FAQ
Section titled “Troubleshooting & FAQ”No rows are appearing. Usually the authenticated account has lost access to the folder, or the file has been moved. Reconnect and reselect.
Phone numbers have lost their leading zero. The column is formatted as a number. Set it to Plain text. Values already written have to be corrected.
Rows are appearing in the wrong columns. Columns were inserted or reordered in the spreadsheet after it was created.
Duplicate rows. Expected behavior. A sheet cannot reject a duplicate, so check whether the source is re-presenting leads.
The connection stopped after someone renamed the file or folder. Both are selected by name. Restore them, or edit the connection and reselect.
Can I deliver into a spreadsheet I already have? No. Studio creates the spreadsheet and the folder structure itself.