Overview
Section titled “Overview”Each lead Signals receives is delivered to an inbox you nominate, as a message. It is the destination for teams whose follow-up starts in an inbox rather than in a system: a sales desk that works from email, a branch manager with no CRM login, an agency mailbox that routes enquiries onward.
Nothing is delivered to a platform API here, so there is no matching and no measurement. The work is delivery and speed.
An inbox is a poor system of record, so where the lead also needs to persist and be searchable later, run a spreadsheet, database or file destination alongside this one.
Supported sources
Section titled “Supported sources”Sources supported by Email
| Category | Supported |
|---|---|
| Lead generation |
Prerequisites
Section titled “Prerequisites”No account or credential is needed on this destination. You need a lead generation source already connected in the same project, because the connection is built on top of it.
Authentication
Section titled “Authentication”In Studio, open Destinations, find the Files category, and click the Email tile. There is nothing to authenticate. Signals sends from its own infrastructure, so no mailbox credentials, app password or SMTP details are needed.
The consequence is that nothing about the recipient is verified at setup. An address with a typo in it is accepted and fails quietly on the first delivery, so paste the address rather than typing it.
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.
Delivery settings
Section titled “Delivery settings”Set the Export frequency, which can be Real-time, 1 hour, 3 hours or 1 day, and enter the Email address the leads should be sent to. A shared mailbox or distribution list is safer here than a named individual, because aliases outlast employees.
Test connection
Section titled “Test connection”Click Test Connection before finishing. It validates the setup by sending a sample record, so you can confirm the address is right and see what the message looks like before real leads start arriving. Then click Finish.
Manage instance
Section titled “Manage instance”One connection delivers one source to one recipient. To deliver to a second recipient, or from a second source, add another instance from Manage Connections. To change an existing one, click the connection name in Manage Connections, click the edit icon in the top right, update the values, click Test Connection and click Finish. Clicking Cancel leaves the previous configuration running; updates apply only on Finish.
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.
Once a message leaves, the copy in the inbox is yours to govern. Retention, forwarding and deletion are decided by your mail system, not by Signals. Email is the least contained destination available, so send only to recipients who need the leads.
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”Use Test Connection during setup and confirm the sample arrives. Check which folder it lands in as well as whether it lands at all, because a first message from an unfamiliar sender often sits in Junk or in a gateway quarantine.
After go-live, expect delivery on the frequency you set. Real-time means within moments of the form being submitted. There is no match quality to measure here; what stands in for it is deliverability, meaning the mail arrives, lands in the inbox rather than spam, and is readable on a phone.
Best practices
Section titled “Best practices”- Send to a shared mailbox or distribution list rather than a named person, so the connection survives someone leaving.
- Ask your mail administrator to allowlist the Datahash sending domain before go-live rather than after the first messages disappear into quarantine.
- Pair this destination with a spreadsheet, database or file destination if the lead needs to persist. Nothing here is a system of record.
- Review the recipient when teams change. Nothing on the connection tells you a mailbox has stopped being read.
Troubleshooting & FAQ
Section titled “Troubleshooting & FAQ”Nothing arrives. Check spam and any gateway quarantine first. Then confirm the address is correct and that the source has produced leads since the connection was created.
Messages land in spam. Ask your mail administrator to allowlist the Datahash sending domain.
Some recipients receive them and others do not. The recipients are on different mail systems with different filtering. Check quarantine on the domain that is missing them.
Duplicate messages. Either the source is re-presenting the same lead, or two connections are delivering to the same recipient. Check Manage Connections first.
Fields are missing from the message. The lead form does not capture them. There is no field selection on this destination.
Can I stop delivery without losing the setup? Pause the connection from Manage Connections rather than deleting it.