Skip to content

Commit

Permalink
πŸ“ fix typos
Browse files Browse the repository at this point in the history
  • Loading branch information
tomshelllby committed Jan 19, 2024
1 parent 7fab6ff commit 402e51f
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,15 +6,15 @@
</picture>
</a>

> We are the boutique analytics consultancy that turns disorganised data into real business value.
> We are the boutique analytics consultancy that turns disorganised data into real business value. [Get in touch](https://tasman.ai/contact/) to learn more about how Tasman can help solve your organisations data challenges.
# Multi-Touch Attribution Engine

**Key Features:**
- πŸ”© Boolean-algebra based filter definitions, allowing fine control of the touches and conversions that are analysed for each attribution model without editing any SQL.
- πŸͺ› Reconfigurable positional and time-based attribution models.
- πŸ”€ Multiple concurrent models, enabling robust multi-model analyses.
- ⏰ Fine-grain attribution window control.
- πŸ”© Boolean-algebra rule-based configurations avoiding custom SQL requirements
- πŸͺ› Reconfigurable positional and time-based attribution models
- πŸ”€ Multiple concurrent models, enabling robust, flexible, multi-model analyses
- ⏰ Fine-grain attribution window control
- βž• Optional incremental materialisations
- ❄️ Custom warehouse selection (Snowflake only)

Expand Down Expand Up @@ -44,7 +44,7 @@ The engine has two primary output models, attributed touches and attributed conv

## Performance Tracking πŸš€

Attribution is tricky and it'ss unlikely that optimal results will be achieved during the initial implementation of this engine - this is because the quality of the outputs are entirely dependent on the quality of the inputs along with tuning of the configurations. As such, an [`performance_history`](models/tasman_mta__performance_history.sql) model has been added that will keep track of each time the attribution engine is run, and collect useful statistics that can help accelerate the implementation as well as monitor key metrics such as attribution rate.
Attribution is tricky and it's unlikely that optimal results will be achieved during the initial implementation of this engine - this is because the quality of the outputs are entirely dependent on the quality of the inputs along with tuning of the configurations. As such, a [`performance_history`](models/tasman_mta__performance_history.sql) model has been added that will keep track of each time the attribution engine is run, and collect useful statistics that can help accelerate the implementation as well as monitor key metrics such as attribution rate.

## Current Limitations ⚠️

Expand Down

0 comments on commit 402e51f

Please sign in to comment.