# US 12,001,500 B2 · System, methods and computer products for determining affinity to a content creator > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,001,500 B2 - Document ID: US12001500B2 - Status: Granted - Kind: B2 - Application number: 17/526,431 - Filed: 2021-11-15 - Published: 2022-05-05 - Granted: 2024-06-04 - Earliest claimed: 2015-11-17 - Assignees: Spotify AB - Applicants: Spotify AB - Inventors: Noel Cody; Kinshuk Mishra; Steve Shirley - Web page: https://patentgrep.com/patent/US12001500B2 ## CPC - G06F 16/955: using information identifiers, e.g. uniform resource locators [URL] - G06F 16/285: {Clustering or classification} - G06F 16/9535: Search customisation based on user profiles and personalisation - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Affinity scores are computed for a plurality of user accounts, each affinity score quantifies an affinity of a user account to a content creator of one or more digital objects hosted in a content hosting platform. Each affinity score is computed by collecting interaction data for the user account corresponding to the content creator, normalizing the collected interaction data using a total activity data of the user account on the content hosting platform and attribute data associated with the content creator, and generating the affinity score using the normalized interaction data. ## Claims ### Claim 1 A method for providing an interface for managing affinity-related information comprising the steps of: receiving, at a dashboard system associated with a content distribution platform that hosts content associated with a content provider, access over a network to affinity data, the affinity data including affinity scores that quantify respective affinities of user accounts on the content distribution platform to the content hosted on the content distribution platform associated with the content provider; accessing, via the dashboard system, the affinity data over the network; ranking the affinity scores of the user accounts, thereby resulting in ranked affinity scores; displaying the affinity data, including the ranked affinity scores in a view of the dashboard system; receiving, at a first interface of the dashboard system, input from the content provider in response to the displayed affinity data; and causing targeted data to be sent to a second interface of a client device based on the ranked affinity scores, the client device being associated with a first user account of the user accounts that is associated with a user other than the content provider; wherein the affinity data further includes one or more category labels that label the user accounts based on the ranked affinity scores, the one or more category labels including a first label indicating a respective affinity score has increased by at least a threshold amount; and wherein the first user account is labeled with at least the first label. ### Claim 2 (depends on 1) The method according to claim 1, wherein the targeted data includes data for an event. ### Claim 3 (depends on 2) The method according to claim 2, wherein the data for the event includes a date, a time, and a location of the event. ### Claim 4 (depends on 2) The method according to claim 2, wherein the event is a concert. ### Claim 5 (depends on 1) The method according to claim 1, further including receiving, at the first interface of the dashboard system, additional input from the content provider that causes: the displayed affinity data to be manipulated, thereby creating manipulated affinity data; and additional targeted data based on the manipulated affinity data to be sent to the second interface of the client device, the client device being associated with one of the user accounts that is associated with a user other than the content provider. ### Claim 6 (depends on 1) The method according to claim 1, wherein the affinity scores are computed based at least in part on: interaction data associated with the user accounts; and attribute data associated with the content provider. ### Claim 7 (depends on 1) The method according to claim 1, further including the step of receiving, at the first interface of the dashboard system, additional input from the content provider based on the displayed affinity data that causes a digital object hosted by the content distribution platform to be modified. ### Claim 8 A computer-implemented dashboard system associated with a content distribution platform that hosts content associated with a content provider, comprising: a processor; and a memory coupled to the processor, wherein the memory stores instructions that in response to execution by the processor cause the processor to perform operations comprising: receiving access over a network to affinity data, the affinity data including affinity scores that quantify respective affinities of user accounts on the content distribution platform to the content hosted on the content distribution platform associated with the content provider; accessing the affinity data over the network; ranking the affinity scores of the user accounts, thereby resulting in ranked affinity scores; displaying the affinity data including the ranked affinity scores in a view; receiving, at a first interface of the computer-implemented dashboard system, input from the content provider in response to the displayed affinity data; and causing targeted data to be sent to a second interface of a client device based on the ranked affinity scores, the client device being associated with one a first user account of the user accounts that is associated with a user other than the content provider; wherein the affinity data further includes one or more category labels that label the user accounts based on the ranked affinity scores, the one or more category labels including a first label indicating a respective affinity score has increased by at least a threshold amount; and wherein the first user account is labeled with at least the first label. ### Claim 9 (depends on 8) The computer-implemented dashboard system according to claim 8, wherein the targeted data includes data for an event. ### Claim 10 (depends on 9) The computer-implemented dashboard system according to claim 9, wherein the data for the event includes (1) a date of the event, (2) a time of the event, (3) a location of the event, or (4) any combination of (1), (2), and (3). ### Claim 11 (depends on 9) The computer-implemented dashboard system according to claim 9, wherein the event is a concert. ### Claim 12 (depends on 8) The computer-implemented dashboard system according to claim 8, wherein the input from the content provider includes the content provider manipulating the displayed affinity data. ### Claim 13 (depends on 12) The computer-implemented dashboard system according to claim 12, further including instructions that cause the processor to cause a hosted digital object associated with the content provider to be modified based on the content provider manipulating the displayed affinity data. ### Claim 14 (depends on 8) The computer-implemented dashboard system according to claim 8, wherein the affinity scores are computed based at least in part on: interaction data associated with the user accounts; social media data associated with the user accounts; and attribute data associated with the content provider. ### Claim 15 (depends on 8) The computer-implemented dashboard system according to claim 8, wherein the input from the content provider based on the displayed affinity data further causes a digital object hosted by the content distribution platform to be modified. ### Claim 16 A non-transitory computer-readable medium having instructions stored therein that in response to execution by a device cause the device to perform operations comprising: receiving, at a dashboard system associated with content distribution platform that hosts content associated with a content provider, access over a network to affinity data, the affinity data including affinity scores that quantify respective affinities of user accounts on the content distribution platform to the content hosted on the content distribution platform associated with the content provider; accessing, via the dashboard system, the affinity data over the network; ranking the affinity scores of the user accounts, thereby resulting in ranked affinity scores; displaying the affinity data including the ranked affinity scores in a view of the dashboard system; receiving, at a first interface of the dashboard system, input from the content provider in response to the displayed affinity data based on the ranked affinity scores; and causing targeted data to be sent to a second interface of a client device, the client device being associated with a first user account of the user accounts that is associated with a user other than the content provider; wherein the affinity data further includes one or more category labels that label the user accounts based on the ranked affinity scores, the one or more category labels including a first label indicating a respective affinity score has increased by at least a threshold amount; and wherein the first user account is labeled with at least the first label. ### Claim 17 (depends on 16) The non-transitory computer-readable medium of claim 16, wherein the affinity scores are computed by: collecting interaction data for the user accounts, thereby creating collected interaction data; normalizing the collected interaction data for each user account using a total activity data of the respective user account on the content distribution platform and attribute data associated with the content provider, thereby creating normalized interaction data, and generating the affinity scores using the normalized interaction data. ### Claim 18 (depends on 16) The non-transitory computer-readable medium of claim 16, wherein the targeted data includes a promotion for an event. ### Claim 19 (depends on 18) The non-transitory computer-readable medium of claim 18, wherein the promotion for the event includes (1) a date of the event, (2) a time of the event, (3) a location of the event, or (4) any combination of (1), (2), and (3). ### Claim 20 (depends on 16) The non-transitory computer-readable medium of claim 16, wherein the instructions further cause the device to perform operations comprising receiving, at the first interface of the dashboard system, additional input from the content provider based on the displayed affinity data that causes digital objects hosted by the content distribution platform to be modified.