Deprecated: Optional parameter $function declared before required parameter $page is implicitly treated as a required parameter in /home/swalsh/public_html/wp-content/plugins/cron-view/plugin.php on line 201

Deprecated: Creation of dynamic property autoptimizeImages::$lazyload_counter is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php on line 34

Deprecated: Creation of dynamic property autoptimizeCompatibility::$conf is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeCompatibility.php on line 18

Deprecated: Creation of dynamic property autoptimizeCriticalCSSCore::$criticalcss is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeCriticalCSSCore.php on line 20

Deprecated: Creation of dynamic property autoptimizeImages::$lazyload_counter is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php on line 34

Deprecated: Creation of dynamic property Smush\Core\Modules::$webp is deprecated in /home/swalsh/public_html/wp-content/plugins/wp-smushit/core/class-modules.php on line 109

Deprecated: Creation of dynamic property Jetpack_Publicize::$modules is deprecated in /home/swalsh/public_html/wp-content/plugins/jetpack/modules/publicize.php on line 38

Deprecated: Creation of dynamic property Automattic\Jetpack\Publicize\Publicize_UI::$in_jetpack is deprecated in /home/swalsh/public_html/wp-content/plugins/jetpack/modules/publicize.php on line 101

Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91
Arsenal use Social Media to welcome new signing Olivier Giroud - Digital-Football.com - Football Social Media & Digital Sports news

Arsenal use Social Media to welcome new signing Olivier Giroud

The latest addition to Arsenal’s frontline last month was highly rated French striker Olivier Giroud, so to welcome the signing (and capitalise on social media), the North London team launched a #WelcomeOlivier Twitter competition.

Using the #WelcomeOlivier hashtag, Arsenal’s competition was very simple – tweet a welcome message to the new striker and potentially win a signed shirt from Olivier. However, the competition didn’t end there, the winning tweets also were placed onto a series of JPGs to be used as desktop wallpapers featuring Giroud in the Arsenal jersey.

Arsenal’s Digital Operations Manager, David Savage, told Digital-Football.com exclusively,

“At Arsenal we see social media chiefly as a set of tools for adding value to the fan experience.  Be it via leveraging our unique access to the club, creating an interface between fans and players or sourcing fan generated content to add a social layer to club activities. Social channels provide us with the means to engage with specific fan groups on the platforms of their choice.”

Arsenal currently lead the Premiership in terms of Twitter followers and rank a very respectable 3rd worldwide. The Gooners showed that social media doesn’t need to be complicated or at all time consuming. By encouraging fans to tweet on their hashtag, they were raising awareness of both the transfer and their own social media activity. Secondly, they used UGC (the tweets) to integrate it into their own content, thereby creating a stronger sense of affinity between brand and fan. Thirdly, they raised awareness for their Fanzone area of the website and drove web traffic there.

Consequently, the short Twitter campaign saw over 10k uses of the hashtag in 48 hours and the @Arsenal Twitter account had an increased follower rate of over 30% (more than their usual average growth).

As football social media continues to grow (even in the off-season), Arsenal also spoke to us about their future plans to expand their football social media activity,

“We’re constantly evaluating the landscape and looking to join fans wherever they’re active – something that will be reflected in our likely expansion onto new platforms in the coming months.”

This is a great example for clubs of all sizes into how they can very quickly utilise social media in order to engage with their fans and promote their offline activity. As we have continued to stress since this site’s beginnings – social media doesn’t need to be complex, merely fan focussed.

Have any more good examples of football social media? Leave us a comment or send us an email on sean [at] digital-football.com

Sean Walsh

Founder of Digital-Football.com and leading Football Social Media expert.

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *