To relate contacts and their behavioral data and transform this information into meaningful insights, you set scoring rules that define a contact’s score, lead type, and lead stage.
Each lead scoring type is characterized by a score of points that capture the lead’s readiness to convert to different conversions you defined. You specify a lead’s readiness using engagement stages of each lead scoring type. For example, you can define stages “Leads” between 50 and 100 points and “Qualified Leads” above 100 points. Contacts pass a stage once they reach the stage threshold.
NOTE: Since the “Qualified leads” stage is closer to conversion than the “Leads” stage, the threshold for the former needs to be higher than the threshold for the latter.
Scoring rules are based on user activities, or interactions, on your website. When a contact views a page, downloads a document, posts comments, or subscribes to an email campaign, or any other interaction you define, the contact earns a specific number of points for each of these activities. Each interaction, or combination of interactions, is encapsulated by a lead scoring rule.
Depending on how you define leads coring rules, a contact may score points for a rule just once or each time they complete a specific interaction. For example, your scoring rule states that each time a contact visits a page under the Pricing section, they score points for the Buyers scoring type. Thus, you can measure the frequency of visits by this contact to buying and pricing information and, based on the contact's score, associate this frequency with lead scoring stages. The higher score a contact scores towards this type, the closer stage to conversion, and therefore, purchase, they are associated to.
The bigger score contacts accumulate within a certain lead scoring type, the closer they are to conversion, that is, the higher engagement stage of the lead scoring type they reach. The higher the score value, the more qualified the lead is.
Rules are not bound to one lead scoring type and can be scored against any type with different values (anything different from zero is considered), depending on your requirements.
Back To Top
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.