Asynchronous advertising placement based on metadata

1. A method for content filtering, the method comprising:

receiving information at an ad server regarding one or more media content files provided to a user device by one or more content servers, wherein each of the media content files includes metadata reflecting characteristics used to organize the respective media content file;

receiving ad-based criteria at the ad server, wherein the ad-based criteria associates one or more ad campaigns with at least one of the media content files, wherein the criteria concern personalization of ad files in at least one of the ad campaigns for a user of the user device based on information in an associated user profile that is updated on a periodic basis and includes acceptability rules that indicate what types of digital ad files the user does and does not want to receive;

executing instructions stored in memory by a processor of the ad server, the instructions executed to:

filter one or more of the associated ad campaigns based on the acceptability rules, and

personalize at least one of the ad files from the filtered ad campaigns to provide a personalized set of ad files for play on the user device, wherein personalizing the at least one ad file is based on characteristics of the at least one media content file and the ad-based criteria associated with each ad file in the personalized set, wherein the personalized set of ad files is stored in memory of the user device, and wherein the personalized set of ad files is included in a stored history;

tracking, by the ad server, which of the personalized set of ad files have been played within a predetermined time period, wherein a plug-in client recalls the played ad files upon request from the memory to be played on the user device; and

updating, by the ad server, the stored personalized set of ad files in memory with a new personalized set of ad files that have been filtered based on updates to the user profile information on the user device, wherein the new personalized set of ad files is stitched into media content files subsequently played on the user device.

2. The method of claim 1 , wherein the user profile information further includes information about ad files or media content files previously accessed by the user device, wherein such information is stored in a log.

3. The method of claim 1 , further comprising stitching at least one ad file in the personalized set with the at least one media content file after the user device has received both the personalized set and the at least one media content file and prior to play of the at least one media content file on the user device.

4. The method of claim 3 , wherein the stitching of the at least one ad file with the at least one media content file is based on metadata associated with the at least one ad file that specifies where the at least one ad file is to be stitched within the at least one media content file.

5. The method of claim 3 , wherein the stitching of the at least one ad file with the at least one media content file is based on metadata associated with the at least one media content file that specifies where ad files are to be stitched within the at least one media content file.

6. The method of claim 1 , wherein delivery of the personalized set of ad files is asynchronous relative to delivery of the at least one media content file.

7. The method of claim 1 , wherein the personalized set of ad files provided to the user device is based on a distribution factor for the filtered ad campaigns.

8. The method of claim 1 , further comprising storing information in memory specifying an order in which the ad files in the personalized set are to be played within the at least one media content file.

9. A system for content filtering, the system comprising:

a communication interface of an ad server that communicates over a communication network, wherein the communication interface:

receives information regarding one or more media content files provided by one or more content servers to a user device, wherein each of the received media content files includes metadata reflecting characteristics used to organize the respective media content file,

receives ad-based criteria that associates one or more ad campaigns with at least one of the media content files, wherein the criteria concern personalization of ad files in at least one of the ad campaigns for a user of the user device based on information in an associated user profile, that is updated on a periodic basis and includes acceptability rules that indicate what types of digital ad files the user does or does not want to receive;

a processor of the ad server that executes instructions stored in a computer-readable storage medium, wherein execution of the instructions by the processor:

filters one or more of the associated ad campaigns based on the acceptability rules, and

personalizes at least one of the ad files from the filtered ad campaigns to provide a personalized set of ad files for play on the user device, wherein personalizing the at least one ad file is based on characteristics of the at least one media content the and the ad-based criteria associated with each ad file in the personalized set; and

the ad server that:

stores the personalized set of ad files, the personalized set of ad files included in a stored history,

tracks which of the personalized set of ad files have been played within a predetermined time period, wherein a plug-in client recalls the played ad files upon request from memory to be played;

updates the stored personalized set of files with a new personalized set of ad files that have been filtered based on updates to the user profile information, wherein the new personalized set of ad files is stitched into media content files subsequently played on the user device.

10. A non-transitory computer-readable storage medium, having embodied thereon a program executable by a processor to perform a method for content filtering, the method comprising:

receiving information regarding one or more media content files provided to a user device by one or more content servers, wherein each of the media content files includes metadata reflecting characteristics used to organize the respective media content file;

receiving ad-based criteria at an ad server, wherein the ad-based criteria associates one or more ad campaigns with at least one of the media content files, wherein the criteria concern personalization of ad files in at least one ad campaign for a user of the user device based on information in an associated user profile, wherein the user profile information is updated on a periodic basis and includes acceptability rules that indicate what types of digital ad files the user does and does not want to receive;

filtering, by the ad server, one or more of the associated ad campaigns based on the acceptability rules,

personalizing, by the ad server, at least one of the ad files from the filtered ad campaigns to provide a personalized set of ad files for play on the user device, wherein personalizing the at least one ad file is based on characteristics of the at least one media content the and the ad-based criteria associated with each ad file in the personalized set, wherein the personalized set of ad files is stored in memory of the user device, and wherein the personalized set of ad files is included in a stored history;

tracking, by the ad server, which of the personalized set of ad files have been played within a predetermined time period, wherein a plug-in client recalls the played ad files upon request from the memory to be played on the user device; and

updating, by the ad server, the stored personalized set of ad files in memory with a new personalized set of ad files that have been filtered based on updates to the user profile information on the user device, wherein the new personalized set of ad files is stitched into media content files subsequently played on the user device.

11. The method of claim 1 , further comprising:

receiving a request to play at least one media content file, wherein the request is received under one or more contexts;

accessing context information to identify the contexts at a time of the request;

selecting at least one ad file from the personalized set based on the identified contexts; and

inserting the selected ad file into the requested media content file prior to play.

12. The method of claim 11 , further comprising maintaining a set of rotation rules for at least one of the ad campaigns, each rule specifying a different context under which a different ad file in the at least one ad campaign is to be inserted into the requested media content file.

13. The method of claim 11 , further comprising automatically changing out the inserted ad file when the contexts have been identified as having changed.

14. The method of claim 11 , wherein the context information includes at least one of time of day, location of play, week of month, number of plays, proportion of plays, expiration period, and other ad files already played.

15. The method of claim 14 , wherein accessing the context information includes obtaining the location of play based on at least one of user zip code included in the user profile, IP address of the user device, and GPS location associated with the user device.

16. The method of claim 1 , further comprising receiving a cue sheet associated with the at least one media content file, the cue sheet indicating one or more locations within the at least one media content file where ad files are to be inserted.

17. The method of claim 16 , wherein the locations within the at least one media content file are associated with time codes or style codes.