Advertisements
Announcing Verizon’s Star Wars Day Social Media Scavenger Hunt

Announcing Verizon’s Star Wars Day Social Media Scavenger Hunt

11182724_10155436797610123_3560347320726205168_o

VERIZON BRINGS THE FORCE TO FANS ON
STAR WARS DAY WITH #CAPTURETHEDROID SOCIAL MEDIA SCAVENGER HUNT

New Yorkers Invited to Find R2-D2 and the Jawas Who Captured Him
for Chances to Win High-Stakes Prizes

WHAT: Verizon is celebrating May the 4th, “Star Wars Day,” with a #CaptureTheDroid social media scavenger hunt brought to life in New York City. Beginning May 2nd, Verizon will begin dropping hints on @VerizonWireless, inviting fans to find the DROID Turbo by Motorola devices that are valuable to both The Empire and The Rebel Alliance. It’s up to fans to locate the DROIDs and save one for themselves before The Empire does!

In New York, fans will solve digital riddles and clues, leading them to secret locations across the city where R2-D2 and the Jawas that captured him can be found. The first two fans to find R2-D2 and the Jawas and deliver a special pass-phrase that they get from solving the digital clues will be awarded a DROID Turbo by Motorola phone and a trip to Comic Con in San Diego. Other Star Wars memorabilia will also be awarded to the next fans who find the secret location(s).

#CaptureTheDroid scavenger hunt will also live digitally for fans nationwide, as they are able to solve the video clues and riddles posted to Verizon’s social channels (Twitter, Facebook and Google+) and guess where other DROIDs are hiding throughout the United States. Winners will be entered into a sweepstakes for tickets to San Diego Comic Con, DROID Turbo by Motorola devices, Star Wars posters, memorabilia and more.

WHEN: “Star Wars Day” – Monday, May the 4th

WHERE: Live scavenger hunt in New York City

Nationwide via Verizon’s social channels (Twitter, Facebook and Google+)

Thank you to Verizon for the press release.

Powered by
Please follow and like us:
error
Advertisements
error

Enjoy this blog? Please spread the word :)

%d bloggers like this: