Skip to main content

Card element reference

This guide is a high-level summary of which card elements are supported in the Workbench card-builder and SDKs.

Top-level is how we refer to the default view of a card - the card content a customer sees in their stream container. Subviews are the secondary layouts, which are accessed by link-buttons on the top-level view.

Some content can only be added in either top-level or subview, but most elements can be used in both.

We have indicated for each element at which level it can be used.

Every element is optional.

Text elements

Category

Title at the top of a card that identifies its category. Only available in top-level view.

Example

alt text

Properties

PropertyDetail
TextThe text to display for the category title.
e.g. “Overdue Tasks”
Icon(Optional) The icon to display to the left of the text.
Icons from the Free Font Awesome collection and custom SVGs are supported.

Support

Card editoriOS SDKAndroid SDKWeb SDK

Media banner which displays at the top of a card. Only available in top-level view. The Images safe areas section provides a detailed description of how to optimise the aspect ratios of these images.

Properties

PropertyDetail
Source URLThe URL to the full size to display when the user taps on the image.
Thumbnail URLThe URL to the thumbnail image which displays inline with the card.
InteractionImage-only. The behavior of the image when clicked. Either "Open full-size", "Link to URL", "Link to subview" or "Pass a JSON payload to your app" Requires SDK version 24.1.0-beta1 or higher.
Display heightThe height of the image (thumbnail for videos), one of "Tall", "Medium", "Short" or "Original". Requires SDK version 24.2.0 or higher.

Support

Card editoriOS SDKAndroid SDKWeb SDK

Headline

A title intended as the main heading for a card. Available in top-level and subview.

Example

alt text

Properties

PropertyDetail
TextThe text to display in the headline.
e.g. “You have 3 overdue tasks to complete”

Support

Card editoriOS SDKAndroid SDKWeb SDK

Text

A body of text, supporting Markdown formatting and an optional icon on its left. Available in top-level and subview.

Properties

PropertyDetail
TextThe text to display.
E.g. “Last task due 3rd July 2019”
Supported Markdown includes:
**bold** or __bold__
*italic* or _italic_
- list item
1. list item
[link](https://atomic.io/)
Icon(Optional) The icon to display to the left of the text.
Icons from the Free Font Awesome collection and custom SVGs are supported.

Support

Card editoriOS SDKAndroid SDKWeb SDK


List

Renders a list of items as a bulleted, numbered or comma separated list. Available in top-level and subview.

Properties

PropertyDetail
TypeThe type of list to render:
number, which renders a numbered list;
bullet, which renders a bulleted list;
comma, which renders a comma separated list.
SourceAn array of items, provided as a list variable, that will be displayed in the list.

Support

Card editoriOS SDKAndroid SDKWeb SDK




Title

The title displayed at the top of the subview. Only available subview.

Properties

PropertyDetail
TextThe title to display at the top of the subview.
E.g. “Update tasks”

Support

Card editoriOS SDKAndroid SDKWeb SDK

Input elements

Date picker

Renders a date picker in the chosen format, allowing the user to select a day, month and year from a platform-specific picker UI. Available in top-level and subview.

Properties

PropertyDetail
LabelThe text to display on the left of the component (if format is inline) or the text to display above the value (if the format is stacked).
Thumbnail URL(Optional) URL to a thumbnail image on the left of the component.
PlaceholderValue to display if no default date is specified, and the user has yet to select a date.
Input nameThe identifier for this field in the response.
Minimum valueThe minimum date that this picker will allow.
Maximum valueThe maximum date that this picker will allow.
Default valueThe default date that the picker should select.
FormatThe format to render the date picker in (inline or stacked).

Support

Card editoriOS SDKAndroid SDKWeb SDK



Renders a dropdown in the chosen format, allowing the user to select from a list of pre-defined values. Available in top-level and subview.

Properties

PropertyDetail
LabelThe text to display on the left of the component (if format is inline) or the text to display above the value (if the format is stacked).
Thumbnail URL(Optional) URL to a thumbnail image on the left of the component.
PlaceholderValue to display when the user has yet to activate the dropdown. Once the user activates the dropdown, the default value (if specified) or the first item in the list is selected.
Input nameThe identifier for this field in the response.
Default valueThe default value that the dropdown should select.
FormatThe format to render the dropdown in (inline or stacked).
Data sourceThe list of items, from the event, that should be rendered in the dropdown.

Support

Card editoriOS SDKAndroid SDKWeb SDK



Stepper

Allows the user to step up and down between a minimum and maximum value. The value can also be changed by selecting the current value and entering a value manually. Available in top-level and subview.

Properties

PropertyDetail
LabelThe text to display on the left of the component.
Thumbnail URL(Optional) URL to a thumbnail image on the left of the component.
Input nameThe identifier for this field in the response.
Minimum valueThe minimum value allowed by the stepper.
Maximum valueThe maximum value allowed by the stepper.
Step valueThe amount to increase or decrease the stepper by when the increment and decrement buttons are pressed.
Default valueThe default value that the stepper starts at.

Support

Card editoriOS SDKAndroid SDKWeb SDK

Checkbox

Renders a checkbox which allows the user to provide a binary response. Can be on its own as a single checkbox, or with other checkboxes as part of a checkbox group. When used as a checkbox group you have the option to specify a minimum and/or maximum number of checkbox items that must be checked. When used as a single checkbox you can specify whether or not it is required to be checked. Available in top-level and subview.

Properties

PropertyDetail
LabelThe text to display on the right of the checkbox input.
ValueThis value is a secondary identifier that is returned on submission of the card. Single checkbox values are formatted the same way as Checkbox group items, e.g.checkbox_abcde.hasAccepted. This value is not visible on the card.
Field nameThe identifier for this field in the response.
Default stateWhether the checkbox initializes as 'checked' or 'unchecked'.

Support

Card editoriOS SDKAndroid SDKWeb SDK

Switch

Allows a user to provide a binary response. Available in top-level and subview.

Properties

PropertyDetail
LabelThe text to display on the left of the component.
Thumbnail URL(Optional) URL to a thumbnail image on the left of the component.
Input nameThe identifier for this field in the response.
Default onIf the switch should default to the ‘on’ state.

Support

Card editoriOS SDKAndroid SDKWeb SDK

Text input

Allows a user to provide a single or multi-line text response. Available in top-level and subview.

Properties

PropertyDetail
LabelThe placeholder to display when the user has not entered any text.
Thumbnail URL(Optional) URL to a thumbnail image on the left of the component.
Input nameThe identifier for this field in the response.
Default valueThe default value displayed in the text input. If there is no default value, the placeholder displays until the user enters text.
Number of LinesThe number of lines the text input can receive without scrolling:

- If number of lines is 0, the text field auto-grows to accommodate the text entered into it.
- If number of lines is 1, the text field is restricted to a single line of text.
- If number of lines is greater than 1, the text field provides enough space for the given number of lines without scrolling, auto-growing after that.

Support

Card editoriOS SDKAndroid SDKWeb SDK

Number input

Renders a single line input that allows only numeric values (integer or decimal). Available in top-level and subview.

Properties

PropertyDetail
LabelThe placeholder to display when the user has not entered any numeric value.
Thumbnail URL(Optional) URL to a thumbnail image on the left of the component.
Input nameThe identifier for this field in the response.
Default valueThe default value displayed in the number input. If there is no default value, the placeholder displays until the user enters a value.

Support

Card editoriOS SDKAndroid SDKWeb SDK

File upload

Renders an input that allows a user to select a file to be submitted with the card. Available in top-level and subview.

Properties

PropertyDetail
LabelThe text to display within the input before a file has been selected.
Field nameThe identifier for this field in the response.
File typeThe file format that the input will accept, currently only image uploads are supported.
File sizeThe file size (in MB) that the input will accept.
RequiredWhether a user is required to supply a file to this input upon submitting the card.
Thumbnail placeholderWhether or not the input should render a placeholder icon in place of the thumbnail preview before an image has been selected.
File destinationThe target that a file selected by this input will be uploaded to upon card submission.

Support

Card editoriOS SDKAndroid SDKWeb SDK

Card actions

Submit button

A button that results in a card being submitted. Available in top-level and subview.

Properties

PropertyDetail
TextThe title to display on the button.
E.g. “Submit”.
Icon(Optional) The icon to display to the left of the text.
Icons from the Free Font Awesome collection and custom SVGs are supported.
Post submit action > ValuesWhen the submit button is triggered, the json payload in the values input field is sent within the card-submitted analytic event as part of the card response payload. This payload is optional, and is sent regardless of the selected post submit action.
Post submit action > NoneNo additional data is sent and no additional actions are taken when the submit button is triggered.
Post submit action > URLA URL that the user is navigated to when submission completes, the URL can be specified to open either in the same window or a new window.
To direct to a callable link (e.g. phone number), use the prefix tel: . e.g. tel:0123456789
Post submit action > PayloadAn optional JSON payload that is passed to the host app on the client side when the submit button is triggered.

Support

Card editoriOS SDKAndroid SDKWeb SDK


A button that triggers a subview, or launches an external URL, when tapped or clicked. Only available in top-level view.

Properties

PropertyDetail
TextThe title to display on the button.
E.g. “More information”.
Icon(Optional) The icon to display to the left of the text.
Icons from the Free Font Awesome collection and custom SVGs are supported.
SubviewThe subview that the user will be navigated to when pressing the link button.
External URLA URL to open when the user presses the link button.
The URL can be specified to open either in the same window or a new window.
Any URL scheme conforming to the standard is supported, allowing for the use of links for specific app functions (deep links). Note: On iOS and Android, deeplinks open the app directly, rather than opening in the browser first.

Support

Card editoriOS SDKAndroid SDKWeb SDK

Dismiss button

A button that results in a card being dismissed. Only available in top-level view.

Properties

PropertyDetail
TextThe title to display on the button.
E.g. “Dismiss".
Icon(Optional) The icon to display to the left of the text.
Icons from the Free Font Awesome collection and custom SVGs are supported.

Support

Card editoriOS SDKAndroid SDKWeb SDK

Snooze button

A button that results in a card being snoozed. If no snooze period is specified against the button in the card editor, the customer can determine how long the card will be snoozed for. Otherwise the card will be snoozed directly on button tap. Only available in top-level view.

Properties

PropertyDetail
TextThe title to display on the button.
E.g. "Snooze".
Icon(Optional) The icon to display to the left of the text.
Icons from the Free Font Awesome collection and custom SVGs are supported.
PeriodThe time period the card is snoozed for. For reference see duration format.

Support

Card editoriOS SDKAndroid SDKWeb SDK

Vote up button

A button that results in a card being voted up, which means a corresponding analytics event is sent for that card (card-voted-up). Only available in top-level view.

Properties

PropertyDetail
TextThe title to display on the button.
E.g. “Vote up".
Icon(Optional) The icon to display to the left of the text.
Icons from the Free Font Awesome collection and custom SVGs are supported.

Support

Card editoriOS SDKAndroid SDKWeb SDK

Vote down button

A button that redirects to a secondary screen to provide further feedback. Only available in top-level view.

After tapping "Submit", an analytics event containing this feedback is sent (card-voted-down).
More information about voting, such as customizing the feedback options, can be found in the Card voting guide.

Properties

PropertyDetail
TextThe title to display on the button.
E.g. “Vote down".
Icon(Optional) The icon to display to the left of the text.
Icons from the Free Font Awesome collection and custom SVGs are supported.

Support

Card editoriOS SDKAndroid SDKWeb SDK

Media

For all media uploads, there is a 128 MB limit on the file size.

All media files are scanned for viruses before they can be used in card templates.

Image

An image rendered in a specified format. Tapping or clicking on the image shows a larger version, which can be zoomed or panned. Available in top-level and subview.

Supported image formats across our SDKs are outlined in the Supported media formats table.

The Images safe areas section provides a detailed description of how to optimise the aspect ratios of these images.

Properties

PropertyDetail
FormatThe format to render the image in.
inline, displaying an image with additional horizontal space on each side;
text, displaying a text link to view the image;
thumbnail, displaying a thumbnail accompanied by a title and description.
Source URLThe URL to the full size to display when the user taps on the image.
Thumbnail URLThe URL to the thumbnail image to display when the format is inline or thumbnail.
DescriptionA description of the image, displayed below the title when format is thumbnail.
E.g. “Atomic.io”
LabelThe label displayed when format is thumbnail or text.
E.g. “Find out more”
InteractionThe behavior of the image when clicked. Either "Open full-size", "Link to URL", "Link to subview" or "Pass a JSON payload to your app". Requires SDK version 24.1.0-beta1 or higher.
Display heightThe height of the image, one of "Tall", "Medium", "Short" or "Original". Requires SDK version 24.2.0 or higher.

Support

Card editoriOS SDKAndroid SDKWeb SDK

Video

A video rendered in a specified format. If the video format is inline, the video plays inline. If the video format is text or thumbnail, the video plays full screen (on iOS and Android). Available in top-level and subview.

Supported video formats across our SDKs are outlined in the Supported media formats table.

Properties

PropertyDetail
FormatThe format to render the video in.
inline, displaying a video thumbnail with additional horizontal space on each side;
text, displaying a text link to view the video;
thumbnail, displaying a video thumbnail accompanied by a title and description.
Source URLThe video to play when the user taps or clicks the play button.
Thumbnail URLThe URL to the thumbnail image to display when the format is inline or thumbnail.
DescriptionA description of the video, displayed below the title when format is thumbnail.
LabelThe label displayed when format is thumbnail or text.
Display heightThe height of the thumbnail image, one of "Tall", "Medium", "Short" or "Original". Requires SDK version 24.2.0 or higher.

Support

Card editoriOS SDKAndroid SDKWeb SDK

Formats

Support for various common video and image formats are outlined in the tables below.

Non-exhaustive lists

These are not intended as exhaustive lists, but as a guide only. Depending on the browsers or operating systems you target, there may be additional media formats that you can use.

Image formatiOSAndroidWeb
JPEG
PNG
GIF
Animated GIF
SVG
Video formatiOSAndroidWeb
MP4
M4V
MOV
HLS
(Safari only)
MKV
3GP

Image and video dimensions

By default, images and videos are scaled to fill the width of the containing card, which is defined by the width of the SDK container. The dimensions of their initial state do not adhere to a specific aspect ratio, but have predefined heights, with image content centered within this area. This helps prevent cards from growing too tall when the SDK is wide. Depending on the variant, the following dimensions will be used.

Always use high-resolution images, especially when they will be viewed on mobile devices with high-density displays.

VariantHeightWidth
Banner200pxFlexible
Inline200pxFlexible
Thumbnail100px100px

If displaying an entire image or video without cropping is important to view the additional detail, customers can do so by tapping them to open them in a subview. Here, they are displayed in their original aspect ratio.

Images safe areas

Include plenty of space around key elements within your images, as they may be cropped at different aspect ratios depending on the device they will be viewed on.

The element displaying banner and inline images have a predefined height of 200px. Images are centred vertically and horizontally within the element.

You should always test how your cards display across multiple devices and platforms – as cropping of banner and inline image elements will vary depending on the platform, device model, and if the device is rotated.

Image crops on cards displayed in the web SDK will depend on the width of the iframe, and can easily be tested via Atomic Connect.

Use images with aspect ratio of 2:1 for banner and inline elements

We recommend creating images with an aspect ratio of 2:1 – this works best with banner and inline image elements, across platform, device and rotation. The exception is the thumbnail element: that has an aspect ratio of 1:1.

The following is an approximate guide to the amount of cropping an image may have, based on some common aspect ratios. The crop percentages are based on our own testing across a number of devices (a mix of iOS and Android, phone and tablet). We can not guarantee exact percentages for specific devices - always perform your own testing.

2:1Mobile: PortraitMobile: LandscapeTablet: PortraitTablet: Landscape
Banner~5% right & left~20% top & bottom~25% top & bottom~30% top & bottom
Inline~10% right & left~20% top & bottom~25% top & bottom~30% top & bottom


1:1Mobile: PortraitMobile: LandscapeTablet: PortraitTablet: Landscape
Banner~20% top & bottom~35% top & bottom~35% top & bottom~30% top & bottom
Inline~20% top & bottom~35% top & bottom~35% top & bottom~30% top & bottom
4:3Mobile: PortraitMobile: LandscapeTablet: PortraitTablet: Landscape
Banner~15% top & bottom~30% top & bottom~35% top & bottom~45% top & bottom
Inline~10% top & bottom~30% top & bottom~35% top & bottom~45% top & bottom
3:2Mobile: PortraitMobile: LandscapeTablet: PortraitTablet: Landscape
Banner~10% top & bottom~30% top & bottom~30% top & bottom~35% top & bottom
Inline~5% top & bottom~30% top & bottom~30% top & bottom~35% top & bottom
16:9Mobile: PortraitMobile: LandscapeTablet: PortraitTablet: Landscape
Banner~5% top and bottom~25% top & bottom~30% top & bottom~35% top & bottom
Inline~5% left & right~25% top & bottom~30% top & bottom~35% top & bottom

Custom icons

Custom icons were introduced in SDK version 24.2.0. Custom icons allow you to upload your own SVG files to use instead of Font Awesome icons.

There are some limitations to which SVG properties are supported in custom icons.

Fully Supported properties

The following properties are supported by all SDK platforms:

  • rect
  • circle
  • svg
  • g
  • ellipse
  • line
  • polygon
  • polyline
  • path
  • text
  • defs
  • pattern
  • clipPath
  • mask
  • linearGradient
  • stop

Supported properties with Issues

The following properties have issues on at least one platform:

  • text
    • text is rendered in Android but fonts are shown very pixelated.

Not Supported

The following properties result in a non-rendered image on at least one platform:

  • a
  • animate
  • animateMotion
  • animateTransform
  • feBlend
  • feColorMatrix
  • feComponentTransfer
  • feFuncB
  • feFuncG
  • feFuncR
  • feGaussianBlur
  • feOffset
  • filter
  • foreignObject
  • image
  • radialGradient
  • set
  • textPath
  • tspan

Nested SVG are not supported by iOS

The following SVG won't work:

<svg width="258" height="383" xmlns="http://www.w3.org/2000/svg">
<!-- First line -->
<svg x="0" y="0" width="258" height="172" viewBox="0 0 300 200" xmlns="http://www.w3.org/2000/svg">
<line x1="0" y1="0" x2="300" y2="200" style="stroke:red;stroke-width:2" />
</svg>
<!-- Second line -->
<svg x="0" y="177" width="258" height="43" viewBox="0 0 300 50" xmlns="http://www.w3.org/2000/svg">
<line x1="0" y1="10" x2="250" y2="10" style="stroke:red;stroke-width:12" />
</svg>
<!-- Third line -->
<svg x="0" y="225" width="258" height="158" viewBox="0 0 300 210" xmlns="http://www.w3.org/2000/svg">
<line x1="0" y1="0" x2="0" y2="200" style="stroke:red;stroke-width:14" />
</svg>
</svg>

But this will:

<svg width="258" height="383" xmlns="http://www.w3.org/2000/svg">
<!-- First line -->
<g transform="translate(0, 0)">
<line x1="0" y1="0" x2="300" y2="200" style="stroke:red;stroke-width:2" />
</g>

<!-- Second line -->
<g transform="translate(0, 177)">
<line x1="0" y1="10" x2="250" y2="10" style="stroke:red;stroke-width:12" />
</g>

<!-- Third line -->
<g transform="translate(0, 225)">
<line x1="0" y1="0" x2="0" y2="200" style="stroke:red;stroke-width:14" />
</g>
</svg>