Leads
Update Lead Status
Update a lead’s status and queue it for conversion processing.
POST
Updates a lead’s status by assigning it a conversion label. The lead is then queued for processing, which sends the conversion to your connected ad platforms (Google Ads, Meta, etc.).
When
When
Identifying a lead
You can identify the lead to update using any one of the following fields. At least one is required. If multiple are provided, the following priority order is used:leadIduniqueIdentifieremailphone
Request body
number
The numeric ID of the lead to update.
string
Look up the lead by email address.
string
Look up the lead by phone number.
string
Look up the lead by its user-provided unique identifier (e.g. your CRM lead ID).
string
required
The conversion label to apply. Use a conversion label ID (UUID) from your project’s conversion labels, or one of the special values:
"open"— reset the lead to open status (no job is queued)"lost"— mark the lead as lost (queued for processing)
conversionId. For more details on setting up conversion labels, see the Conversion Labels guide.number
Lead value in cents (e.g.
5000 for $50.00). Must be a non-negative number. If provided, the lead’s price is updated before processing.At least one lead identifier (
leadId, email, phone, or uniqueIdentifier) is required. The leadId field is no longer the only way to identify a lead.Response
The response varies depending on theconversionId value. All responses include uniqueIdentifier alongside leadId.
When conversionId is "open"
string
"Lead status updated to open".number
The ID of the updated lead.
string | null
The unique identifier for the lead, or
null if not set.string
"open".boolean
false — no job is queued for open status.When conversionId is a conversion label or "lost"
string
"Lead queued for processing".number
The ID of the updated lead.
string | null
The unique identifier for the lead, or
null if not set.string
"pending".boolean
true.object[]
Array of validation warnings indicating integrations that will be skipped due to missing data. Each warning contains:
Error: duplicate job (409)
If the lead already has a pending job in the processing queue, a409 Conflict is returned.