Leadtrak.ai documentation

Getting started

• Create your account
• Build your first funnel in ten minutes
• Publish to your own domain
• Invite your team — unlimited users
• Understanding the 30-day Growth trial

Building funnels

• Question types and one-question-per-screen layout
• Per-answer scoring weights
• Conditional branching and skip logic
• Starting from a sector template
• Theming, logos and colour
• Mobile preview and load-speed checks

Lead capture & validation

• How leads are written before processing
• Email and phone validation rules
• Deduplicating repeat enquiries
• Setting your qualification threshold
• Lead inbox, filters and CSV export

Tracking & attribution

• Installing the tracking pixel (it ships with the builder)
• UTM parameters and source mapping
• Recording ad spend by channel
• Reading cost per qualified lead
• The visitor journey on the lead page, and choosing between the four attribution models
• Attribution limits and how to allow for them

Follow-up, routing & support

• Email follow-up sequences and enrolment
• Routing rules — notifying the right person by score or answer
• Reading the lead record: answers, score breakdown, history
• Raising and tracking a support ticket

Integrations & API planned

• Getting leads in over the HTTP capture endpoint (built)
• CSV export of leads (built)
• Sending transactional email through our mailer — POST /api/v1/email/send, shared-key auth, HTML and plain text, base64 attachments, rate limited per minute, and only from sending domains we have configured (built — single shared key, not yet per-tenant API keys)
• Branded email templates — pass "template": "welcome" instead of writing HTML and the email is rendered in the colours, logo text and footer of the sending domain, with a plain-text alternative derived automatically (built)
• Outbound webhooks — a signed JSON POST to your own URL on lead.created, lead.status_changed, lead.qualified, lead.won and lead.lost, HMAC-SHA256 over the raw body, five retries with backoff, a replayable delivery log and auto-disable after ten consecutive failures (built)
• Public REST API with per-tenant keys and rate limits (planned)
• Zapier, Make and CRM connectors (planned)

Full detail on the email sending API and the branded templates →

Billing & plans planned

• No billing system is implemented yet — published prices state the intended commercial model
• Plans, prices and what will count as a lead (planned)
• Invoices, VAT and receipts (planned)
• Exporting your data (built — CSV export)