# Opportunity pipeline scoring

some points on scores created in the opportunity pipeline

* metrics: let's divide them into **counts** and **scores**.
* counts are the actual numbers, e.g. the number of twitter followers. mentions have counts for:
  * visibility (impressions)
  * engagement
* scores (for now) are integers. they are calculated by us on the basis of counts and go from 0 to 100. the total score is an average of all three scores.
* we have two kinds of retrievers:*api-based\_and\_site-based*. the api based (twitter, facebook) are (usually) social networks, whereas other are URLs in general (this is very vaguely speaking).
* a general principle should be as follows: whenever the count/score can be calculated on the retriever, it should be done there. otherwise, it is delegated to the`MentionFormatter`class (for now)
* metrics descriptions:

  * **visibility** (impressions): how many people can view the mention. this can be e.g. a number of followers on twitter/facebook or a measure of site's visibility via alexa rank. it is meant as an *off-site metric* ---from [wikipedia](http://en.wikipedia.org/wiki/Web_analytics) :

  > Off-site web analytics refers to web measurement and analysis regardless of whether you own or maintain a website. It includes the measurement of a website's potential audience (opportunity), share of voice (visibility), and buzz (comments) that is happening on the Internet as a whole.

  * **engagement**: user (inter)actions involving the mention. can be likes, retweets etc. or a number we get from sharedcount's api.
  * **presence**(seo, splash): score representing how optimized/relevant the mention source is to the keyword. this is meant to be an

    *on-site metric*
* we estimate visibility count for site-based retrievers through alexa. see [here](https://www.evernote.com/shard/s1/sh/f1c105ad-f627-4739-bf38-e4c6b0ba39e5/14c8b0fcaf30567c4d81f085684c8f53)
* [how to get impressions from engagement](http://socialmediatoday.com/rgbsocial/1495136/correlating-social-media-engagement-impressions)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://omalab.gitbook.io/guide/engineering-wiki/legacy-and-deprecated/opportunity-pipeline-scoring.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.