# Generic Lead Scoring Model
## About
`glsm` is a user-friendly Python package that simplifies the process of building lead scoring models. It supports both predictive and non-predictive models, providing flexibility and ease of use.
The goal of the lead score is to provide a qualification metric for comparison between leads. It is based on product interest and company interaction data.
### Predictive Model
Soon!
### Non-predictive Model
| Name | Description | Variable|
|-------------------|-------------------|-------------------|
| Weight| Feature weight that represents the relative importance of each feature | $$w$$ |
| Points| Assigned points of each feature | $$p$$ |
| Normalized weight | Weights unit vector normalization | $${\hat{w}} = \frac{w}{\sqrt{\sum\limits^{n}_{i=0}w_i^2}}$$ |
| Lead score | A weighted sum of assigned points for each feature, where the feature weights are normalized to form a unit vector. | $$\lambda = \sum_{i=1}^n {\hat{w}_i^2}{p_i}$$ |
---
## Index
1. [About](#about)
1. [Predictive Model](#predictive)
2. [Non-predictive Model](#non-predictive)
2. [Disclaimer](#disclaimer)
3. [Installation](#installation)
4. [Theory](#theory)
1. [Predictive Model](#predictive-model)
2. [Non-predictive Model](#non-predictive-model)
1. [Weight:](#weight-w)
2. [Normalized Weight:](#normalized-weight-hatw)
1. [Unit vector normalization:](#unit-vector-normalization)
2. [Feature weights vector magnitude:](#feature-weights-vector-magnitude)
3. [Normalized weight vector:](#normalized-weight-vector)
3. [Qualification threshold](#qualification-threshold)
4. [Points:](#points-p)
5. [Lead Score:](#lead-score-lambda)
6. [Features](#features)
5. [Usage](#usage)
1. [Predictive Model](#predictive-model-usage)
2. [Non-predictive Model](#non-predictive-model-usage)
1. [Importing the library](#importing-the-library)
2. [Instantiating the model and adding features](#instantiating-the-model-and-adding-features)
3. [Removing features](#removing-features)
4. [Calculating the lead score](#calculating-the-lead-score)
1. [From a dictionary](#from-a-dictionary)
2. [From a csv](#from-a-csv)
## Disclaimer
This library is in beta. Suggestions and contributions are welcome.
## Installation
### Requirements
- pydantic
- pandas
Can be installed using pip:
```bash
pip install glsm
```
---
# Theory
There are two ways for you to understand the proposed models:
1. Through the [Google Sheets simulator](https://docs.google.com/spreadsheets/d/1ESEtcjno36ZLW5XMEoHqLKHjiZMkrZeIECcrcgFxHzA/edit?usp=sharing) (Non-predictive only)
2. Reading the following sections
## Predictive
Soon!
---
## Non-predictive
This model and the following set of rules are a suggestion to get you started. You can use them as a starting point and adapt them to your business needs.
The library is flexible enough to allow you to use your own assumptions and rules.
The non-predictive model has the following characteristics:
1. It avoids the use of predictive algorithms, which can be data-intensive and require significant computational power and technical expertise to operate effectively.
2. It uses relative feature weights, meaning that the inclusion of a new feature won't change the weights of the existing ones. This can simplify the implementation and interpretation of the model.
3. It provides a score that ranges from 0 to 100 points, with 50 being the minimum threshold for lead qualification. The score reflects the current objectives and scenarios of the company, allowing for comparisons of lead performance over time.
### Weight (${w}$):
Feature weight is a value that multiplies the points assigned to each feature. It is used to differentiate the importance of each feature.
You can make it easier to understand by thinking of it as a multiplier. The higher the weight, the more important the feature is. You can use any range of values (due to the unit vector normalization), but it is easier to interpret if the weights are between 0 and 1.
Suppose you choose to use values from 0 to 1. Your most important feature will have a weight of 1. Other features should have a weight less than 1.
### Normalized Weight (${\hat{w}}$):
The model needs to be flexible and adaptable to accommodate changes in the business environment. Sometime after the model is built, the company may change its focus or process. In this case, features may need to be added or removed.
The normalized weight is a unit vector that is used to scale data in a way that preserves the relative relationships between the features when new features are added.
The basic idea is to transform the data such that the magnitude of the vector formed by the features is equal to 1. This ensures that each feature is scaled proportionally to the others, so the relative relationships between them is preserved when new features are added.
You may be asking yourself why not just recalculate the weights after adding or removing a feature?
Well, this may work if you have the original data and just want to make a report out of it, but once you calculate the lead score and send the conversion events to platforms such as Google Analytics, Facebook Ads, etc. The scores registered in those platforms can't be changed. Later on you may want to create audiences based on the lead score, but you won't be able to do that if the scoring model has changed. The normalized weight vector solves this problem.
<!-- #TODO rewrite this section -->
#### Unit vector normalization:
$$
\hat{w_n} = \frac{w_n}{|w|}
$$
#### Feature weights vector magnitude:
$$
|w| = \sqrt{\sum\limits^{n}_{i=0}w_i^2}
$$
#### Normalized weight vector:
$$
\hat{w_n} = \frac{w_n}{\sqrt{\sum\limits^{n}_{i=0}w_i^2}}
$$
In this way the sum of the squares of the normalized weights is equal to 1:
$$
\sum\limits^{n}_{i=0}{\hat{w}_i^2} = 1
$$
### Qualification threshold:
The qualification threshold is the value that determines whether a lead is qualified or not. It is calculated as the midpoint of the range of points assigned to each feature.
$$
\theta = \text{points range}_{max} - \frac{\text{points range}_{max} - \text{points range}_{min}}{2}
$$
If the lead score $\geq \theta$ then the lead is qualified.
Note that you can always change the qualification threshold to suit your needs. Since the default points range is 0 to 100, the default threshold is 50.
### Points ($p$):
Points assigned to each option of each feature. The points are assigned based on the desirability of each option. The points are then multiplied by the normalized weight of the feature to obtain the weighted points that are then summed to obtain the lead score.
> **NOTE:** The numbers below are only a suggestion. You can use any set of values. The important thing is to be consistent.
The proposed points assignment framework is as follows:
1. Order the options from least desirable to most desirable.
2. Determine the range of points for each feature: Define the minimum and maximum points for each feature. The minimum points should be assigned to the least desirable option, and the maximum points to the most desirable option. For instance, you could assign points on a scale of 0 to 100.
3. Determine if the feature is numeric or categorical.
- **If defining from numeric variables:**
Specify the target ranges that best represents the ICP.
For example, in a feature called "Monthly users", the ICP range could be "50k to 100k"
- **If defining from categorical variables:**
Identify the options that best represent the ICP. For example, in a feature called "Industry", the ICP options could be "Retail" and "Telecom".
4. Assign points to the ICP option: Assign the qualification threshold points (suppose 50 points in this case) to the ICP option(s).
5. Divide the remaining points range into equal intervals: For options less desirable than the ICP option, divide the range from the minimum points to the qualification threshold points (0 to 50) into equal intervals. For options more desirable than the ICP option, divide the range from the qualification threshold points to the maximum points (50 to 100) into equal intervals.
Suppose a feature A has 4 options: A1, A2, A3, A4. The ICP option is A2:
- For options less desirable than A2 (A1): Divide the range 0 to 50 into equal intervals (0 to 50, one interval of 50 points).
- For options more desirable than A2 (A3 and A4): Divide the range 50 to 100 into equal intervals (50 to 100, two intervals of 25 points each).
6. Assign points to the other options based on their position in the intervals: Assign points to each option based on the position of that option within the equal intervals.
- A1: 0 points (minimum)
- A2: 50 points (ICP option)
- A3: 75 points
- A4: 100 points (maximum)
If none of the options seem to be a good fit for assigning 0 points, you can introduce a new baseline option that represents the least desirable criteria. This baseline option will be assigned 0 points, and the other options will be assigned points accordingly.
The options for feature A would now be: A0, A1, A2, A3, and A4, with A0 being the new baseline option. The points assignment will now follow the same steps as before, but with A0 receiving 0 points:
- A0: 0 points (minimum)
- A1: 25 points
- A2: 50 points (ICP option)
- A3: 75 points
- A4: 100 points (maximum)
Use your best judgement and domain knowledge or historical data that suggests a certain lead score is more indicative of a qualified lead to determine the target ranges and how many options to include before and after the ICP options.
Note that more than one ICP option can be defined for each feature as seen below:
| Industry | Points | Calculation |
| -------------- | ------ | ----------------------- |
| Other | 0 | 50 - (50/5)*5 |
| Agriculture | 10 | 50 - (50/5)*4 |
| Transportation | 20 | 50 - (50/5)*3 |
| Healthcare | 30 | 50 - (50/5)*2 |
| Manufacturing | 40 | 50 - (50/5) |
| Education | 50 | qualification_threshold |
| Finance | 50 | qualification_threshold |
| Technology | 50 | qualification_threshold |
| Retail | 75 | 50 + 50/2 |
| Telecom | 100 | 50 + (50/2)*2 |
### Lead Score ($\lambda$):
Lead score is the sum of squares the normalized weights of each feature multiplied by the points assigned to each feature.
$$
\lambda = \sum_{i=1}^n {\hat{w}_i^2}{p_i} = ({\hat{w}_1^2}{p_1})+({\hat{w}_2^2}{p_2})+({\hat{w}_3^2}{p_3})...({\hat{w}_n^2}{p_n})
$$
The higher the lead score, the more desirable the lead is. The lead score is then compared to the qualification threshold to determine if the lead is qualified or not.
Lead score can be used to rank and prioritize leads, and to create audiences based on the lead score on platforms such as Google Analytics, Facebook Ads, etc.
### Features
Features are a set of characteristics assigned to each lead. If you have difficulties finding out which features to add, start by adding relevant lead form or CRM fields as features.
Each feature has points associated with it, which are assigned to each option of the feature. The points assigned to each option are relative to the qualification threshold. The higher the points, the more desirable the option.
Each feature has a weight associated with it, which is used to differentiate the importance of each feature. The higher the weight, the more important the feature is.
A feature have several options, each of which represent a range of values. For example, the feature "Monthly Website Users" has the following options:
| Monthly Website Users | Points |
| --------------------- | -------- |
| Up to 50k | 0 |
| 50k - 100k | 50 (ICP) |
| 100k - 200k | 75 |
| More than 200k | 100 |
You should first define the features and their options, then assign 50 points to the minimum viable option for the lead to be considered qualified. The remaining points should be distributed among the other options in a way that reflects the relative importance of each option.
Remember that this is a suggestion, you can assign the points as you see fit and as your business requires. You may want to use negative points to penalize leads that do not meet certain criteria for example. It is generally easier to work with positive points, but it is up to you.
# Usage
## Predictive Model usage
Soon!
## Non-predictive Model usage
In the examples folder you can find a Jupyter Notebook with a step-by-step guide on how to use the library.
You may also want to check the [Google Sheets simulator](https://docs.google.com/spreadsheets/d/1ESEtcjno36ZLW5XMEoHqLKHjiZMkrZeIECcrcgFxHzA/edit?usp=sharing) (Non-predictive only)
### Importing the library
```python
from glsm.non_predictive.model import NonPredictive
from glsm.non_predictive.features import Feature
```
### Instantiating the model and adding features
```python
model = NonPredictive()
feature_a = Feature(
name="Monthly Users",
weight=0.5,
options_df=pd.DataFrame([
{"label": "Up to 50k", "is_ICP": False},
{"label": "50k - 100k", "is_ICP": True},
{"label": "100k - 200k", "is_ICP": False},
{"label": "More than 200k", "is_ICP": False},
])
)
feature_b = Feature(
name="Industry",
weight=0.25,
options_df=pd.DataFrame([
{"label": "Other", "is_ICP": False},
{"label": "Agriculture", "is_ICP": False},
{"label": "Transportation", "is_ICP": False},
{"label": "Healthcare", "is_ICP": False},
{"label": "Manufacturing", "is_ICP": False},
{"label": "Education", "is_ICP": True},
{"label": "Finance", "is_ICP": True},
{"label": "Technology", "is_ICP": True},
{"label": "Retail", "is_ICP": False},
{"label": "Telecom", "is_ICP": False},
])
)
model.add_features([feature_a, feature_b])
```
### Removing features
```python
model.remove_features(['Industry'], ['Monthly Users'])
```
### Calculating the lead score
#### From a dictionary
```python
lead = {
"Monthly Users": "50K - 100K",
"Industry": "Technology",
"Mkt Investment": "$300K - $400K",
}
lambda_value = model.compute_lambda(lead)
```
#### From a csv
Check out the leads.csv file in the examples folder.
```python
df = pd.read_csv('leads.csv')
df['lambda'] = df.apply(
lambda row: model.compute_lambda(row.to_dict()),
axis=1
)
```
Raw data
{
"_id": null,
"home_page": "",
"name": "glsm",
"maintainer": "",
"docs_url": null,
"requires_python": "",
"maintainer_email": "",
"keywords": "python,lead score,modeling,lead generation,lead scoring,lead scoring model",
"author": "Victor Valar",
"author_email": "<valar@victorvalar.me>",
"download_url": "https://files.pythonhosted.org/packages/47/f3/5907d6afdfcccd496f8f6647afbbc9a2a230df65c0348f0a7e1b4d4defea/glsm-0.1.3.tar.gz",
"platform": null,
"description": "\n# Generic Lead Scoring Model\n\n## About\n\n`glsm` is a user-friendly Python package that simplifies the process of building lead scoring models. It supports both predictive and non-predictive models, providing flexibility and ease of use.\n\nThe goal of the lead score is to provide a qualification metric for comparison between leads. It is based on product interest and company interaction data.\n\n### Predictive Model\n\nSoon!\n\n### Non-predictive Model\n\n\n| Name | Description | Variable|\n|-------------------|-------------------|-------------------|\n| Weight| Feature weight that represents the relative importance of each feature | $$w$$ |\n| Points| Assigned points of each feature | $$p$$ |\n| Normalized weight | Weights unit vector normalization | $${\\hat{w}} = \\frac{w}{\\sqrt{\\sum\\limits^{n}_{i=0}w_i^2}}$$ |\n| Lead score | A weighted sum of assigned points for each feature, where the feature weights are normalized to form a unit vector. | $$\\lambda = \\sum_{i=1}^n {\\hat{w}_i^2}{p_i}$$ |\n\n---\n\n## Index\n\n1. [About](#about)\n 1. [Predictive Model](#predictive)\n 2. [Non-predictive Model](#non-predictive)\n2. [Disclaimer](#disclaimer)\n3. [Installation](#installation)\n4. [Theory](#theory)\n 1. [Predictive Model](#predictive-model)\n 2. [Non-predictive Model](#non-predictive-model)\n 1. [Weight:](#weight-w)\n 2. [Normalized Weight:](#normalized-weight-hatw)\n 1. [Unit vector normalization:](#unit-vector-normalization)\n 2. [Feature weights vector magnitude:](#feature-weights-vector-magnitude)\n 3. [Normalized weight vector:](#normalized-weight-vector)\n 3. [Qualification threshold](#qualification-threshold)\n 4. [Points:](#points-p)\n 5. [Lead Score:](#lead-score-lambda)\n 6. [Features](#features)\n5. [Usage](#usage)\n 1. [Predictive Model](#predictive-model-usage)\n 2. [Non-predictive Model](#non-predictive-model-usage)\n 1. [Importing the library](#importing-the-library)\n 2. [Instantiating the model and adding features](#instantiating-the-model-and-adding-features)\n 3. [Removing features](#removing-features)\n 4. [Calculating the lead score](#calculating-the-lead-score)\n 1. [From a dictionary](#from-a-dictionary)\n 2. [From a csv](#from-a-csv)\n\n## Disclaimer\n\nThis library is in beta. Suggestions and contributions are welcome.\n\n## Installation\n\n### Requirements\n\n- pydantic\n- pandas\n\nCan be installed using pip:\n\n```bash\npip install glsm\n```\n\n---\n\n# Theory\n\nThere are two ways for you to understand the proposed models:\n\n1. Through the [Google Sheets simulator](https://docs.google.com/spreadsheets/d/1ESEtcjno36ZLW5XMEoHqLKHjiZMkrZeIECcrcgFxHzA/edit?usp=sharing) (Non-predictive only)\n2. Reading the following sections\n\n## Predictive\n\nSoon!\n\n---\n\n## Non-predictive\n\nThis model and the following set of rules are a suggestion to get you started. You can use them as a starting point and adapt them to your business needs.\nThe library is flexible enough to allow you to use your own assumptions and rules.\n\nThe non-predictive model has the following characteristics:\n\n1. It avoids the use of predictive algorithms, which can be data-intensive and require significant computational power and technical expertise to operate effectively.\n2. It uses relative feature weights, meaning that the inclusion of a new feature won't change the weights of the existing ones. This can simplify the implementation and interpretation of the model.\n3. It provides a score that ranges from 0 to 100 points, with 50 being the minimum threshold for lead qualification. The score reflects the current objectives and scenarios of the company, allowing for comparisons of lead performance over time.\n\n### Weight (${w}$):\n\nFeature weight is a value that multiplies the points assigned to each feature. It is used to differentiate the importance of each feature.\n\nYou can make it easier to understand by thinking of it as a multiplier. The higher the weight, the more important the feature is. You can use any range of values (due to the unit vector normalization), but it is easier to interpret if the weights are between 0 and 1.\n\nSuppose you choose to use values from 0 to 1. Your most important feature will have a weight of 1. Other features should have a weight less than 1.\n\n### Normalized Weight (${\\hat{w}}$):\n\nThe model needs to be flexible and adaptable to accommodate changes in the business environment. Sometime after the model is built, the company may change its focus or process. In this case, features may need to be added or removed.\n\nThe normalized weight is a unit vector that is used to scale data in a way that preserves the relative relationships between the features when new features are added.\n\nThe basic idea is to transform the data such that the magnitude of the vector formed by the features is equal to 1. This ensures that each feature is scaled proportionally to the others, so the relative relationships between them is preserved when new features are added.\n\nYou may be asking yourself why not just recalculate the weights after adding or removing a feature?\nWell, this may work if you have the original data and just want to make a report out of it, but once you calculate the lead score and send the conversion events to platforms such as Google Analytics, Facebook Ads, etc. The scores registered in those platforms can't be changed. Later on you may want to create audiences based on the lead score, but you won't be able to do that if the scoring model has changed. The normalized weight vector solves this problem.\n\n<!-- #TODO rewrite this section -->\n\n#### Unit vector normalization:\n\n$$\n\\hat{w_n} = \\frac{w_n}{|w|}\n$$\n\n#### Feature weights vector magnitude:\n\n$$\n|w| = \\sqrt{\\sum\\limits^{n}_{i=0}w_i^2}\n$$\n\n#### Normalized weight vector:\n\n$$\n\\hat{w_n} = \\frac{w_n}{\\sqrt{\\sum\\limits^{n}_{i=0}w_i^2}}\n$$\n\nIn this way the sum of the squares of the normalized weights is equal to 1:\n\n$$\n\\sum\\limits^{n}_{i=0}{\\hat{w}_i^2} = 1\n$$\n\n### Qualification threshold:\n\nThe qualification threshold is the value that determines whether a lead is qualified or not. It is calculated as the midpoint of the range of points assigned to each feature.\n\n$$\n\\theta = \\text{points range}_{max} - \\frac{\\text{points range}_{max} - \\text{points range}_{min}}{2}\n$$\n\nIf the lead score $\\geq \\theta$ then the lead is qualified.\n\nNote that you can always change the qualification threshold to suit your needs. Since the default points range is 0 to 100, the default threshold is 50.\n\n### Points ($p$):\n\nPoints assigned to each option of each feature. The points are assigned based on the desirability of each option. The points are then multiplied by the normalized weight of the feature to obtain the weighted points that are then summed to obtain the lead score.\n\n> **NOTE:** The numbers below are only a suggestion. You can use any set of values. The important thing is to be consistent.\n\nThe proposed points assignment framework is as follows:\n\n1. Order the options from least desirable to most desirable.\n2. Determine the range of points for each feature: Define the minimum and maximum points for each feature. The minimum points should be assigned to the least desirable option, and the maximum points to the most desirable option. For instance, you could assign points on a scale of 0 to 100.\n3. Determine if the feature is numeric or categorical.\n\n - **If defining from numeric variables:**\n Specify the target ranges that best represents the ICP.\n For example, in a feature called \"Monthly users\", the ICP range could be \"50k to 100k\"\n - **If defining from categorical variables:**\n Identify the options that best represent the ICP. For example, in a feature called \"Industry\", the ICP options could be \"Retail\" and \"Telecom\".\n4. Assign points to the ICP option: Assign the qualification threshold points (suppose 50 points in this case) to the ICP option(s).\n5. Divide the remaining points range into equal intervals: For options less desirable than the ICP option, divide the range from the minimum points to the qualification threshold points (0 to 50) into equal intervals. For options more desirable than the ICP option, divide the range from the qualification threshold points to the maximum points (50 to 100) into equal intervals.\n\n Suppose a feature A has 4 options: A1, A2, A3, A4. The ICP option is A2:\n\n - For options less desirable than A2 (A1): Divide the range 0 to 50 into equal intervals (0 to 50, one interval of 50 points).\n - For options more desirable than A2 (A3 and A4): Divide the range 50 to 100 into equal intervals (50 to 100, two intervals of 25 points each).\n6. Assign points to the other options based on their position in the intervals: Assign points to each option based on the position of that option within the equal intervals.\n\n - A1: 0 points (minimum)\n - A2: 50 points (ICP option)\n - A3: 75 points\n - A4: 100 points (maximum)\n\n If none of the options seem to be a good fit for assigning 0 points, you can introduce a new baseline option that represents the least desirable criteria. This baseline option will be assigned 0 points, and the other options will be assigned points accordingly.\n\n The options for feature A would now be: A0, A1, A2, A3, and A4, with A0 being the new baseline option. The points assignment will now follow the same steps as before, but with A0 receiving 0 points:\n\n - A0: 0 points (minimum)\n - A1: 25 points\n - A2: 50 points (ICP option)\n - A3: 75 points\n - A4: 100 points (maximum)\n\nUse your best judgement and domain knowledge or historical data that suggests a certain lead score is more indicative of a qualified lead to determine the target ranges and how many options to include before and after the ICP options.\n\nNote that more than one ICP option can be defined for each feature as seen below:\n\n\n| Industry | Points | Calculation |\n| -------------- | ------ | ----------------------- |\n| Other | 0 | 50 - (50/5)*5 |\n| Agriculture | 10 | 50 - (50/5)*4 |\n| Transportation | 20 | 50 - (50/5)*3 |\n| Healthcare | 30 | 50 - (50/5)*2 |\n| Manufacturing | 40 | 50 - (50/5) |\n| Education | 50 | qualification_threshold |\n| Finance | 50 | qualification_threshold |\n| Technology | 50 | qualification_threshold |\n| Retail | 75 | 50 + 50/2 |\n| Telecom | 100 | 50 + (50/2)*2 |\n\n### Lead Score ($\\lambda$):\n\nLead score is the sum of squares the normalized weights of each feature multiplied by the points assigned to each feature.\n\n$$\n\\lambda = \\sum_{i=1}^n {\\hat{w}_i^2}{p_i} = ({\\hat{w}_1^2}{p_1})+({\\hat{w}_2^2}{p_2})+({\\hat{w}_3^2}{p_3})...({\\hat{w}_n^2}{p_n})\n$$\n\nThe higher the lead score, the more desirable the lead is. The lead score is then compared to the qualification threshold to determine if the lead is qualified or not.\n\nLead score can be used to rank and prioritize leads, and to create audiences based on the lead score on platforms such as Google Analytics, Facebook Ads, etc.\n\n### Features\n\nFeatures are a set of characteristics assigned to each lead. If you have difficulties finding out which features to add, start by adding relevant lead form or CRM fields as features.\n\nEach feature has points associated with it, which are assigned to each option of the feature. The points assigned to each option are relative to the qualification threshold. The higher the points, the more desirable the option.\n\nEach feature has a weight associated with it, which is used to differentiate the importance of each feature. The higher the weight, the more important the feature is.\n\nA feature have several options, each of which represent a range of values. For example, the feature \"Monthly Website Users\" has the following options:\n\n\n| Monthly Website Users | Points |\n| --------------------- | -------- |\n| Up to 50k | 0 |\n| 50k - 100k | 50 (ICP) |\n| 100k - 200k | 75 |\n| More than 200k | 100 |\n\nYou should first define the features and their options, then assign 50 points to the minimum viable option for the lead to be considered qualified. The remaining points should be distributed among the other options in a way that reflects the relative importance of each option.\n\nRemember that this is a suggestion, you can assign the points as you see fit and as your business requires. You may want to use negative points to penalize leads that do not meet certain criteria for example. It is generally easier to work with positive points, but it is up to you.\n\n# Usage\n\n## Predictive Model usage\n\nSoon!\n\n## Non-predictive Model usage\n\nIn the examples folder you can find a Jupyter Notebook with a step-by-step guide on how to use the library.\nYou may also want to check the [Google Sheets simulator](https://docs.google.com/spreadsheets/d/1ESEtcjno36ZLW5XMEoHqLKHjiZMkrZeIECcrcgFxHzA/edit?usp=sharing) (Non-predictive only)\n\n### Importing the library\n\n```python\nfrom glsm.non_predictive.model import NonPredictive\nfrom glsm.non_predictive.features import Feature\n```\n\n### Instantiating the model and adding features\n```python\nmodel = NonPredictive()\n\nfeature_a = Feature(\n name=\"Monthly Users\",\n weight=0.5,\n options_df=pd.DataFrame([\n {\"label\": \"Up to 50k\", \"is_ICP\": False},\n {\"label\": \"50k - 100k\", \"is_ICP\": True},\n {\"label\": \"100k - 200k\", \"is_ICP\": False},\n {\"label\": \"More than 200k\", \"is_ICP\": False},\n ])\n)\nfeature_b = Feature(\n name=\"Industry\",\n weight=0.25,\n options_df=pd.DataFrame([\n {\"label\": \"Other\", \"is_ICP\": False},\n {\"label\": \"Agriculture\", \"is_ICP\": False},\n {\"label\": \"Transportation\", \"is_ICP\": False},\n {\"label\": \"Healthcare\", \"is_ICP\": False},\n {\"label\": \"Manufacturing\", \"is_ICP\": False},\n {\"label\": \"Education\", \"is_ICP\": True},\n {\"label\": \"Finance\", \"is_ICP\": True},\n {\"label\": \"Technology\", \"is_ICP\": True},\n {\"label\": \"Retail\", \"is_ICP\": False},\n {\"label\": \"Telecom\", \"is_ICP\": False},\n ])\n)\nmodel.add_features([feature_a, feature_b])\n```\n\n### Removing features\n```python\nmodel.remove_features(['Industry'], ['Monthly Users'])\n```\n\n### Calculating the lead score\n\n#### From a dictionary\n\n```python\nlead = {\n \"Monthly Users\": \"50K - 100K\",\n \"Industry\": \"Technology\",\n \"Mkt Investment\": \"$300K - $400K\",\n }\n\nlambda_value = model.compute_lambda(lead)\n```\n\n#### From a csv\nCheck out the leads.csv file in the examples folder.\n```python\ndf = pd.read_csv('leads.csv')\ndf['lambda'] = df.apply(\n lambda row: model.compute_lambda(row.to_dict()),\n axis=1\n)\n```\n\n\n\n",
"bugtrack_url": null,
"license": "LICENSE.txt",
"summary": "A Python package that simplifies the process of building lead scoring models.",
"version": "0.1.3",
"project_urls": null,
"split_keywords": [
"python",
"lead score",
"modeling",
"lead generation",
"lead scoring",
"lead scoring model"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "cb367dd204eb72a9e99fcef6479f4eccebb5984b8034da220163d505eabcba23",
"md5": "727afdf6dc9d94b88eb738d4eeb5aff8",
"sha256": "0171b7b89657e42467bcad3d848c47fcee3be3a6c2aa5c84ac4055b6dabef5a4"
},
"downloads": -1,
"filename": "glsm-0.1.3-py3-none-any.whl",
"has_sig": false,
"md5_digest": "727afdf6dc9d94b88eb738d4eeb5aff8",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": null,
"size": 10170,
"upload_time": "2023-07-21T20:20:40",
"upload_time_iso_8601": "2023-07-21T20:20:40.225506Z",
"url": "https://files.pythonhosted.org/packages/cb/36/7dd204eb72a9e99fcef6479f4eccebb5984b8034da220163d505eabcba23/glsm-0.1.3-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "47f35907d6afdfcccd496f8f6647afbbc9a2a230df65c0348f0a7e1b4d4defea",
"md5": "766135468365437379060bd1defd1a1a",
"sha256": "c1adbff6dbd9e01243f1ece88010f9fcdca86c15ac961eced46a3de3c54a780f"
},
"downloads": -1,
"filename": "glsm-0.1.3.tar.gz",
"has_sig": false,
"md5_digest": "766135468365437379060bd1defd1a1a",
"packagetype": "sdist",
"python_version": "source",
"requires_python": null,
"size": 14422,
"upload_time": "2023-07-21T20:20:42",
"upload_time_iso_8601": "2023-07-21T20:20:42.219391Z",
"url": "https://files.pythonhosted.org/packages/47/f3/5907d6afdfcccd496f8f6647afbbc9a2a230df65c0348f0a7e1b4d4defea/glsm-0.1.3.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-07-21 20:20:42",
"github": false,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"lcname": "glsm"
}
JSON