Which Brand Won Veganuary? Consumers Give Their Verdict
By Leia ReidJan 24
A dramatic episode seven sent Twitter into meltdown.
In one of the highest performing episodes on Twitter since the series began, here’s the social data review.
**SPOILER ALERT: We won’t go into the details of what happened but unlike in most of our social data reviews this week’s contains a fairly unavoidable and fairly big spoiler. If you want to avoid that, we’d suggest coming back later.**
The overall mention volume for the hour long episode hit 76,000 this week, making it the highest performing episode since the dizzying heights of episodes one and two.
The biggest spikes occurred in the early scenes, with volumes at one point hitting 4,000 per minute.
Without ruining anything, something fairly significant happens in the later scenes and we’d have expected a far higher spike here, but perhaps viewers were glued to their screens so much that they couldn’t look away to tweet.
To be fair, though, the mention spike at 9:53 of 2,220 tweets was higher than any peak from episode six.
**This is your second warning. Spoilers are coming**
Usually, the most mentioned character doesn’t necessarily reveal what happens to them, just that they have a significant impact on the episode. Kind of like when Hodor was the top mentioned character in episode five.
But this week, there’s no getting around the spoilers. The top mentioned person is someone most people thought was long dead.
That might explain the mention spike at the beginning of the episode…
You can play with our Game of Thrones data, spanning all the way back to season one, in our interacting data viz here.
These were the top retweeted reactions throughout the episode. @GoT_Tyrion‘s tweets, as usual, were on point.
— Tyrion Lannister (@GoT_Tyrion) June 6, 2016
— meredith elyse (@worstnightmere) June 6, 2016
Other top shared tweets pointed to the fact that the episode seemed shorter than usual.
— Kait Calabrò (@KaitCalabro) June 6, 2016
What did you think of episode 7?
Are you a journalist looking to cover our data? We’ve got plenty more. Email us: email@example.com