Pages Overview¶
What is a page?¶
Pages in ActionKit generally correspond to web pages, where your users can take an action. ActionKit doesn’t offer content page types, only action pages. For most groups, it makes sense to maintain and host the home page of their website outside of ActionKit, linking from there to ActionKit Pages for advocacy, fundraising, events and other member engagement.
You direct users to your Pages to express support for your position, lobby decisionmakers, donate, sign up for events, and more. Pages capture data about those actions and your users.
Pages are also how users get subscribed to your mailing list so you can email them through ActionKit. By default, anyone who takes action is added to the mailing list you associate with the page. To maintain good email deliverability, your page should clearly indicate this, so users aren’t surprised when they receive email from you.
You can customize just about everything about your page, from the appearance, to the user form fields, to user specific content. You can host your pages with us, using our mini-CMS to enter your page content, or you can host your page externally, using another CMS.
Pages are broken down into Types to give you quick access to features specific to the page’s purpose.
How do I add a page?¶
From the Pages Tab, you can create a page from scratch or starting from a model.
To create a page from scratch, click Add Page, and select the Page Type from the dropdown. To create from a model, click Page From Model and then select the model. The latter only works if you already have a model for the page type you want to create.
You’ll land on the Action basics screen.
At the top is a link to the History, which will list all changes made to this page.
There are four steps for creating a page of most types:
Action basics - Create the page and set basics like the name, tags, and type-specific info like advocacy targets. This is all information required for action processing, regardless of where you’re hosting the page.
Edit content - Select a Templateset to define the page’s appearance and customize the user form. Enter content, or if you indicate that you’re hosting the page on your own servers, we’ll put some filler in for the content.
After-action info - Define everything that happens after the user submits (again, regardless of where the page is hosted) including the landing page, thank you email, tell-a-friend and social media sharing, and after-action notifications.
View on site - Proof and test the page. If you selected the checkbox to host your own page, this step is called Preview/get HTML and you’ll see a button to download the HTML.
Petition and Letter pages have an additional step for setting up automated signature delivery. Whipcount pages have one additional screen for whipcount results. For events, you must create an Event Campaign, then the steps above are used to create Host and Attendee Pages.
What are the page types?¶
ActionKit walks you through the process of creating Pages based on Type, streamlining the process and incorporating best practices. The Types are:
Petition – Petition Pages are generally used to petition an advocacy target on a specific issue or campaign. Users can add a personal comment but they cannot edit the statement. Petitions support one-click signing.
Letter - Letter Pages are similar to Petition Pages, but the user is encouraged to edit the letter you provide or write their own. Also, one-click signing is only available for petition pages. Letter pages are designed to encourage the user to customize the content, so you want the user to land on the screen with the content.
Call – Call Pages ask the user to call an advocacy target, generally to lobby them on an issue. These pages display the target phone number and ask the user to indicate whom they called and how it went.
Whipcount – Whipcount pages are a version of call pages that allow you to track the positions of a set of targets. A typical whipcount would target a small set of legislators who are either undecided on an issue, or hold key positions in the legislative process. Whipcount pages do not rely on a user’s address to determine targets. The user sees the full list of targets, selects one to call, then sees a form with the target’s phone number, instructions, and a contact form (unless the user is already recognized). The user calls and records the target’s position on your issue. Once enough users have confirmed a target’s response (based on your settings on the Whipcount Responses screen under User submitted), that target shows as confirmed so the next user can call a different target.
You can also use whipcount pages to generate thank and spank calls to targets.
Letter to the editor (LTE) – LTE Pages ask users to compose an original letter to the editor of a local, regional, or national newspaper. The user first selects a newspaper from a list, then composes a user, then submits. ActionKit emails the user’s letter to the editor for the relevant paper using data from a third party database. A user can only submit once for any given paper from an LTE page.
Survey – Survey Pages provide one or more questions for your users. Use surveys to get input on a specific campaign or to track opinions about your organization over time or for anything where you want input. You can provide your users with selectable answers in any format or provide space for users to enter their own free form responses.
The results are available for download as a CSV by clicking the Download Actions link on the Reports Tab.
Event – Events are usually (but not always) used to organize off-line gatherings for advocacy, team-building, public education, etc. To create an event you first create an Event Campaign, which has multiple pages associated with it, including a page where hosts sign up and one where attendees sign up.
Donation – Donation Pages ask your users to contribute, order Products, or support Candidates (through bundled contributions) using a credit card, PayPal, or ACH direct debit.
To accept credit card donations, you must have a payment account set up with a merchant vendor we integrate with. You can accept recurring donations and donations in many currencies.
To accept PayPal donations, we need information about your PayPal Account.
To accept ACH direct debit, you need a merchant account with Braintree and you must sign up for their ACH beta program.
You can also manage donations through ActionKit.
Update Recurring Donation - From pages of this type, users with existing recurring donations can update the amount of their recurring donation or update their credit card number, bank information (for ACH direct debit donations), or billing address. The billing address is prefilled from the last saved billing address for this recurring profile, and changes to the billing address are only available for Braintree, Authorize.net and PayFlowPro accounts. Users cannot update the billing address for PayPal accounts.
The update page also includes a link to the cancel recurring donation page.
If you have more than one merchant account, your page will automatically use the correct one for the user’s recurring profile.
The template for changing the layout or appearance of this page is Recurring update.
Cancel Recurring Donation – This Type allows users with an existing recurring donation commitment to log in and cancel the commitment. The user cannot request refunds for past payments from this page.
The template for changing the layout or appearance of this page is Recurring cancel.
Signup – Signup Pages are the most basic Type. You can use them to add users to a mailing list or associate them with a Tag.
Unsubscribe – Unsubscribe Pages allow your users to ask not to be sent future mailings. Once a user is unsubscribed you can’t email them from ActionKit.
Users can also ask to be removed from particular mailing lists, however, your page must make it possible to unsubscribe from all mailing lists with one click. If they’re following a link from an ActionKit mailing (e.g. they have an AKID), they must be recognized and cannot be asked to enter their email address.
When a recognized user lands on your unsubscribe page, they see a checkbox for each list they belong to, as long as your template set is based on the Original. All the boxes will be checked by default. The user can simply submit to unsubscribe entirely. If the user unchecks all the boxes and then submits, the same thing happens - the user is unsubscribed from all lists. Only if the user leaves some boxes checked do they remain subscribed to any mailing lists.
In your own templatesets and offsite pages, you must maintain this type of approach – either pre-selecting all the lists or providing a prominent remove-from-all-lists option at the top of the screen. Although you may lose a couple users who would otherwise have checked only some of the lists, this is a minor price to pay for maintaining good deliverability. If a user thinks they unsubscribed entirely, but forgot to check a box and therefore receives an email, they may become angry and complain to their ISP, which is very damaging to your email reputation.
Account Tools – You can also create several account screens where your end users can manage their own profile, including the user update and password screens. You can only create one version of each screen.
Import Pages - This page type doesn’t correspond to a user-facing web page. Import Pages are used to add users, actions, or user data to your database from a CSV file. Add these Pages from the Pages Tab or the Users Tab.
What are the options for hosting my page?¶
You can host your page with ActionKit or on your own server. Either way you can access all the same functionality - your end users will be recognized, error messages returned, data submitted to the database, Confirmation Emails sent, etc.
To host a page yourself, you need to copy some code into the HTML on your server. Select the Host outside ActionKit box on the Edit content screen when you create your page. Then view the source and download the code from the Preview/Get HTML screen.
When you check the box, we prefill some generic content in the text boxes. If you want the correct content to be included in the code you download, just overwrite the filler. Otherwise, skip the text boxes and enter your text in your own CMS.
We also display a URL field. Enter the URL for your page and we’ll hook it up to the View link on the Pages Tab.
Read more tips and suggestions in the embedding section.
How do I customize my page’s appearance?¶
Customize the look and feel of your Pages using Templates. Our templating system separates the graphic design work of creating pages with your organization’s style from the campaign work of setting goals, crafting your message, and creating content.
Templates define everything about the appearance of your pages from your page layout and colors, to the fields displayed in your user forms and the image for your thermometers. Each Page you create in ActionKit combines input from multiple Templates.
A Templateset is just a group of all the available Templates; each ActionKit Page combines input from multiple Templates.
To set a Page’s appearance you just select the appropriate Templateset from the dropdown on the Edit Content screen.
How can I personalize what a user sees on my page or in my thank you email?¶
Snippets are click-to-insert template tags used to display information specific to each user within the text on your Pages and in mailings.
For example, if you wish to identify the user by name on a page or in a mailing, you would expand the User header under Snippets and select First name. The following Snippet of code will be inserted into your HTML:
{{ user.first_name|default:"Friend" }}
ActionKit can only display conditional content for recognized users. Users who aren’t recognized will see the default value defined for the specific Snippet. For example, if you insert First name an unrecognized user will see the default, 'Friend'. You can change the default value by typing over it when you insert it, but not universally for the Snippet.
Some Snippets don’t have a default value and you’d generally only want to use them in cases where the users who will see them have a value for the field. For example, it only make sense to use the average donation Snippet with past donors.
Note
Always view your page as a recognized user to make sure your Snippets are displaying as you’d expect.
The Snippets available for Pages are slightly different than those available for mailings, including the Confirmation Email. View the Snippets and the code they insert for Pages and mailings. You should be able to insert these available snippets anywhere on your page, including the page title.
You can define your own custom snippets to make it easy to insert frequently-used bits of text and code into your pages and mailings.
How do I create pages in other languages?¶
There are a few things you need to do to create a Page in a non-English language, and if you’d like, to hook it to other translations.
You need to have added your language.
Then when you create your Page, select the language on the Action basics screen. All users who take action on this page will have their language preference set to the selected language. If you’d like existing users’ language setting to remain as it is, select "——–" from the drop down.
Also, your Page will use the default Templateset for the language (although you can select another one instead).
If this is a translation of another Page, you can associate it with the other versions by selecting a Multilingual Campaign. All Pages that share the same multilingual campaign are treated as one Page for reporting and by the thermometer if you’ve selected a goal.
Pages with a Multilingual Campaign display links at the top right of the Page so users can toggle to the language they prefer.
Note
For Donation Pages, the multilingual campaign feature allows you to group Pages with different currencies, but the language picker won’t be shown unless the Pages actually have different languages, and public-facing thermometers will only include donations in one currency.
Enter your content in the appropriate language on the Edit content screen and the text of the Confirmation and TAF Emails on the After action info screen. ActionKit will pre-select the default Email Wrapper for the language for your Confirmation Email.
How can I see what my user sees when they view my page?¶
When you follow a link in Pages to view a page, you see what the page will look like for a user who isn’t recognized. Most often an existing user will follow a link in an email from you to reach your page and ActionKit will recognize the user.
For most basic testing, you don’t need to view the page as a recognized user. But here too, when you’ve got a new templateset or you want to test something specific, you may want to see what a recognized user will see.
You have two options:
You can create your draft email and send yourself proofs. Follow the link to the page in the proof to view the page as the user specified in the to line of the proof mailing.
Or
Search for the user by name or email or other criteria from the Users tab. Click through to the user record. Copy the akid shown under the user name. Return to the URL of your page. At the end of the URL, after the final "/", append “?akid=” and paste the token. The URL will look like: “http://docs.actionkit.com/?akid=.1.qgzMpW”. The page will show what this user will see if they follow a link to the mailing. You can repeat this for as many users as you’d like.
In either case, you should be careful submitting. ActionKit thinks you are the recognized user, so if you submit, an action will be recorded in the recognized user’s name and they’ll receive a Confirmation Email if you’ve set that up for the page.
If you want to view the Snippets on the thank you screen or a Confirmation Email for a user aside from yourself, it’s best to do that as another staff user.
Unsubscribe Pages¶
What do the options on this screen mean?¶
Action Basics Screen¶
Title, Name, Notes¶
Enter the title the user will see at the top of the web page.
Edit the short name if you don’t want to use what is auto-generated from the title. This forms part of the URL for this page. Only use letters, numbers, underscores, and dashes. No spaces or other characters.
For example, the URL for a signup page is http://docs.actionkit.com/signup/your_short_name/.
Use the Notes field to associate information with a page for internal use. Notes are displayed on the Pages Tab and Browse All screen.
Language¶
This option is only relevant if you’ve set up Languages aside from English in your instance. If so, the additional Languages will show here in the drop down under More Options.
Select a Language to:
Save this as the user’s language for any user who takes action on this page.
Use the translated system messages (e.g. “Email is required”), if you added these when you set up the Language.
Tell ActionKit to pre-select the default Templateset for the Language on the Edit content screen and to pre-select the default Email Wrapper for the Language for your Confirmation Email – if you’ve set defaults for these.
If you don’t want the user’s language to change because they took action on this page, you can select '———' from the Language list.
To learn more about ActionKit’s Language functionality, including how to add Languages and translate error messages see Languages and Multilingual Campaigns.
Multilingual campaign¶
Multilingual Campaigns allow you to associate multiple Pages with each other for tracking and reporting. If you’ve selected a Goal, the thermometer for Pages that share the same Multilingual Campaign shows the combined results.
Also, your end users will see links at the top right of the page so they can toggle to their preferred Language.
You can add a Multilingual Campaign from the Pages Tab or from the Multilingual Options section on the Action basics screen when you’re creating a page.
Create a Multilingual Campaign for each Page that you plan to translate. Then select the Campaign and the Language when you create each translation.
On the Pages Tab, if you click the grey Multilingual Campaigns link, you’ll see summary information for each Campaign including the count of action takers and a list of the Pages showing each Language.
Spam checks¶
Only relevant if you’ve enabled spam checking. Use this to tell ActionKit not to apply the checks to this page.
Is model¶
You can mark a page as a Model, as you can a mailing, and use it as the basis for future Pages of the same type.
Models can be used to save standard text you include in the Confirmation Email or the tell-a-friend message for Petition Pages, or to save your most commonly used Donation page settings, or as a shortcut for creating C3 versus C4 Donation Pages with the appropriate page wrapper, merchant vendor account, Email Wrapper and From Line.
When you copy a Model, all the settings remain the same, except the copy is not marked as a Model.
Designate your Model by checking the Is model box on the Action basics screen under More options.
Click on the light gray Models link at the top of the page list on your Pages tab to see a list. Or use the filter options on the Browse all screen.
Model pages do not work differently than other pages. Users can still submit on a Model page, if you make the URL public.
Note
Only users with the Pages - plus Model Pages permission and superusers can create and edit model pages. The checkbox to designate a page as a model will not show up for other users.
Use in mail wrapper¶
One unsubscribe page will be used as your organization’s default, which means it will be automatically included in email wrappers. You can link to a different unsubscribe page by editing the wrapper or you can change your default unsubscribe page. All wrappers must link to an unsubscribe page.
Just select Use In Mail Wrapper under Unsubscribe Options on the Action basics screen for the page you want as the default. This will replace whatever page was previously selected as your default unsubscribe page.
Page fields¶
Custom page fields are a powerful and flexible tool that allows you to add a section of content or code to an individual page.
For example, if you want to ask users to tweet about an action they’ve taken, you could add a page field called "twitter" and include a suggested message specific to the page. If you have a Protect Parrots petition your sample message might be “Parrots are smart. I just signed to save them here: action_URL”
Page fields you’ve created are available on the Action basics screen for each page.
Note
If you don’t see a Page fields section on this screen, no custom page fields have been created for your organization.
Use this syntax to include page fields in your templatesets or to reference them when creating a page: {{ page.custom_fields.YOUR_FIELD_NAME_HERE }}. Or, if your custom page field contains template tags or filters that need to be interpreted, then use this syntax instead: {% include_tmpl page.custom_fields.YOUR_FIELD_NAME_HERE %}.
Edit content screen¶
Templateset¶
Customize the look and feel of your Pages using Templates. Our templating system separates the graphic design work of creating pages with your organization’s style from the campaign work of setting goals, crafting your message, and creating content.
Templates define everything about the appearance of your pages from your page layout and colors, to the fields displayed in your user forms and the image for your thermometers. Each Page you create in ActionKit combines input from multiple Templates.
A Templateset is just a group of all the available Templates; each ActionKit Page combines input from multiple Templates.
To set a Page’s appearance you just select the appropriate Templateset from the dropdown on the Edit Content screen.
Unsubscribe pages use the unsubscribe template.
Host Outside ActionKit¶
You can host your page with ActionKit or on your own server. Either way you can access all the same functionality - your end users will be recognized, error messages returned, data submitted to the database, Confirmation Emails sent, etc.
To host a page yourself, you need to copy some code into the HTML on your server. Select the Host outside ActionKit box on the Edit content screen when you create your page. Then view the source and download the code from the Preview/Get HTML screen.
When you check the box, we prefill some generic content in the text boxes. If you want the correct content to be included in the code you download, just overwrite the filler. Otherwise, skip the text boxes and enter your text in your own CMS.
We also display a URL field. Enter the URL for your page and we’ll hook it up to the View link on the Pages Tab.
Read more tips and suggestions in the embedding section.
Content¶
The content for your pages is entered here. The text boxes for all page types share the same basic functionality.
WYSIWYG¶
Most everywhere that you can enter and edit text (e.g. page content text boxes, mailing body), we’ve provided a basic WYSIWYG editor (TinyMCE) and a syntax coloring editor (CodeMirror) as well as the standard browser text area.
Select Visual to use the WYSIWYG editor and view the rendered content without writing your own HTML. The toolbar has buttons you can use for standard functions and formatting. Just hover over the tool to see the name. For example, you can click to indent a paragraph or to insert an image. The show/hide toolbars button opens a second bar with additional formatting options.
Select Code in the toolbar to have color-coding and line numbers for easier editing of the code. Different elements, like Javascript or CSS, are given different tinted backgrounds or text colors.
Select Plain to remove all highlighting.
Note
The visual editor, like other WYSIWYG editors, may at times add more than you expect to the HTML, like extra <p> tags, and at other times, strip out things, like styling. You may want to avoid the visual editor when updating code-heavy items such as mailing wrappers and templatesets, and limit the use of the visual editor to areas that are more content-heavy, like page text and mailing body content.
Spell Check¶
We’ve made it possible for you to enable your browser’s native spell checking when using the WYSIWYG visual editor, at least for most major browsers. The keyboard shortcut, menubar command, or context menu option required to enable spell checking is different in each browser, but typically you can right-click (or control-click, or two-finger-click) on an editor panel to reveal the ‘Spelling’ or ‘Spelling and Grammar’ commands for it. Firefox users may have to begin by selecting ‘Install Dictionary’ to enable spellchecking the first time, if they have not already done so. This enables ‘check spelling as you type’ functionality in Mac Safari, Chrome and Firefox as well as possibly Windows for Chrome, Firefox and IE 10+.
Snippets¶
Snippets are click-to-insert template tags used to display information specific to each user within the text on your Pages and in mailings.
For example, if you wish to identify the user by name on a page or in a mailing, you would expand the User header under Snippets and select First name. The following Snippet of code will be inserted into your HTML:
{{ user.first_name|default:"Friend" }}
ActionKit can only display conditional content for recognized users. Users who aren’t recognized will see the default value defined for the specific Snippet. For example, if you insert First name an unrecognized user will see the default, 'Friend'. You can change the default value by typing over it when you insert it, but not universally for the Snippet.
Some Snippets don’t have a default value and you’d generally only want to use them in cases where the users who will see them have a value for the field. For example, it only make sense to use the average donation Snippet with past donors.
Note
Always view your page as a recognized user to make sure your Snippets are displaying as you’d expect.
The Snippets available for Pages are slightly different than those available for mailings, including the Confirmation Email. View the Snippets and the code they insert for Pages and mailings. You should be able to insert these available snippets anywhere on your page, including the page title.
You can define your own custom snippets to make it easy to insert frequently-used bits of text and code into your pages and mailings.
After-action info screen¶
Redirect URL¶
In the Required section, you’ll see the URL for the thank you page with the text you entered in the previous step. If you’d like to direct the user to a different page, enter the URL here.
The URL is always pre-filled, but you can change it if you’d like to direct users to another page instead. Just enter the URL. For example, you might want to have your users land on a Donation page after they sign a Petition.
If you change the redirect, be sure to submit from your page to confirm that you entered the URL correctly.
You can use snippets in your redirect url. This is a convenient way to send users to specific follow-up URLs based on how they filled out your form, or include dynamic parameters from the action or other data.
Snippets available here are those associated with the action taker and the action, like {{ action.order.total }}. Or, if you have a custom field named, say, donations_2024, the snippet would be {{ user.custom_fields.donations_2024 }}. You can also reference parameters from the original page URL via {{ args.<name> }}. This allows you to do things like pass along parameters from a URL in a mailing to a follow-up donation page. Be sure to test your pages extensively when using this feature. Invalid URLs or broken snippets will redirect to the standard thank you page.
Alternate approach: Using a hidden input on the page with the name redirect and value of a URL will override the redirect URL you entered.
See How do I pass a source code through to a redirect? for more on the hidden input approach.
Confirmation email¶
The Confirmation Email usually thanks the user for their action.
You can use Snippets to insert conditional content. To include a Snippet in the subject, cut and paste the Snippet from those available for the body.
There’s a Snippet that allows you to include the user’s response to any survey questions (aka action fields). The syntax is action.custom_fields.QUESTION_NAME. You can only do this for survey questions that are on the page associated with the Confirmation Email.
Note
Sometimes you’ll want to include a link to a higher-bar, or more difficult, action the user can take. For example, a Petition page Confirmation Email might thank the user and ask him or her to call their legislator about the same issue. To do this, you need to create the second action page (the Call page in this example). Then enter the link to the second action in this email and in your Thank you text box on the Edit content screen.
Your Confirmation Email must include an unsubscribe link. Not many users unsubscribe as a result of the thank you email, but offering that option contributes to your standing with the various ISPs.
To create your Confirmation Email you need to:
1 Select the Email wrapper from the dropdown list. Wrappers define the header and footer of your email. See creating email wrappers.
2 Select the Email From Line entry from the dropdown list, add a new From Line, or fill in a From Line for use in this mailing only by clicking “use a custom From Line”. See From Line.
3 Enter your Email subject.
4 Enter your Email body.
Notification emails¶
Notifications are emails to someone aside from the action taker, prompted by actions on the Page.
You can use these for a variety of purposes including:
sending an email to the honoree about gifts made in their honor,
alerting field organizers to each new event created in an event campaign,
notifying a campaign director every 1,000 new actions on a page,
emailing your development staff for each new recurring commitment.
Create your notifications and then select the ones you want to associate with each page on the After action info screen. Each action can prompt multiple notification emails.
Notification emails will only send if there are values for the subject line, to emails, from email, and mailing body. So you can use conditional content to control whether the notification requirements have been met. You can also use a custom reply-to email address for your notification email to reply directly to the user who took action.
Warning
Blank mailing bodies may still have <p> tags and comment code that process as content. To block sending, use {% requires_value foo %} in the body, or use a conditional in the subject, to email, or from email.
We provide a few sample notifications that you can use or customize:
In honor of: This example shows how you’d prompt a notification email to the honoree after each gift in his/her honor. First you need to add an action field with the label ‘action_in_honor_of_email’ to the Donation Page template you’ll be using. Then you can use the to line in the example – {{ action.custom_fields.in_honor_of_email }}. The example also shows some conditional content you might include in the notification email by adding additional custom action fields to your template.
Tell staff about monthly donation: In this example, the subject includes the criteria to prompt the sending of the email. Whichever staff you select from the list or enter in the “to” line will receive this notification after each new monthly donation is created. The body includes some conditional content.
Notify every 1000: In this example, the send criteria is in the body and the subject includes conditional content.
Here are some other examples that aren’t included in your instance but that you might add:
Notify someone when a donation is greater than $250:
Subject: {% if action.order.total > 249 %}New $250+ Donation!{% endif %}
* Notify event hosts of new attendees:
To: {% for host in action.event.hosts %}{{ host.email }}{% if not forloop.last %},{% endif %}{% endfor %}
Subject: Subject {{ user.first_name }} has RSVPed for your event
Read about adding notifications.
How should I test my page?¶
As soon as you save a page in ActionKit it’s "live", meaning any user who ends up at the URL can see the page and take action. Of course, users generally don’t find a page unless you’ve shared it by sending an email or linking to it from your website or sharing it on Facebook or another public forum.
Always test a page before you share it with your users and again if you make changes.
A basic test plan for unsubscribe pages follows.
If you have multiple mailing Lists, we suggest running additional tests as a recognized user.
You may want to do additional testing for specific cases.
If you’re using a new, untested templateset, your testing should be more extensive and involve multiple browsers. Read about templateset testing here.
For most page types, when you test your page, your actions are recorded just as your user’s actions are. You can confirm that the data you entered was recorded in the database.
Finally, you may want to check optional elements you’ve included like snippets and taf.
Where can I find unsubscribe data?¶
The Unsubscribe Reasons report shows comments left by users in response to the question 'Why are you leaving?', if your page includes that. The results are stored in a custom action field associated with the unsubscribe action.