Integrations and Lead Widget Embedding
Connect Google Business Profile signals and embed Tradie Card lead widgets on approved external domains.
Guide Outcome
This guide covers integration controls for trust visibility and embedded capture, while keeping domain security and public safety boundaries intact.
- • Google Business Profile trust signals are connected and managed.
- • Widget is embedded with controlled host permissions.
- • External lead capture still lands in the same Leads workflow.
Step-by-Step Workflow
Step 1
Connect Google Business Profile
Use Integrations to connect and manage review-related business location details.
- • Connection status is visible in Integrations.
- • Linked location details match your real business listing.
- • Review visibility preference is configured appropriately.
Step 2
Enable and configure widget
Turn on widget access in Widgets and set approved host patterns before embedding on external pages.
- • Widget enabled state is correct.
- • Allowed domains include every intended host.
- • Layout and source path metadata are validated on test page.
Step 3
Deploy script snippet
Install the widget script and slug configuration on your external site so enquiries route back to Tradie Card.
- • Script loads over HTTPS.
- • Slug and rendered iframe target the intended card.
- • Widget renders without domain-block errors.
Step 4
Verify end-to-end lead capture
Submit a test enquiry and confirm it appears in Leads with widget source context fields.
- • Test lead arrives in Leads.
- • Widget source metadata is present.
- • Response workflow works the same as card-origin leads.
Feature Reference
Google Business Profile Integration
Connect once, then control review presentation from dashboard settings.
- • Location mapping and refresh status are exposed in Integrations.
- • Review visibility can be enabled or paused per business state.
- • Reverification states are surfaced when required.
Widget Security Model
Widget embeds use host validation and explicit allowlist patterns.
- • Unknown domains can be blocked from rendering widget capture.
- • Widget availability state can be switched off by business owner.
- • Embed routes are configured for non-indexed operational rendering.
Unified Inbox Outcome
External site leads still run through one operational inbox.
- • Widget submissions flow to Leads with the same status model.
- • Communication and assignment workflows remain identical.
- • Analytics can separate widget-origin and card-origin volume.
Safety and Public Scope
Public docs describe product behavior and user workflows only.
Internal infrastructure, private APIs, credentials, and secret operations are intentionally excluded.
Sensitive and private tracking routes are configured no-index where applicable.
All feature descriptions in this docs cluster are tied to production code paths and current UI behavior.
Related Guides
Public Card, Trust Signals, and Publishing
Configure your public Tradie Card for local discovery, direct enquiries, and trust-first conversion.
Open related guideAnalytics, Queues, and Operational Optimisation
Track lead flow, response performance, document outcomes, and action queues to improve conversion consistency.
Open related guideApply This Guide in Your Workspace
Use this workflow directly in your dashboard, then continue with the next guide to complete your full lead-to-job operating system.
