Lead source on the record

The source stored on the lead

The source is the campaign, the referral, or the answer engine that started the visit, stored on the lead. A later visit does not erase it.

ChatGPT or Perplexity is kept when the visit started there. The same comparison applies as for a campaign.

The source stored on the lead is the place the visit began. A campaign name, a referral, or an answer engine can be that place. The field holds the one that started the visit, and it stays with the lead after the form is submitted.

A later visit can arrive from a different campaign. The source already stored is the one that started the first visit. That later arrival leaves the stored field as it was. The lead keeps the start.

ChatGPT is kept when the visit started in ChatGPT. Perplexity is kept when the visit started in Perplexity. Each one is stored the same way a campaign is stored. Score by source uses that stored field, and the comparison is the same one used for a campaign.

A referral is kept the same way. The lead shows the referral that started the visit. A person can group leads by that field and read the score beside each one. The grouping uses the source. The score on each lead stays the score already marked.

The form already on the site carries the campaign and the referral through to the lead. The source is attached to the record a person opens in the workspace. The field is on the lead itself, so the record still shows the start after the form has been submitted.

The first reply is a different record. It is one message, signed as the customer, sent from the customer's domain, and limited to approved knowledge. The source on the lead does not choose the words in that message. Keeping the source leaves the message unsent.

An answer engine is kept when the visit started there. A visit that started on a campaign stays a campaign. The field records the start the visit actually had. It does not add a source the visit never used.

The same lead can later be opened, scored, and answered. The source field remains the campaign, the referral, or the answer engine from the start. ChatGPT stays ChatGPT on that lead when that is where the visit began. Perplexity stays Perplexity on the same terms.

What the source is not

The source is not the score. The score is 0 to 100 with the reasons. You can compare that score by source. The source field does not calculate it.

The source is not a substitute made of the last click alone. Last click does not replace the source on the lead.

The score is a number from 0 to 100. The reasons sit beside it on the lead. Comparing that score by source means reading the number next to the source field. The source field holds the start of the visit. The number is produced elsewhere on the same lead.

A score of 80 or above raises an alert by email and to the workspace's chat. The alert tells a person to look. The source field does not raise that alert. The score does not write the campaign, the referral, or the answer engine into its own number.

Last click is the latest click before the form. The source is the campaign, the referral, or the answer engine that started the visit. When the latest click and the start differ, the lead keeps the start. The source field remains the start.

Both notes can sit on the lead at once, so a person can compare score by source. The comparison reads the two fields. The source field holds the start. It does not run the sum that produced the score.

The reasons on the score explain the mark. A reason can name how complete the form is, or whether the contact looks real. A reason stays with the number. It does not become the campaign, and it does not become Perplexity.

The source view groups leads by the stored source. Inside a group, the scores can be read together, each with its reasons. The group name is the source. The numbers in the group remain scores. Naming the group does not calculate them.

A last click can be a useful trace of the latest step. The record this page keeps is still the source on the lead. Replacing that field with the latest click would drop the campaign, the referral, or the answer engine that started the visit. The lead keeps that start.

Where the sample sits

The sample is a mortgage application with source ChatGPT. The reply on that page confirms the amount. This page only keeps where the visit started.

Attribution does not send the reply. Sending is a separate step.

The sample lead is Olivia Bennett. The amount on the form is £240k. The source stored on that lead is ChatGPT, because the visit started there. The score on that same record is 92. This page keeps the source. The mortgage page is where the reply confirms the amount.

The reply on the mortgage application is the first reply. It is signed as the customer, sent from the customer's domain, and limited to approved knowledge. It confirms the amount the person entered. That confirmation lives on the mortgage page. This page stores where the visit started.

Attribution records the source on the lead. The reply waits for its own step. A stored source of ChatGPT does not dispatch the message. The customer's domain still has to be verified, and the message still has to stay inside approved knowledge.

A new form starts in approval. The reply stays pending until a person in the workspace sends it, or until the workspace has accepted responsibility for those messages. The source field is already on the lead while that reply is still unsent.

The sample source is ChatGPT because the visit started in ChatGPT. The same rule would keep Perplexity if the visit had started in Perplexity. On this record the stored source is ChatGPT. The amount, and the reply that confirms it, belong to the mortgage application.

Score 92 sits beside the source on Olivia Bennett's record. The source field did not calculate 92. The reply that confirms the £240k amount is described on the mortgage page. This page does not time that send.

Sending remains the later step. The lead can show ChatGPT as the source, £240k as the amount, and 92 as the score, and still have no message gone out. Attribution has finished its job when the source is on the lead. The first reply has its own send.

How this differs from the published times

The source says where the visit started. The published response times are a separate note, speed to lead.

Score 92 on the sample is one record. It is not a benchmark for every source, and this page does not add a reply time to it.

The reason to open that page is 42 hours, and the source and the published times are different notes.

The source names the campaign, the referral, or the answer engine. The published times name how long a first reply took in the figures gathered for that page. A lead can show ChatGPT as the source while those figures stay on their own page.

Score 92 belongs to the sample mortgage record. It describes Olivia Bennett's £240k request. A campaign, a referral, or Perplexity does not inherit that score. A reply time is not stored in the source field.

The first reply remains one message from the customer's domain, limited to approved knowledge. The published times do not send that message. The source does not send it either. Sending stays a separate step from the note that says where the visit started.

A person opens the speed to lead page to read the published times. They open the lead to read the source. The two pages answer two questions. Where the visit started is the question this page answers.

The sample record can be read as two notes side by side: source ChatGPT, and score 92. The source is the note this page keeps. The score is explained with its reasons on its own page. The published times stay on theirs.

ChatGPT or Perplexity on the lead means the visit started there. It does not mean the published times have been copied onto that lead. The comparison of score by source still uses the stored field. The published times remain the other note.