We try not to use a lot of jargon in our platform or in our help documentation, but every company and sector has its own jargon. To keep us all on the same page, we've put together a glossary.
Admin: usually referring to 'org admins', admins are users with special privileges on the site. 'Org admins' are generally staff members at your organization who have full privileges over the site. (See also: Teams) Other types of admins include 'partner admins' and 'campaign admins'.
Admin Homepage: this is the starting page for most admin pages. It includes stats about your organization's platform usage, links to the help center, and ControlShift's Twitter feed. To access the admin homepage, click the down arrow next to your name and choose the "[Your Site] Admin" option. You can also go to [URL of your site's homepage]/org.
Admin Page: usually combined with a feature (e.g. petition admin page, effort admin page, etc.), this refers to the admin view of that piece of content. For example, a petition's admin page is accessible by clicking the Admin button on the petition's signature page. An effort's admin page is accessible by going to the Admin Homepage > Efforts > name of the effort.
Buckets: along with sources, buckets track where signatures are coming from. Unlike sources, buckets persist through generations. Imagine that you sent an email to your list asking them to sign a campaign and the link that you included in the email had a bucket code appended to it. Let's say that 5 email recipients clicked the link in the email and signed the campaign. One of them then shared on Facebook, 4 of his friends clicked on the facebook and signed the campaign. Your bucket would have 9 signatures because 5 came from the first generation (the email) and 4 came from the second generation (the facebook share). The bucket will continuing to track signature activity as long as people keep sharing the bucketed URL. Learn more about buckets.
Calendar: In ControlShift, a calendar is a collection of related events. Often calendars are used to organize days of action (e.g. a bunch of events events, organized around the same issue, happening across the country).
ChangeSprout Inc.: the legal name for the company that supports the ControlShift platform, TakeCharge, and VisitThem.
ControlShift: refers to the online, distributed campaigns/events/groups platform. Also used informally to refer to the company that supports the ControlShift platform.
Daisy Chain: refers to what happens after some signs a petition. Usually they'll be asked to share the campaign on social media, but org admins can override the default post-signing daisy chain. Learn more about changing the post-signing daisy chains.
Decision Makers: these are the people/organizations that can give your supporters what they're asking for in their petitions. As a feature, the decision makers feature allows the decision maker to be automatically updated about the campaign's progress. Learn more about the decision makers feature.
DPA: Data Processing Agreement. This is a legal contract that governs how ControlShift can use and process your data (including the data of your supporters and staff members). Our DPA is aimed at GDPR compliance, but it's available to any customer who wishes to complete it. You can complete the DPA online.
Effort: a feature that allows org admins to manage national or international campaigns with many local targets. The petitions included in an effort often share a common theme and common text, but have different local decision makers. Each petition within an effort generally has its own leader and its own petition.
Geographies (Geographic Regions):
Ham: Not the meat; when we say "ham" we mean the opposite of spam. Ham normally refers to petitions, events, comments, and messages that are from real people, are about real issues, and are not trying to sell movie downloads or prescription drugs. Learn about spam/ham.
Landing Page (feature): this is a feature that is similar, though separate, from the Efforts feature. Landing Pages allow admins to manage a national or international campaign with many local targets. All targets in a Landing Page are added by supporters, not pre-chosen by admins. Learn more about Landing Pages.
Landing Page (within an Effort or Landing Page): a public directory page for the petitions included in an effort or landing page. This is sometimes referred to as the effort/landing page's 'map page'. Learn more about landing pages.
Local Organizing Map: lookup page includes all known events (both ControlShift and external events) and ControlShift local groups. Customers who have completed our EU GDPR DPA will need to enable the Mapbox integration first. Then, the map is available by going to your site's homepage and appending
/local. For example: https://demo.controlshiftlabs.com/local.
Locale: a language. This generally refers to the language(s) that users can view your site in.
Markdown: this is markup language that allows text to be formatted (e.g. bolded, italicized, etc.). We support markdown for the what and why text of petitions in Effort and Landing Pages. You can learn more about markdown here. Learn more about using markdown in Efforts.
Member: interchangeable with user, signer, attendee, and supporter, this refers to someone – generally not organization staff – who has taken action on the site.
Moderation: the act of reviewing and choosing a visibility status for petitions, events, emails, and groups on the platform. Learn more about moderation.
Org admin: These users have administrative permissions on the platform. Generally org admins are members of the "Owners" team, meaning that they access to everything on the site. If the organization has created an additional Teams, then members of those teams will also be considered org admins, event if they don't have access to everything.
Partner Admins: usually members of a partner organization's staff, these users have advanced privileges over the petitions and events associated with their partnership. Learn more about partner admin permissions.
Partner's Management Tools: the special tools that partner admins have access to. With these tools, they can see a list of the events/calendars/petitions that are included in their partnership. They can also contact the people who have been added to their mailing list, and potentially export users from the platform. For org admins, this view is accessible by going to the partnership's hub page . Learn more about the partner manage page.
Partnership: a feature that allows an organization to work with another organization to run campaigns/host events. Partnerships are created by org admins. Learn more about partnerships.
Region: a geographic shape that's used in 'turfing'. Organizations can send ControlShift a kml or kmz file that allows the organization to divide their country of focus (or the world) into separate regions. Petitions/events/groups can then be automatically assigned to those regions. Admin teams can also be region-restricted and will only be able to see content assigned to their region.
RSVP: a French phrase that's used in English. In French, this means "Répondez s'il vous plaît." In English, this is both the action of saying that you will or will not attend an event, and the response itself. A Yes RSVP means that you're attending the event. A no RSVP means that you're not attending the event.
Segment: generally refers to Segment.com a third-party service that allows organization to send platform data to various analytics services using one code. This is an optional integration. Learn more about Segment + ControlShift.
Slug: A slug is a unique part of a page URL (generally found at the end of the URL) that refers a site visitor to that specific piece of content. For example, if a petition has a url of: https://demo.controlshiftlabs.com/petitions/repair-the-yellow-brick-road-1, that petition's slug is
repair-the-yellow-brick-road-1. Slugs are also used to identify other content on the platform, like partnerships, events, groups, efforts, etc. For example, a partnership whose public-facing page is: https://demo.controlshiftlabs.com/partnerships/frack-free-moon has a
frack-free-moon slug, and an effort at: https://demo.controlshiftlabs.com/efforts/ban-fracking/lookup/new has a
Sources: sources allow you to track where signatures/RSVPs/petition creation is coming from – e.g. Facebook/Twitter shares, email blasts, etc. For signatures and petition creation, the platform automatically tracks some sources, but org admins can also track custom sources. Learn more about signature sources. Learn more about petition sources.
Spam: not the "meat"; spam is a moderation status that designates the petition, event, comment, or message as not legitimate. Instead it's being used to sell movie downloads, prescription drugs, etc. The spam designation is sent back to our spam filter and teaches the filter what to look for in the future. Learn about spam/ham.
Teams: the teams feature allows organizations to set granular permissions for different groups of users.
Themes: themes control the appearance of your site, including fonts, colors, logo, and header/footer links. Many organizations have one theme that matches their organization's style guide. However, organizations can create multiple themes per instance. These additional themes can be used for partner content, specially-branded events related to a day of action, specially-branded petitions to match a microsite campaign, etc. Learn more about themes.
UTM Parameters: codes that can be added to certain petition and event page URLs that track where traffic is coming from. Learn more about UTM parameters.
VisitThem: another tool for progressive organizations supported by ChangeSprout. VisitThem allows organizations to create campaigns asking their members to make in-person visits to their Members of Congress. Learn more about VisitThem.