Skip to content

How Convertly CRM Works

Convertly is a lead-centered CRM. A lead remains the main record throughout the sales process; there is no separate opportunity record that must be created later.

Lead enters Convertly
-> source and campaign context are stored
-> ownership and lead defaults are applied
-> tasks, follow-ups, and notes record sales work
-> stage and value reflect the current opportunity
-> configured advertising events are queued
-> analytics summarizes the result
  • Native embedded forms
  • Meta instant forms through Meta Lead Sync
  • Inbound Leads API
  • Universal Webhook Mapper
  • CSV import
  • Manual creation

Each source can apply defaults such as stage, source, categories, owner, value, custom fields, and selected new-lead alert recipients. Available defaults depend on the intake method.

A lead record can contain contact details, source, campaign context, value, categories, notes, timeline events, tasks, follow-ups, and AI results. Keeping these items together makes handoffs easier to review.

Automations run when supported lead events occur, such as lead creation, assignment, stage change, source change, or form submission. Scheduled reminders and overdue digests are handled by the notification system instead of the automation builder.

Google Ads and Meta CAPI use mappings configured in Settings -> Ads. The event sent depends on the configured mapping and the identifiers available on the lead. Meta Lead Sync is a separate inbound workflow for importing Meta form submissions.

Analytics uses the selected date range and your access scope. Performance Explorer supports multiple cards, previous-period comparison, and breakdowns by time, source, stage, owner, or lead category. Revenue Intelligence uses the value stored on leads.

Every workspace is organization-scoped. Access within the organization also depends on role: Admin, Manager, and Sales work across organization records, while Staff has an assignment-focused view.