In some embodiments, the historical data record 300 may include an index as for each instance of content playback as depicted in column 314. In some embodiments, an index may identify a last position reached in playback. By way of example, an index may be a run time, a scene identifier, or the like that indicates a position within playback of the content that was last reached. By way of example, song D may have a total playback time (total run time) of three minutes and twelve seconds. However, due to the user input received at 09:43:20 as depicted at 316, song D may have been halted one minute and twenty seconds into the song. An index indicating the current position (e.g., 1:20) may be stored such that the last point reached in the song may be stored for subsequent use.

The historical data record 300 may include any suitable data related to any suitable aspect of user input and/or operations performed at the user device. Column 318 depicts maintaining a record of the volume levels at which content was played. Any suitable information stored in the historical data record 300 and/or the state information record 200 of FIG. 2 may be utilized by the content management engine 102 at any suitable time for any suitable purpose (e.g., to make decisions regarding what content is to be played and/or which device(s) are to be used for playback).

Returning to FIG. 1, the state information may be maintained in the manner and/or records described in connection with FIGS. 2 and 3 or otherwise. In some embodiments, the state information 114 may be stored as objects, lists, files, or the like and may be specific to the device, a group of devices, or user account.