Google Forms
Overview
Section titled “Overview”Google Forms collects responses in a form you already own. Signals reads those responses as leads and delivers them wherever your team works: a CRM, a spreadsheet, a database, a file drop, an inbox or WhatsApp.
Use this connector when your lead capture lives in a Google Form rather than in an ad platform. It suits enquiry forms, event registrations and any process where the form is the front door.
Signals connects through the Google Forms AppSheet add-on, which reads your form and its linked response sheet and makes the responses available for integration.
Supported destinations
Section titled “Supported destinations”Destinations supported by Google Forms
| Category | Supported |
|---|---|
| CRM | |
| Files & delivery |
Authentication
Section titled “Authentication”In Studio, open Sources, find the Lead generation category, and click the Google Forms tile.
- Click Sign in with Google.
- Select the Google account you want to connect and click Continue.
You are returned to Studio.
Configuration
Section titled “Configuration”Instance Setup
Section titled “Instance Setup”- Give the instance a name. Use the form name if you plan to read several.
- Choose the Google Form you want to send data from.
Test connection
Section titled “Test connection”Click Test Connection before finishing. Signals shows a preview of the responses it can read from the form, which is the quickest way to confirm you picked the right one.
An empty preview usually means the form has no responses yet rather than a broken connection. Submit a test response and try again.
Manage instance
Section titled “Manage instance”One connection reads one form. To read several forms, create several connections.
To add another, open the Manage existing instance table and click Add Instance. Repeat the setup, choosing the Google account, the form and a connection name, then test the connection and click Finish. The new instance appears in the Manage existing instance table.
To change one, click the connection name in the Manage existing instance table, then click the edit option in the menu to the top right. Update the connection name or the form selection, test the connection, then click Finish. If you cancel, the previous configuration continues to run; updates apply only once you finish.
Data & identifiers
Section titled “Data & identifiers”Signals reads the answers to the questions your form asks. Because the questions are yours, the fields available downstream are whatever you chose to collect, so include email or phone if you intend to use the responses for marketing.
Personal identifiers are normalized and SHA-256 hashed before they are sent to any advertising destination. Where the destination is a system of your own, such as a CRM, a spreadsheet, an inbox or a file drop, the lead is delivered as submitted.
Best practices
Section titled “Best practices”- Collect email or phone in the form. Destinations weight these highest, so responses carrying neither match at a much lower rate.
- Avoid renaming or reordering questions once the connection is live. The response sheet columns shift with them and your destination mapping will drift.
- Name each instance after the form it reads, since the list gets long once you run several.
- Keep the authenticating Google account active and with access to the form. If access is lost, the connection stops.
Troubleshooting & FAQ
Section titled “Troubleshooting & FAQ”The Google sign-in does not complete. Confirm the account you chose has access to the form, then try again.
The form is not listed. The authenticated Google account cannot see it. Check the form is shared with that account, then reconnect.
Test Connection shows no responses. Usually the form has none yet. Submit a test response and try again.
Fields no longer match the destination. The questions on the form changed. Re-check the mapping on the destination connector.
Responses stopped arriving. Check the form is still accepting responses and that the authenticating account still has access to it.