The lead record
What this page is — the full record for one lead: identity, ownership, qualification, custom fields, consent, and its whole history of activity.
What it is for — working a single lead. Everything known about the person, on one screen, editable in place.
The problem it solves — this is where the actual selling work is recorded, so it is where most questions land: which picker gets its values from where, why the score reads 0, and why the grade chip and the grade field can disagree with each other in the same panel.
Route: /org/marketing/leads/{id} · Permission to view: View Marketing Suites lead management
Permission to edit: Edit Existing Leads
The detail route is gated on .view, not .edit. Someone with view-only access can read the whole
record — they simply cannot change it.
1. The shape of the page
| Region | Holds |
|---|---|
| Header | Name, job title, company, lifecycle stage, pipeline, current status, Convert |
| Stepper | Every status of the pipeline, with the current one marked |
| Left column | Contact Info · Ownership · Tags · Consent |
| Centre | Activity Log · Comments · Emails · Calls |
| Right column | Qualification · Custom Fields · Marketing |
2. Editing in place
There is no edit mode and no page-level Save. Click a value, change it, and it is written.
Select timezone, Select language, e.g. Web Form and similar greyed italics are prompts for empty
fields. A field showing one holds nothing.
Where each picker's values come from
| Field | Values from | If empty |
|---|---|---|
| Source | The active lead sources | No sources configured |
| Pipeline | Pipelines scoped to this project or organisation-wide | None configured |
| Status | Statuses of the chosen pipeline | That pipeline has no statuses |
| Owner | Users enabled as agents | No agents enabled |
| Grade | The configured grades | No grades configured |
| Lifecycle stage | The five fixed values | — |
| Currency | A fixed list of seven — USD, EUR, GBP, AUD, CAD, INR, JPY | — |
3. Qualification — and its internal contradiction
The chip next to the dial is computed from the score. The Lead Grade field below it is the value stored on the lead. They disagree whenever a grade has been set by hand.
The leads list shows only the computed one. Full explanation in status, grade and score.
Scoring does not run when a lead is created or updated. Assignment does. A score of 0 on a new lead is normal, not a misconfiguration.
4. Custom fields
The panel lists fields that hold a value, and offers an adder for the definitions that do not. Field types come from the definition: text, textarea, number, date, boolean, url, select and multi-select.
An integration sending custom_fields as text containing JSON is rejected with a clear error, so the
values either appear here or the request fails. See
the webhook reference.
The Marketing card — Source channel and Campaign
Directly below Custom Fields, the Marketing card says where the lead came from.
The grey block at the top, marked 1, is a read-only summary.
| Value | Reads |
|---|---|
| Source channel | The channel the lead arrived through, for example facebook (social) |
| Campaign | The campaign tag of the link they used, for example diwali-offer |
Both read Direct / unknown when the lead arrived without campaign tags.
Under the summary are the fields it is built from — Landing Page, Campaign (UTM), UTM Source, Medium, Term and Content — each edited in place like the rest of the record. The Source picker above them is the lead's configured lead source and is a separate thing.
A lead created by a form submission receives these values from the visitor's tagged link. A lead that already existed keeps the values it had. The full rules are in How campaign tracking works.
5. Engagement
Four centre tabs, covered in activities, notes and calls.
Changing a field adds a Lead Updated entry describing the change. A record that has been edited
several times has a timeline that is partly an audit log.
6. Consent
| Flag | Column |
|---|---|
| Email Marketing | consent_email |
| SMS Messages | consent_sms |
consent_whatsapp | |
| Consent Source | consent_source — free text |
consent_timestamp is stamped server-side the moment any flag arrives, and the API deliberately does
not accept it from a caller — a compliance record must not depend on the client's clock.
7. Convert
The Convert button turns the lead into a contact, a deal, or both.
What it writes:
| Ticked | Result |
|---|---|
| Create contact | A contact, lifecycle stage customer — or opportunity if a deal is also created |
| Create deal | A deal in the chosen pipeline and stage, linked to the contact |
| Both | Contact, then deal, then the lead is marked converted and linked to both |
Conversion looks up the email first. If a contact exists in the project it is linked rather than recreated — so converting twice does not create two contacts.
8. Don't confuse this with…
| This | Not this |
|---|---|
| The grade chip | The Lead Grade field |
| Status on the stepper | Lifecycle stage in the header |
Comments tab | Activity Log tab — comments are notes, activities are logged events |
| Convert on the record | Conversion rules, which do it automatically |
| Source channel on the Marketing card | The Source picker — a configured lead source, not a campaign tag. See campaign tracking |
9. Troubleshooting
| Symptom | Cause |
|---|---|
| A picker is empty | Its configuration table has no active rows. Section 2 |
| Score reads 0 | Expected — scoring runs only on Recalculate. Section 3 |
| Grade differs from the list | The list computes it. Section 3 |
| An integration's values never arrive | Its request is being rejected — check for the custom_fields error. Section 4 |
The timeline is full of Lead Updated entries | Field edits write activity rows. Section 5 |
| Saving moved the lead to another pipeline | Its pipeline belonged to another project. See the board |
| Source channel reads Direct / unknown | The lead arrived without campaign tags, or it existed before its tagged submission. See campaign tracking |