Route leads by device/browser signal (mobile app lead vs web lead) to specialized team
One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.
Professional
Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Marketing Hub Professional.
OutcomeA lead captured through the mobile app reaches the team trained on the app experience, and a web-form lead reaches the standard web team, instead of both going through one generic queue that treats the two channels the same.
Workflow maplead-routing-045
One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.
When to use it, when not to
Use it
Use it when mobile app leads and web leads genuinely need different
follow-up (different product context, a different onboarding flow,...or a
team specifically trained on the app).
Use it when the mobile app and the website use separate, distinct
HubSpot forms or a distinct integration path, so the channel is knowable
at intake without guessing from a browser string.
Read more on when to use itShow less
Skip it
Do not use it if a single form serves both channels identically
embedded in the app's webview and the website;...there is no reliable
signal to branch on in that case, fix the intake separation first.
Do not use it expecting a native "device type" contact property; standard analytics device data exists at the page-view and session
level, not as a persistent contact property.