2010 Lexus Gs350 Climate Seats Sunroof Nav Rear Cam 25k Texas Direct Auto on 2040-cars

Auto blog

What effect did Super Bowl ads have on online car searches?

Lexus's Super Bowl ad Let's Play starring an RC version of the RC 350 sliding around wasn't really a big hit among Autoblog readers, with a pretty miserable 13 down-votes as of this writing, compared to the winning Nissan spot with 52 up-votes. The Japanese luxury brand doesn't need to feel blue about the results, though, because in at least one metric the commercial ranks as the most popular of the night. According to Adweek analyzing figures from Kelley Blue Book, the Lexus coupe saw an astounding 1,820-percent increase in searches on the auto pricing site, more than any other vehicle advertised during the game. Viewers were apparently intrigued by the BMW i3 because the EV came in second place with a 1,131-percent jump. Third place went to the Mercedes-AMG GT with a 950-percent boost from its whimsical ad. The lowest growth for the night was from Toyota with a 20-percent upswing for the Camry. In terms of brand searches, the Kia James Bond-inspired spot brought a 68-percent increase in searches to KBB's website, according to Adweek. Dodge scored a close second with a 62-percent bump, and Fiat's humorous ad apparently resonated enough for third place and a 52-percent jump in searches. Despite the RC 350's popularity, Lexus actually ended up at the bottom of the list with just 6 percent more visitors looking for the company. To explain the weird discrepancy, a Kelley Blue Book analyst explained to Adweek that visitors came to the site specifically looking for the RC 350 and to a lesser extent the NX, which saw a 48-percent jump in queries, but that interest didn't extend to the whole brand. Related Video: News Source: Adweek Marketing/Advertising Lexus Coupe Performance Videos lexus rc lexus rc 350

Toyota offered $146.5 million to build Lexus ES in Kentucky

Toyota posted a media advisory yesterday saying that Akio Toyoda, president of Toyota, and Jim Lentz, CEO of Toyota North America, would be making a production announcement tomorrow in New York City, and Automotive News reports that the automaker will be announcing a plan to domestically produce the Lexus ES. According to the report, numerous plants are competing to build the ES in North America, and the State of Kentucky has offered the automaker up to $146.5 million to build the luxury sedan at the Georgetown, KY assembly plant.
If Georgetown gets the ES, which has been built in Japan since its debut in 1989, it would be built alongside the Toyota Camry, which is somewhat ironic since in our review of the 2013 Lexus ES350, we wrote that this ES finally says "goodbye to its Camry roots." In order to get the whole amount offered, the article states that Toyota would have to invest $531.2 million and hire 570 full-time workers at the plant, which doesn't sound all that unreasonable since the plant would require an additional 50,000 units of annual production, not to mention the fact that the Georgetown facility is already at its capacity for building the Camry.

Google shares more details on self-driving car accidents

Google has pledged to release monthly reports on the status of its self-driving car program, and says these updates will include information on accidents involving the vehicles. But the company won't release the actual accident reports, a sore point for activists who recently have clamored for the company to be more transparent in the way it tests this promising technology on public roads. "Google is dribbling out bits of information in the hope to silence legitimate calls for full transparency," said John Simpson, privacy director for Consumer Watchdog, a nonprofit that has asked Google to release reports from the 12 accidents the company says it has been involved in over the past six years. "They are testing on public roads, and the public has a right to know exactly what happened when something goes wrong." Under California law, the accident reports are not considered public records. Google has attributed all accidents to human error, and says drivers of the other cars involved caused 11 of the 12 accidents. In eight of those, the Google cars were rear-ended, and the autonomous vehicles were sideswiped in two other crashes. One of the accidents occurred at an intersection when a human driver failed to yield at a stop sign, and in one incident, a Google driver accidentally rear-ended another car while manually driving. Google had previously provided those details. The first monthly report installment sheds new light on which types of self-driving vehicles were involved, directions of travel, locations, and whether the cars were operating in autonomous or manual mode. Update: Google says this information comes directly from the OL 316 forms used to report accidents involving autonomous cars in California, though it has "edited the summaries lightly to protect other drivers' information." But Google still will not release the original OL 316 forms, nor the "traffic collision report" forms used in California to report accidents. Another company that has been involved in a single self-driving car accident, Delphi Automotive, has released this information, which verified its car was not at fault. Regarding Google, Simpson said, "We now know a few more details of what happened. The problem is that it's Google's version and they want us to take their word for it." The Google self-report adds information that goes beyond accidents, with further details on the company's overall program.