Voter Registration

Overview

We partner with Rock The Vote to register young people to vote on behalf of DoSomething.org, by redirecting to them to the Rock The Vote (RTV) registration website and appending our partner ID: https://register.rockthevote.com/registrants/new?partner=37187

Our importer app, Chompy downloads all voter registrations created with our partner ID, and imports them as voter-reg posts by posting to the Rogue API. See import docs.

Voting Portal

We host our voting portal, vote.dosomething.org on Instapage. It prompts user for their email and zip, and redirects them to the Rock The Vote registration URL with our partner ID, pre-populating the email and zip submitted from the form.

TODO: Link to doc about why we host on Instapage / Phoenix limitations

Voter Registration Action

The VoterRegistrationAction content type can be used to display a call to action button that redirects a user to our vote.dosomething.org portal.

Online Registration Drives

The call to action in the Ready, Set, Vote campaign asks a member (the alpha) to get their friends to register to vote, by providing them with a custom URL to their own Online Voter Registration Drive (OVRD) that they can share with their friends (the betas).

Current version

The campaign action page (aka the alpha page) uses a SocialDriveAction to customize the query parameters of the beta page -- which is hosted on our Instapage voting portal at https://vote.dosomething.org/member-drives.

An example complete custom link for an alpha with user ID 58e68d5da0bfad4c3b4cd722 will look like:

https://vote.dosomething.org/member-drive?userId=58e68d5da0bfad4c3b4cd722&r=user:58e68d5da0bfad4c3b4cd722,source:web,source_details:onlinedrivereferral,referral=true

Upcoming version

In May 2020, we will release updated versions of both the alpha and beta OVRD pages.

Alpha page

The OVRD (Ready Set Vote) campaign action page will still be used as the alpha page, except we render a hardcoded template instead of the Contentful blocks field. This is hardcoded because it displays one-off features, such as a list of the beta's that the alpha has gotten to register to vote via their OVRD, that we don't need to make re-usable by other campaigns or pages at this time.

We hardcode specific configuration ContentBlock ID's and Action ID's:

Production:

Content:

• How To Share ContentBlock - 3fj7mXlyrcJZ3mUKXqco1R

• FAQ ContentBlock - 1nLV3YUhLzJdlcGrd2Mq9N

Total scholarship entries:

• Share Photo Post Action - 1025

Dev:

Content:

• How To Share ContentBlock - 1xcG1CTinKwn3Iyxtcc0f4

• FAQ ContentBlock - 6H22Y1wmICy05pM9twIGGR

Total scholarship entries:

• Share Photo Post Action - 27

Beta page

We'll host the beta page internally in Phoenix instead of Instapage, at path /us/my-voter-registration-drive?referrer_user_id=58e68d5da0bfad4c3b4cd722 (where the referrer_user_id is our alpha's user ID).

This beta page is a hardcoded template, but shares some components with the OVRD campaign template, like its CoverImage and scholarship information. The OVRD campaign's contentful ID, 3pwxnRZxociqMaQCMcGOyc, is the same in all of our dev, qa and production spaces. Usually this isn't the case -- our Contentful ID's don't match between our dev and production spaces -- but this entry was created before we introduced different Contentful environments to our Phoenix space. Because of this, we're able to hardcode this Contentful ID to use in both dev and production environments.

Tracking Source

TODO: Document how the r query parameter is used by the Chompy import.