Products

One SDK for mobile push and in-app.

Both products are in the same SDK. The app adds it once. Push reaches the lock screen. The card is drawn in the app. They share an audience, and the price is per app. A new app starts free. With no users there is nothing to bill. The first 1,000 monthly active users on that app stay at $0.

Start for free

9:41 Now

Xulo

Your order is on the way

It arrives today, before 20:00.

Mobile push A notification with a title, a body, an image, and a link.

Arriving today

Open the card to follow the delivery.

Track order

In-app A native card. On an open, or when the app calls a name.

One SDK

Mobile push and the in-app card are one SDK, for a native iOS app. The app adds it once. There is no second package for the card.

That SDK registers the device, keeps the install id, shows the notification, and draws the card.

How they work together

A push can stand on its own. The card can stand on its own. They can also follow each other. After a specific push, the card can show on the next open of the devices that received that push.

An open is the app coming to the foreground. Coming forward again while the app is already open does not count. The card can show once on the next open, on every open, on the first open only, or on the open you number, once. You write that number in the panel. It can also show when the app calls a name you set, once on that device or on every call. The call is not stored. If the app never calls the name, that card does not show. It is not sent through Apple’s push service. One card shows at a time. If several match, the newest published card wins.

The same audience

Push and the card use the same audience. A segment, a tag, an external id, the install id, or a test device. A purchase keeps a lifetime total, and a segment can limit that spend to the last 24 hours, the last 7 days, the last 30 days, or all time.

Xulo keeps an install id that survives a token refresh. A reinstall gets a new one. An external id is optional and does not replace the install id.

Who comes back

The panel keeps the day a device first opened, and the later days it opened. For devices first seen on one day, it shows the share that opened the app again on day 1, on day 7, and on day 30.

That is the last-open record, kept by day. It is not how long a session lasted. It is not a custom event. It is not a list of people. It does not add a fee.

A person sends

The panel, or an agent at https://mcp.xulo.io/mcp, can draft the message, the audience, and the card. The draft includes a count of who would receive it.

A person says yes. Then it sends. Writing the draft does not send it. A push or a card can be two variants, split evenly across the audience. A scheduled push can also be a clock time on each device, taken from the device settings when the app opens.

One price

The first 1,000 monthly active users on an app are free. After that, $6 per 1,000. Apps do not pool. In-app impressions are not billed.

Questions

What does Xulo offer?

Mobile push and a native in-app card, in one SDK. They share an audience. The first 1,000 monthly active users on an app are free. After that, $6 per 1,000. Apps do not pool.

Do mobile push and in-app need two SDKs?

No. Both are in one SDK for a native iOS app. The app adds it once. There is no second package for the card.

Do mobile push and in-app use the same audience?

Yes. A segment, a tag, an external id, the install id, or a test device can receive either. The card is not sent through Apple’s push service.

Can a segment use what someone has spent?

Yes. A purchase is an amount, a currency, and an order id. The person page keeps the lifetime total for each currency. A segment picks the last 24 hours, the last 7 days, the last 30 days, or all time. Inside that window it can be people who spent, people who did not, or people who spent at least an amount in one currency. Currencies are not converted.

Can a shop send its orders?

Yes. The iOS SDK records a purchase on the open install. A shop does not run the SDK. Its server sends the same record with an external id when the order is paid. Phones and the shop add up when they share that id. The same order id replaces the previous amount, so a refund is that order written again with what remains.

What does the return rate show?

For devices first seen on one day, the share that opened the app again on day 1, on day 7, and on day 30. The panel keeps the first open day and the later open days. That is the last-open record, kept by day.

Is the return rate a list of people?

No. It is not a list of people, not how long a session lasted, and not a custom event. It does not add a fee.

Can a push be followed by the card?

Yes. After a specific push, the card can show on the next open of the devices that received that push. An open is the app coming to the foreground. The card can also show once on the next open, on every open, on the first open, on the open you number, or when the app calls a name you set. That call is not stored.

Who sends?

The panel or an agent at https://mcp.xulo.io/mcp can draft the message, the audience, and the card. A person says yes. Writing the draft does not send it. The send can be two variants, or a clock time in each device’s timezone.

Does a new app pay?

A new app starts free. With no users there is nothing to bill. The first 1,000 monthly active users on that app stay at $0.