Abstract: Requests for content are received from a user. For example, an HTTP request for a web page sent by a computing device of the user is received by a server. Each request has a landing context, which may include information about the user sending the request, the request itself, the referrer, or another subject. This information can be found in the requests or accessed from sources external to the requests. The information in the landing context is used to redirect the request to a particular web page or other piece of content. Information about a success or repel resulting from the redirection may be collected and used to inform later redirections.

Abstract: Requests for content are received, for example, an HTTP request for a web page is received. Each request has a landing context, which may include information about the user sending the request, the request itself, the referrer, or another subject. This information can be found in the requests or external to the requests. The information of the landing context is compared to appropriate triggering criteria. For requests that satisfy the appropriate triggering criteria, a destination is provided based on one or more weighted treatments. The request is directed to the provided destination. The results of the requests are subsequently analyzed and used to adjust the treatments in an automated fashion.

Abstract: Requests for content are received, for example, an HTTP request for a web page is received. Each request has a landing context, which may include information about the user sending the request, the request itself, the referrer, or another subject. This information can be found in the requests or external to the requests. The information of the landing context is compared to appropriate triggering criteria. For requests that satisfy the appropriate triggering criteria, a destination is provided based on one or more weighted treatments. The request is directed to the provided destination. The results of the requests are subsequently analyzed and used to adjust the treatments in an automated fashion.

Abstract: Requests for content are received, for example, an HTTP request for a web page is received. Each request has a landing context, which may include information about the user sending the request, the request itself, the referrer, or another subject. This information can be found in the requests or external to the requests. The information of the landing context is compared to appropriate triggering criteria. For requests that satisfy the appropriate triggering criteria, a destination is provided based on one or more weighted treatments. The request is directed to the provided destination. The results of the requests are subsequently analyzed and used to adjust the treatments in an automated fashion.

Abstract: Disclosed are various embodiments for generating automobile parts bundles associated with maintenance events. A maintenance schedule is retrieved and various maintenance events are identified. Various maintenance tasks associated with maintenance events are also identified. Parts associated with these maintenance tasks are placed into parts bundles associated with the maintenance event and a unique identifier within a parts catalog.