Abstract: A system and method may optional include or utilize a processor configured to receive a request for social network content for display in a sponsored content position in a newsfeed of a social network interface, the position having a position criterion, identify a sponsored content item of multiple sponsored content items stored on a database based, at least in part, on a characteristic of the sponsored content item meeting the position criterion, a bid associated with the sponsored content item, and a scaling factor, wherein each of the sponsored content items correspond to one of multiple item types and at least two of the sponsored content items are of a different item type. The scaling factor for each of the sponsored content items is based on the item type of the corresponding one of the sponsored content items.

Abstract: A system and method optionally includes or utilizes a processor may receive a request for social network content for display in a position of a plurality of sponsored content positions in a newsfeed of a social network interface, each of the plurality of sponsored content positions having a position criterion, at least two of the plurality of sponsored content positions having a different position criterion and identify a sponsored content item of a plurality of sponsored content items stored on a database based, at least in part, on a characteristic of the sponsored content item meeting the position criterion and a bid associated with the sponsored content item. A transmitter may transmit the sponsored content item from the processor to a server for display on a user interface.

Abstract: A system may include a database configured with individual partitions, one of the partitions corresponding to a sponsored content campaign of a social network. The system may further include multiple servers each communicatively coupled to the database, and each configured to implement a campaign having a campaign termination criterion. Each of the servers may include a processor configured to track sponsored content event data received from a user device based on the campaign and transmit the event data to the database and terminate the campaign based on a comparison of the event data as received from a partition of the database corresponding to the campaign and an estimation of event data not received from the database. The database may be configured to store the event data as received from the servers in the partition corresponding to the campaign upon receipt of the event data.

Abstract: Apparatus and methods are provided for indexing electronic content to be served to users' mobile and/or stationary communications and computing devices. An index is composed of multiple slices, with each slice storing multiple entries and each entry representing one content item or one campaign or collection of content items. An entry is populated with tokens representing attribute/value pairs of a target audience of the content item and/or property/value pairs of the item or the item's campaign. A query or request to identify content items for serving to a particular user is similarly formatted with tokens representing attribute/value pairs of the user and/or item/campaign. Queries can then be executed rapidly across any or all index entries in any or all slices. Within a slice, entries may be sorted by value or score, and integer components within an individual entry may be sorted to facilitate rapid comparison with a query.

Abstract: A system may include a database configured with individual partitions, one of the partitions corresponding to a sponsored content campaign of a social network. The system may further include multiple servers each communicatively coupled to the database, and each configured to implement a campaign having a campaign termination criterion. Each of the servers may include a processor configured to track sponsored content event data received from a user device based on the campaign and transmit the event data to the database and terminate the campaign based on a comparison of the event data as received from a partition of the database corresponding to the campaign and an estimation of event data not received from the database. The database may be configured to store the event data as received from the servers in the partition corresponding to the campaign upon receipt of the event data.

Abstract: A social network system includes a machine-readable memory storing computer-executable instructions and a plurality of member data elements associated with a member, one or more hardware processors having executed the computer-executable instructions, configure the social network system to provide an interface to a content provider allowing the content provider to define a lead rule for a cost-per-lead (CPL) campaign, the lead rule including a lead action and a lead content item, the lead action identifies a member action relative to the lead content item, receive the defined lead rule into the memory, activate the CPL campaign including the defined lead rule, transmit the lead content item to the member, receive indication that the member has performed the lead action, and provide the member as a lead to the content provider, including providing a first member data element of the plurality of member data elements to the content provider.

Abstract: A system may include a database configured with individual partitions, one of the partitions corresponding to a sponsored content campaign of a social network. The system may further include multiple servers each communicatively coupled to the database, and each configured to implement a campaign having a campaign termination criterion. Each of the servers may include a processor configured to track sponsored content event data received from a user device based on the campaign and transmit the event data to the database and terminate the campaign based on a comparison of the event data as received from a partition of the database corresponding to the campaign and an estimation of event data not received from the database. The database may be configured to store the event data as received from the servers in the partition corresponding to the campaign upon receipt of the event data.

Abstract: A system may include a database configured with individual partitions, one of the partitions corresponding to a sponsored content campaign of a social network. The system may further include multiple servers each communicatively coupled to the database, and each configured to implement a campaign having a campaign termination criterion. Each of the servers may include a processor configured to track sponsored content event data received from a user device based on the campaign and transmit the event data to the database and terminate the campaign based on a comparison of the event data as received from a partition of the database corresponding to the campaign and an estimation of event data not received from the database. The database may be configured to store the event data as received from the servers in the partition corresponding to the campaign upon receipt of the event data.

Abstract: A system may include a database configured with individual partitions, one of the partitions corresponding to a sponsored content campaign of a social network. The system may further include multiple servers each communicatively coupled to the database, and each configured to implement a campaign having a campaign termination criterion. Each of the servers may include a processor configured to track sponsored content event data received from a user device based on the campaign and transmit the event data to the database and terminate the campaign based on a comparison of the event data as received from a partition of the database corresponding to the campaign and an estimation of event data not received from the database. The database may be configured to store the event data as received from the servers in the partition corresponding to the campaign upon receipt of the event data.

Abstract: Apparatus and methods are provided for indexing electronic content to be served to users' mobile and/or stationary communications and computing devices. An index is composed of multiple slices, with each slice storing multiple entries and each entry representing one content item or one campaign or collection of content items. An entry is populated with tokens representing attribute/value pairs of a target audience of the content item and/or property/value pairs of the item or the item's campaign. A query or request to identify content items for serving to a particular user is similarly formatted with tokens representing attribute/value pairs of the user and/or item/campaign. Queries can then be executed rapidly across any or all index entries in any or all slices. Within a slice, entries may be sorted by value or score, and integer components within an individual entry may be sorted to facilitate rapid comparison with a query.

Abstract: Apparatus and methods are provided for indexing electronic content to be served to users' mobile and/or stationary communications and computing devices. An index is composed of multiple slices, with each slice storing multiple entries and each entry representing one content item or one campaign or collection of content items. An entry is populated with tokens representing attribute/value pairs of a target audience of the content item and/or property/value pairs of the item or the item's campaign. A query or request to identify content items for serving to a particular user is similarly formatted with tokens representing attribute/value pairs of the user and/or item/campaign. Queries can then be executed rapidly across any or all index entries in any or all slices. Within a slice, entries may be sorted by value or score, and integer components within an individual entry may be sorted to facilitate rapid comparison with a query.

Abstract: A system and method may optional include or utilize a processor configured to receive a request for social network content for display in a sponsored content position in a newsfeed of a social network interface, the position having a position criterion, identify a sponsored content item of multiple sponsored content items stored on a database based, at least in part, on a characteristic of the sponsored content item meeting the position criterion, a bid associated with the sponsored content item, and a scaling factor, wherein each of the sponsored content items correspond to one of multiple item types and at least two of the sponsored content items are of a different item type. The scaling factor for each of the sponsored content items is based on the item type of the corresponding one of the sponsored content items.

Abstract: A system and method optionally includes or utilizes a processor may receive a request for social network content for display in a position of a plurality of sponsored content positions in a newsfeed of a social network interface, each of the plurality of sponsored content positions having a position criterion, at least two of the plurality of sponsored content positions having a different position criterion and identify a sponsored content item of a plurality of sponsored content items stored on a database based, at least in part, on a characteristic of the sponsored content item meeting the position criterion and a bid associated with the sponsored content item. A transmitter may transmit the sponsored content item from the processor to a server for display on a user interface.

Abstract: A system may include a database configured with individual partitions, one of the partitions corresponding to a sponsored content campaign of a social network. The system may further include multiple servers each communicatively coupled to the database, and each configured to implement a campaign having a campaign termination criterion. Each of the servers may include a processor configured to track sponsored content event data received from a user device based on the campaign and transmit the event data to the database and terminate the campaign based on a comparison of the event data as received from a partition of the database corresponding to the campaign and an estimation of event data not received from the database. The database may be configured to store the event data as received from the servers in the partition corresponding to the campaign upon receipt of the event data.

Abstract: Apparatus and method are provided for indexing electronic content to be served to users that operate mobile and/or stationary communications and computing devices. An index is composed of multiple slices, with each slice capable of storing multiple entries and each entry representing one content item. A content item's index entry is populated with integer values representing attribute/value pairs of a target audience of the content item. A query or request to identify content items for serving to a particular user is similarly formatted with integers representing attribute/value pairs of the user. Queries can then be executed rapidly across any or all index entries in any or all slices. Within a slice, entries may be sorted by value or score, and integer components within an individual entry may be sorted to facilitate rapid comparison with a query.

Abstract: Apparatus and methods are provided for indexing electronic content to be served to users' mobile and/or stationary communications and computing devices. An index is composed of multiple slices, with each slice storing multiple entries and each entry representing one content item or one campaign or collection of content items. An entry is populated with tokens representing attribute/value pairs of a target audience of the content item and/or property/value pairs of the item or the item's campaign. A query or request to identify content items for serving to a particular user is similarly formatted with tokens representing attribute/value pairs of the user and/or item/campaign. Queries can then be executed rapidly across any or all index entries in any or all slices. Within a slice, entries may be sorted by value or score, and integer components within an individual entry may be sorted to facilitate rapid comparison with a query.