Outcome. A lead captured through a Facebook or LinkedIn native lead ad form reaches the right rep queue for the product or campaign it came from, instead of sitting in a generic ads bucket.
flowchart TD
A[Lead ad form submitted] --> B{Campaign maps to which product?}
B -->|Product A| C[Rotate to Product A reps]
B -->|Product B| D[Rotate to Product B reps]
B -->|unmapped| E[Rotate to General paid-ads pool + notify ops]
C --> F[Set routed date, notify, create call task]
D --> F
E --> F

When to use it, when not to
- UseUse it when the Facebook Lead Ads and/or LinkedIn Lead Gen Forms integration is connected and mapped to HubSpot forms.
- UseUse it when different ad campaigns represent different product lines or offers that should route to different specialist reps.
- SkipDo not use it if all paid-ads leads go to the same generalist pool regardless of campaign; a plain rotation (lead-routing-002) is simpler.
- SkipDo not use it as your only lead-quality gate. Native lead ad forms pre-fill from the platform's own profile data with no validation, pair this with a data-quality check, see Known pitfalls.
or the lead routing pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.





