Secondary card actions
In addition to the primary action options you design into your card templates, such as buttons, links, forms and rich media, action cards offer your users a number of secondary options.
Secondary action options such as the ability to snooze cards, dismiss cards and provide feedback on cards, give your customers the ability to control their experience, in-turn helping you scale your use of in-app messaging without irritating customers or missing important feedback that you'll need to be effective in this channel.
Disabling secondary actions
These secondary action options can be blocked by you on a card by card basis when designing templates. For example, not all cards should allow recipients to snooze them.
- When editing a card template, from the card configuration menu, choose Menu actions, to see and adjust the options available in the main overflow menu, and in the (mobile) swipe menu for that template.
We strongly recommend leaving as many secondary action options as possible on for customers, to reduce the risk of frustrating users or becoming tone-deaf as you scale proactive engagement in your most important channels.
Card voting
The feature which enables customers to tell you how they feel about a card you've sent is known as card voting. This option enables customers to indicate whether a card was useful to the user or not, and is accessible when they tap on the overflow button in the top right of a card.
Card voting should be configured from the "Menu actions" options in the Card elements menu. From this location you can choose to enable/disable vote up or vote down menu actions. Additionally you can choose to enable/disable text feedback for a vote up or vote down action.
If enabled for vote up actions (Beta feature, requires SDK 25.2.0 or higher), users will have the chance to optionally provide text feedback (up to a 280 character limit) when voting up a card.
If enabled for vote down actions, users will be presented with the "Something else" reason for why a card wasn't useful. Again they will be able to provide text feedback up to a 280 character limit.
If the user indicates that the card was useful, a corresponding analytics event is sent for that card (card-voted-up), containing the text feedback if applicable.
If they indicate that the card was not useful, they are presented with a secondary screen where they can choose to provide further feedback. The available reasons for why a card wasn’t useful are:
- It’s not relevant;
- I see this too often;
- Something else (shown when text feedback has been enabled).
After tapping "Submit", an analytics event containing this feedback is sent (card-voted-down).
You can customize the titles that are displayed for these actions, as well as the title displayed on the secondary feedback screen. By default these are:
- Thumbs up - "This is useful";
- Thumbs down - "This isn’t useful";
- Secondary screen title - "Send feedback".
There is an option to enable card voting for all cards within a stream container from the SDK stream container configuration. As of SDK version 25.2.0 this feature has been deprecated and configuration from within the workbench should be used instead.
For more information on using this feature in the SDKs, see the relevant documentation for iOS, Android or Web.
When installing Atomic SDKs you can choose to override Atomic's default labels for secondary menu options and other text labels displayed in placeholders and empty states throughout Atomic-managed UI, so they fit your brand's tone of voice.
If you have enabled voting in either the workbench for a card, or in the SDK for a stream container, then users will be able to vote on that card when delivered to the stream container. This means you should be careful when deciding to enable card voting in the SDK stream container configuration, as card editors in the workbench will be unable to disable voting for cards sent to that stream container.
Card snoozing
The Atomic SDKs provide the ability to snooze a card from a stream container or single card view. Snooze functionality is exposed through the card’s action buttons, overflow menu and the quick actions menu (exposed by swiping a card to the left, on iOS and Android).
Tapping on the snooze option from either location brings up the snooze date and time selection screen. The user selects a date and time in the future until which the card will be snoozed. Snoozing a card will result in the card disappearing from the user’s card list or single card view, and reappearing again at the selected date and time. A user can snooze a card more than once.
When a card comes out of a snoozed state, if the card has an associated push notification, and the user has push notifications enabled, the user will see another notification, where the title is prefixed with Snoozed:.
You can customize the title of the snooze functionality, as displayed in a card’s overflow menu and in the title of the card snooze screen. The default title, if none is specified, is Remind me.
For more information on using this feature in the SDKs, see the relevant documentation for iOS, Android or Web.