# A native card, drawn in the app.

It can show when the app comes to the foreground, or when the app calls a name you set. It is not a web page, and it is not sent through Apple’s push service.

The panel and an agent fill the same record: image, title, body, one button, link, colors, a close button, and a place. The place is the center, full screen, a top banner, or a bottom banner. One card shows at a time. If several match, the newest published card wins.

It is not sent through Apple’s push service. Impressions are not on the bill. The card can be two variants, split evenly. A person still approves.

- Once, on the next open.
- On every open.
- On the first open only.
- On the open you number, once.
- After a specific push, on the next open of devices that received it.
- When the app calls a name you set. Once on that device, or on every call.
- Two variants. Each one keeps its own impressions, dismisses, and button clicks.

## What the card is made of

The panel and an agent fill the same record. Image, title, body, button label, link, and the colors for the background, the title, the body, and the button. A close button is part of that record. The dim depends on where the card sits.

The SDK draws it. The type is the system font. The editor is a live preview of those fields. A person approves before it is published.

## Where the card sits

The same record sits in one of four places. Center is a window in the middle, and the app behind it is dimmed. Full screen fills the app. There is no separate dim. A banner sits on the top edge or the bottom edge. The app behind a banner stays usable.

Every place uses the same fields. Image, title, body, one button, and a close button. The type is the system font. A second button, a countdown, and a custom font are not part of this record. There is no fifth place.

## On an open

An open is the app coming to the foreground. Coming forward again while the app is already open does not count as another open. The SDK asks on that open whether this device has a card.

Once, on the next open. That device does not see it again. On every open, it shows each time the app comes to the foreground. On the first open only, it shows the first time that device opens the app.

On the open you number, once. You write the number in the panel. The fifth open shows the card once. Later opens do not. After a specific push, it shows on the next open of the devices that received that push.

## A name the app calls

The name is a short text on the campaign. You choose it. The app calls that name at the moment you pick, with one line of code. The SDK asks then, and draws the card if this device has one for that name.

The call is not a log. It is not stored, and a visited page does not show the card later. If the app never calls the name, the card does not show. On that device it can show once, or on every call.

## One card at a time

The SDK asks on an open, and when the app calls a name, whether this device has a card. One card shows. If several match, the newest published card wins.

The card keeps its own impressions, dismisses, and button clicks. The count is for that campaign. A click is stored on the install, and it is visible on that device’s page in the panel.

## The same audience as push

The card uses the same audience as mobile push. A segment, a tag, an external id, the install id, or a test device. It is not a second list. That audience includes what a person has spent: the last 24 hours, the last 7 days, the last 30 days, or all time.

Push permission is not required for the card to show. A device that refused push and opened the app can still see it. The card is not sent through Apple’s push service.

## Two variants

The card can be two variants. The audience is split evenly. Each variant keeps its own impressions, dismisses, and button clicks.

A person still approves. Xulo does not pick a winner.

## What it costs

Impressions are not a separate charge. A device that opened the app in the last 30 days is already a monthly active user, including when it refused push.

The first 1,000 monthly active users on an app are free. After that, $6 per 1,000. Apps do not pool. A second app does not spend the first app’s free thousand.

## Questions

### Is the in-app card a web page?

No. The card is drawn natively in the app. It is not a web view, and it is not sent through Apple’s push service. It can sit in the center, full screen, or as a banner on the top or the bottom edge.

### When does the card show?

On an open, which is the app coming to the foreground, or when the app calls a name you set. An open can be once on the next open, every open, the first open only, the open you number, or after a specific push. A name shows once on that device, or on every call. The call is not stored.

### Are in-app impressions billed?

No. Impressions are not a separate charge. A device that opened the app is already a monthly active user, including when it refused push. The first 1,000 monthly active users on an app are free. After that, $6 per 1,000. Apps do not pool.

### Can an agent design the card?

Yes. The agent and the panel fill the same record: image, title, body, one button, link, colors, a close button, and where it sits. A person still approves the send.

### Can the card be an A/B test?

Yes. The card can be two variants. The audience is split evenly. Each variant keeps its own impressions, dismisses, and button clicks. A person still approves. Xulo does not pick a winner.

### Can the card use its own font?

No. The type is the system font. A second button, a countdown, and a custom font are not part of the record. The place is one of four: center, full screen, top banner, or bottom banner.

### Does a banner dim the app?

No. A top or bottom banner leaves the app usable. The center window dims what is behind it. Full screen is the screen, so there is no separate dim. The close button is on all four.

### Does the card use the same audience as push?

Yes. A segment, a tag, an external id, the install id, or a test device. The card is not a separate list, and it is not sent through Apple’s push service. The same audience can use what a person has spent, over the last 24 hours, the last 7 days, the last 30 days, or all time.