Skip to main content

Action cards

Atomic surfaces actionable in-app messages called Action Cards to customers when they're inside your existing apps. The orchestration of action cards, including how they're personalized, delivered and dynamically responded to is managed by Action Flows.

As well as delivering information, Action cards offer the ability for your customers to take action directly with the card. The responses from recipients and information about how they're interacted with cards is securely returned to your systems.

Action cards are:

  • Secure - securely delivered behind the login inside your web and mobile apps
  • Personalized - personalized with customer profile values and dynamic data
  • Targeted - delivered to the right person, in the relevant platforms and perfect location in your app
  • Actionable - deliver videos, collect form data, track responses, redirect and deep-link
  • Respectful - cards can be snoozed, dismissed, and collect verbatim customer feedback
  • Effortless - recipients can from from information to action with near-zero effort
  • Seamless - seamlessly embedded inside existing app layouts using smart stream containers
  • Auditable - every step from publishing to action is logged with compliance-ready audit data
  • Flexible - drag and drop card elements to design simple, advanced, and even multi-page messages
  • Live - embargo messages, set expiry, override content at runtime from your app and more

Action card templates are part of Action Flows. To create a card, make an Action Flow, then within it, add a Send a card step to the flow. This will create a new card template, linked to the Send a card step.

Designing cards

Once you have a card template to work with inside your Action Flow, it's time to design it.

  • Check out the creating cards article to see how cards are designed in the card editor inside an Action Flow.
  • Read the subviews article to read about how cards can contain supporting screens to expand the surface area and interactivity of cards
  • Read about context data to understand how card context can be personalized with dynamic data from incoming trigger events, user profiles, and outputs from other Action Flow steps
  • Explore the card element reference to learn about each card element

Sending cards

Cards are created and sent based on the steps in the Action Flow sending them. When the Action Flow is triggered and starts, it runs through it's steps; when it runs a Send a card step, Atomic will use the card template linked to the step to generate a unique card instance, and send it to your target customer in-app. If a push notification is configured as a part of the card template, this too will be sent.

Read the Action Flow triggers article to learn about how cards are sent, and check out the testing article to learn about how you can send yourself test cards while you're designing them and configuring your draft Action Flow.

Displaying cards in your apps

Atomic SDKs installed in your apps communicate securely with the Atomic platform to get cards for the current user, render them in your app and handle customer interaction, while broadcasting events out to your app and back to the Atomic platform.

During your Atomic implementation, you'll create one or more streams. Streams are a way to group similar cards together. Streams are then assigned to stream containers, which your developers will place into your app. This setup means your card designers can choose which stream(s) a particular card should be displayed in, and then the stream containers in your apps connected to those streams will be where the card is displayed to your customers. The integration guide provides more information on common patterns, and other integration decisions you'll make along the way.

API-driven containers

In cases where you can't—or don't want to—use Atomic's SDKs to display cards, you can access raw card data and metadata using API-driven card containers. These containers let your app access the card stream data, so you can present it where and however your designers and developers require.

API-driven card containers provide SDK APIs for your app to call to record core card actions (like dismissing, snoozing and submitting cards), but these won't include metrics like card displayed, or stream container displayed. Read more about in our SDK guides for Web, iOS, Android, Flutter and React Native.

Tracking card responses and performance

Atomic capture analytics that record when cards are created and sent, and many other points in the cards lifecycle, including when and exactly how and customers interact with them.

Card insights dashboard

The Insights dashboard provides a quick and simple overview of how individual cards are performing. Open the insights dashboard from the left sidebar menu, then select the card you're monitoring from the options list. Learn more about card insights in the insights article, including how the insights dashboard defines the calculated metrics.


The Insights dashboard is (currently) focussed exclusively on the performance of individual cards. To view reporting on high-level Action Flow activity, use the Activity report available within Action Flow

Action Flow activity reports

Analytics activity for each Action Flow, which includes metrics covering all steps in the flow, can be found within the Action Flow. From the Action Flows dashboard open your flow, then open the Activity tab. Learn more about Action Flow activity reports in the insights article.

Extracting or sending analytics to 3rd party systems

Check out the analytics article to learn how all analytics events tracked in Atomic can be extracted via API, downloaded from the Workbench, or sent to connected systems using Webhooks.


Events tracked in the Atomic SDKs can also be picked up and used by your app as they happen. Learn more in the Web, iOS and Android SDK guides.