Tracking interaction with sponsored and unsponsored content

A method for tracking user interaction with content of a website, the method comprising operations performed using one or more hardware processors, the operations comprising:

• receiving a tracking event packet including data fields comprising a packet identification that uniquely indicates the tracking event packet, a tracking event identifier uniquely indicating a specific instance of the user interaction with the content, a content identifier uniquely indicating content with which the user interacted, a cost associated with the user interaction, a campaign identifier uniquely indicating a campaign with which the content is associated, and an advertiser identification uniquely indicating an advertiser that initiated the campaign;
• determining whether the tracking event packet is a duplicate based on the packet identification and marking the packet as invalid if the tracking event packet is determined to be a duplicate;
• hashing, by a databus consumer, the advertiser identification;
• aggregating, by the databus consumer dedicated to serving and performing operations on data from packets with advertiser identifications that hash to a same value, non-duplicate tracking event packets by advertiser identification such that packets with advertiser identifications that hash to the same value are aggregated together;
• determining, by the databus consumer and based on the data from the packets with advertiser identifications that hash to a same value, budget and performance related metrics of the campaign;
• determining whether the tracking event packet corresponds to a revenue generating tracking event,
• transferring, by the databus consumer, the budget and performance related metrics to a first database and a second database, the first database includes data stored for analytics and the second database includes data stored for billing and campaign performance monitoring;
• transferring, by the databus consumer, aggregated tracking event packets to the first database and the second database sooner subsequent to the aggregation if it is determined that the aggregated event packets include a tracking event packet corresponding to a revenue generating tracking event than if the aggregated event packets do not include a tracking event packet corresponding to a revenue generating tracking event;
• and
• presenting analytics information using data from the transferred aggregated tracking event packets and the budget and performance related metrics on the first database or providing a bill to the advertiser using data from the transferred aggregated tracking event packets on the second database.

A system for tracking user interaction with content of a website, the system comprising:

• one or more hardware processors;
• one or more memories communicatively coupled to the one or more hardware processors, the one or more memories including instructions stored thereon, which when executed by the one or more processors, cause the one or more processors to perform operations, the operations comprising:
• receiving a tracking event packet including data fields comprising a packet identification that uniquely indicates the tracking event packet, a tracking event identifier uniquely indicating a specific instance of the user interaction with the content, a content identifier uniquely indicating content with which the user interacted, a cost associated with the user interaction, a campaign identifier uniquely indicating a campaign with which the content is associated, and an advertiser identification uniquely indicating an advertiser that initiated the campaign;
• determining whether the tracking event packet is a duplicate based on the packet identification and marking the packet as invalid if the tracking event packet is determined to be a duplicate;
• hashing, by a databus consumer, the advertiser identification;
• aggregating, by the databus consumer dedicated to serving and performing operations on data from packets with advertiser identifications that hash to a same value, non-duplicate tracking event packets by advertiser identification such that packets with advertiser identifications that hash to the same value are aggregated together;
• determining, by the databus consumer and based on the data from the packets with advertiser identifications that hash to a same value, budget and performance related metrics of the campaign;
• determining whether the tracking event packet corresponds to a revenue generating tracking event,
• transferring, by the databus consumer, the budget and performance related metrics to a first database and a second database, the first database includes data stored for analytics and the second database includes data stored for billing and campaign performance monitoring;
• transferring, by the databus consumer, aggregated tracking event packets to the first database and the second database sooner subsequent to the aggregation if it is determined that the aggregated event packets include a tracking event packet corresponding to a revenue generating tracking event than if the aggregated event packets do not include a tracking event packet corresponding to a revenue generating tracking event;
• and
• presenting analytics information using data from the transferred the budget and performance related metrics on the first database or providing a bill to the advertiser using data from the transferred aggregated tracking event packets on the second database.