how to build an integrated digital engagement platform with drupal
DESCRIPTION
TRANSCRIPT
OHO Interactive
Presented by John Money and Jeremy Duffy, OHO Interactive
October 2013
How To Build an Integrated Digital Engagement Platform With Drupal
What You’ll Learn To Do
๏ Build a multi-channel digital engagement platform
๏ Tightly integrate third party applications in the cloud
๏ Create an infrastructure that is scalable and flexible
Integrated Platform
๏ Websites๏ mittromney.com๏ dozens microsites
๏ Mobile apps ๏ iPhone, Android native๏ m. main site
๏ Email๏ Social Media
๏ Facebook๏ Twitter
Integrated Platform Components
Customer Data Warehouse
Salesforce User Integration
๏ Average 1,000+ new users/hour as high as 20k/hour
๏ Choose the right API๏ SOAP๏ REST๏ Bulk
๏ Hourly batch updates๏ Processing off of production
servers
Salesforce Webform Integration
๏ Sign-up without account creation
๏ SFDC relationships๏ Contacts๏ Campaigns
๏ REST API๏ Custom triggers
developed on SF
Direct Marketing
One Click Donations
๏ Saved from website๏ One click from email๏ One click from SMS
API Work (Donations)
Use the Drupal APIs
๏ Piryx donation was 100% form API
๏ Campaign entity objects to store default values๏ OAuth provisioning
๏ Donation submission data not stored๏ Database of record Piryx
Social Integration
Social Login
๏ Account registration were KPM
๏ Gigya Connect was originally used
๏ More streamlined user experience with native OAuth
Social Graph (FoF)
๏ Crowd effect๏ Personal brand
improved conversion rate
Facebook App
๏ Facebook Voter registration app
๏ Powered by Drupal Webform
Open Graph Actions
๏ Leverage Drupal Open Graph (Meta Tags)
๏ Extended for custom messaging on Facebook, Twitter๏ Beta access to
Twitter Cards
Mobile Integration
Mobile App Development๏ Native mobile apps๏ Data powered by Drupal
XML feeds๏ OAuth API for mobile
login/registration
Mobile site๏ m. site featured most
interactive portions of main site
Live Event Integration
Eventbrite
๏ Free tickets to rallies, meet-ups, and local events
๏ Over 1,000,000 tickets issued๏ Captured supporter
information and email๏ 1/3 Registrants were new
๏ Geo-search for events
Microsites
Same code base, different theme
๏ Multi-site installation ๏ Optimized theme๏ 24 hour role out๏ Database considerations๏ To share or not to share
Architecture and Process
System Architecture to Scale๏ Cloud used to scale up quickly๏ To support both more users and more applications
๏ Acquia and Amazon AWS hosted Drupal๏ Dynamic host scaling
๏ Akamai ๏ Content Delivery, DDOS, failover with NetStorage
๏ No single point of failure and multiple fail-back systems๏ Other providers for apps, notifications, SMS, payments,
etc.๏ Almost daily DDOS attacks
Drupal - Iterative Code Review
๏ Agile development, mainly twice weekly releases๏ Empowered release engineer to pass/fail features
๏ Used Jira to drive automated release
Performance Management๏ Intense perf dev - 10x improvement๏ From choking on 4,000 in June to thriving on 45,000 in October
๏ Combined automated testing with New Relic tools๏ Found scale problems in common modules๏ Added new features including resource intensive geo search๏ Two developers become speed ninjas
Questions?