Hi, could someone explain the scoring logic used in Score Rows. If I have Keywords A, B, C set up - with a score of 10 for A, 10 for B and 10 for C For example the company description that I am scoring includes Key word A 3 times, keyword B 3 times and keyword C 3 times Would the score be 3x10 + 3x10 + 3x10 = 90 ie for each time the key word occurs OR 1x10 + 1x10 + 1x10 = 30 because it only counts IF it occurs not how many times OR 1x10 = 10 because it only counts one/any of the keyword occurs Here is a screenshot of my set up - and the "reasons" to help figure it out https://app.clay.com/workspaces/109036/tables/t_PcJM9ueydX2f/views/gv_ijFcjOeezinO this is the table
OMG .. is it case sensitive?
so my VC key word would not fire for vc?
this is the panel above enlarged and highlighted for keywords - hence my confusion that it only got a score of 100
Sorry, another question, can keywords have negative scores eg can I add the keyword Blockchain and give it a score of -50?
Hey Ian!! Sorry for the delay. Here's an example that would help clarify how the scoring works. Also, it's case insensitive so it should still pick it up (also in the example).I'll record a quick look if it helps too

And yes, you can assign it a negative score too by adding the symbol before the number like in your example above :)
Thanks guys, the video was super clear in explaining. In summary for each Scoring Criteria what counts is the 1st occurance of any of the Keywords in that Scoring Crietria list and its value So .... if I want to accumulate "scores" for each time a keyword appears, as a workaround I have to have a separate Scoring Criteria for each keyword .... Can I suggest an enhancement that toggles the accumulation mode a) 1st occurance of any keywords (with regard to order) (as now) b) "Unique Accumulate": Counts the unique occrences of all keywords ie if keyword VC appears x6 times, and Capital x7 in the text, it would count as 2 c) "Per Occurence Accumulate" Count each time any keyword appears (so above would be 6+7)
Awesome suggestions! Will also add that from the previous thread. We do have separate integrations that count occurrences but nested in this one does make sense too. Thank you!
