For surveys and other designs of your own, a message can also be
custom HTML: your HTML, CSS and JavaScript, shown
sandboxed by the Sequenzy SDKs, with a JavaScript bridge to close it, open
links, log events and save answers. Survicate surveys and Braze custom HTML
messages work as is.
In-app messages are unlimited on every plan, including Free, and do not use
email credits. Nothing is
sent by email or push: if your app does not fetch the feed, contacts never see
the items.
How it works
- Add a Show In-App step to a sequence. Each contact who reaches it gets
one item in their in-app feed, with merge tags like
{{FIRST_NAME|there}}already filled in. - Your app fetches the signed-in contact’s feed, either from the browser or from your backend.
- Your app shows the items and reports
displayed,clicked,dismissedandreadback. Those reports power the step’s stats and decide what stays in the feed.
Set it up with an AI coding tool
In Settings → In-app, choose Copy prompt for a web app, or for a mobile or server-rendered app. The prompt has your workspace’s values filled in and explains how to fetch the feed, render each format and report events. Paste it into Cursor, Claude Code or Codex, or send it to your developer.Add an in-app step
In the sequence builder, add Show In-App under Messages. Start from Templates (trial ending, limited offer, welcome, new feature, quiet update, milestone, rating request and tip card) or a blank step, then choose:- Message or Content card.
- For messages, the format: modal, banner or full screen. A modal is a Sheet that rises from the bottom (the default) or Centered. Banners go at the top or bottom.
- An optional eyebrow, a short line above the title such as
3 days left(up to 40 characters). - A title and message (at least one), and an optional https image. On modals and full screens the Image style puts the image Above text or Behind text, with the text in white on a dark gradient.
- Up to two buttons. A button either opens a link (an https URL or an app
deep link such as
myapp://billing) or closes the item. - Optional extra data: string key/values your app receives with the item,
for example
screen: billing. Merge tags work in values. - An optional expiry in days (1 to 365), and for cards, Pin to the top.
style
(backgroundColor, textColor, mutedTextColor, buttonColor,
buttonTextColor, cornerRadius, buttonRadius, fontFamily), so your app
can draw it in your brand without hard-coding colors. The preview shows the
result on a phone and on the web.
Through the API, set style on the step, for example
{ "preset": "bold", "cornerRadius": 8 }. When you update a step, the
style you send merges into its current style: set a value to null to go
back to the preset’s value, or send "style": null to reset everything. If you
override a background color but not the text color on it, the text switches to
black or white when the preset’s color would be hard to read.
A step never stops the journey: if the content is empty after merge tags are
filled in, the step is skipped and the contact moves on. Each contact gets at
most one item per step, even if the step is processed again.
The API takes the same fields on in-app steps: eyebrow, imagePlacement
(top or background) and position (bottom or center for modals). List
templates with List In-App Templates
and write copy with Write In-App Copy, or
sequenzy in-app templates and sequenzy in-app write in the CLI.
You can also add in-app steps through the API with type: "in_app" on
Create Sequence or
Update Sequence steps, with
sequenzy sequences create --steps-json in the CLI, or with the
insert_sequence_step MCP tool.
Fetch from the browser
Browser apps can call Sequenzy directly with your publishable site key (Settings → Integrations → Publishable keys) and an identity token that your backend mints for the signed-in user. The token proves which contact the browser speaks for, so one user can never read another user’s feed.- After sign-in, your backend calls
POST /api/v1/web-tracking-identitieswith a secret API key (scopescommerce:write,automations:triggerandsubscribers:write) and{ "publicKey": "seq_pk_...", "email": "<user email>" }, and returnsidentityTokento the browser. If you already callsequenzy.identify, reuse that token. - The browser fetches the feed:
kind (message or card) and limit (1 to 100) are optional. Add
"formats": ["modal", "banner", "fullscreen", "html"] only if your app shows
custom HTML messages; without it they are left out.
The response
is { "success": true, "messages": [...] }, with items in the
List In-App Messages shape.
- The browser reports events:
text/plain so browsers skip the CORS preflight. Browsers must
come from one of the key’s allowed origins, and native apps must send an
allowed app ID in the x-sequenzy-app-id header (see
Mobile SDKs). Both endpoints are rate limited per IP address.
A valid identity for a contact that no longer exists returns an empty feed.
Show in your mobile app
The Mobile SDKs for iOS, Android, React Native and Flutter fetch the feed, show messages as a modal, banner or full screen in the step’s style, report every event, and give you content cards for your own screens.Push primers
A push primer is an in-app message that explains why notifications help before the system prompt appears. iOS shows that prompt only once, so asking at a good moment (after a first workout, when an order ships) matters more than asking early. Start from the Turn on notifications template, or give a button the Asks for push action (request_push_permission in the API).
When the contact taps it, the Mobile SDKs
show the system prompt. If they turned notifications off earlier, iOS and
Android no longer prompt, so the SDK opens the app’s notification settings
instead. Either way it reports the click with the resulting permission.
- Who sees it. Only apps whose SDK can ask for permission receive primers;
other feeds leave them out, and they stay in the inbox for an app version
that can. Target contacts whose
pushPermissionattribute is notgrantedorprovisional, so people who already allow notifications aren’t asked. - Results. The step’s stats count contacts who allowed notifications (including iOS provisional) and those who declined.
- Your own UI. Backends that render the feed themselves pass
actions=request_push_permissionto List In-App Messages, and sendpushPermissionwith theclickedevent.
Fetch from your backend
For server-rendered apps, or apps that route everything through their own backend, fetch with a secret API key:- List In-App Messages with the
contact’s
emailorexternalId(subscribers:readscope). - Record In-App Event for each report
(
subscribers:writescope). Forward only IDs that came from that user’s own feed.
Reporting events
Only the first report of each type sets its timestamp, so retrying
displayed,
dismissed and read is safe. Every clicked report adds to the click
count, so send it once per click.
Each event also appears in the contact’s activity as in_app.displayed,
in_app.clicked, in_app.dismissed or in_app.read, next to
in_app.created when the step ran and in_app.skipped when it was skipped.
Results
With stats turned on in the sequence flow, each in-app step shows how many contacts got the item, the share that saw it and the share that clicked. Push primers also show how many contacts allowed notifications from them. The same counts are available from Get In-App Step Stats,sequenzy in-app stats <stepId> and the get_in_app_step_stats MCP tool.
A contact’s page lists their in-app items with what happened to each, and lets
you remove an item that is still waiting. Deleting a contact deletes their
in-app items.