- Use cases
Lead generation
A lead sitting in an ad platform is not a lead anyone is working. Lead generation moves form submissions out of the platform and into the system your team actually uses, so follow up starts while the person still remembers filling in the form.
This is the opposite direction from Lead and CRM conversions, which sends qualification outcomes back to the platform.
Sources and destinations
Section titled “Sources and destinations”The ad platform is the source here and your own system is the destination. There is no Integration Type step, and all five sources feed all of the destinations below.
Supported sources
| Category | Supported |
|---|---|
| Lead generation |
Supported destinations
| Category | Supported |
|---|---|
| CRM | |
| Files & delivery |
How submissions arrive
Section titled “How submissions arrive”Signals pulls your lead forms frequently, so a submission reaches your CRM without anyone exporting anything. Lead response time drives conversion more than almost anything else you control downstream, and the value of routing leads automatically is that it removes the delay between submission and first contact.
Mapping
Section titled “Mapping”Platform lead forms have their own field names, and they will not match your CRM. Map them on Field Mapping before going live, and include the platform lead ID. That identifier is what lets you send qualification outcomes back later through Lead and CRM conversions.
Studio filters each dropdown to columns whose data type is eligible, so a missing option usually means a type mismatch rather than a missing field.

