Create in-app campaigns

Send a targeted announcement inside your iOS app. A Card presents a centered message with artwork and an action button. A Banner presents a compact message at the top of the screen; customers can tap its content to open the action or close it to dismiss it.

Your app must identify the signed-in customer and signal that its screen is ready. See the iOS integration guide for setup.

1. 01

   Choose the audience

   Open Campaigns in the BTX desktop app and add a campaign. Enter an internal name and select a Segment. Start with a segment containing only your test accounts.

2. 02

   Add the content

   Choose Card or Banner under Presentation. Add the title, body, and artwork. Configure an HTTPS link or a published Help Center article as the action. Cards also need a button label; banners use the entire content area as the action.

3. 03

   Review and start

   Review the preview, then select Start Campaign. Verify the recipient count before confirming. Select Save Draft if you want to return to the campaign later.

Starting a campaign fixes its audience to the eligible SDK customers in the selected segment. Later signups or segment additions do not join that campaign. Create a new campaign when you need a new audience or another announcement.

Optional: Enable Include a push notification before starting. Push requires the app's push integration and customer permission. A push tap follows the normal app launch flow; it does not force a campaign to appear.

Each customer has a queue ordered by when campaign deliveries were created. The app selects the oldest active campaign on a cold launch: a fresh app process, rather than a return from the background. It attempts at most one campaign during that launch.

The app waits until the customer is signed in and the screen is ready. An internet connection is required; customers who are offline wait for a later launch. If the app cannot confirm whether a campaign appeared, it avoids showing it again. A confirmed presentation failure can retry on a later launch.

Viewed, clicked, or dismissed campaigns do not appear again for that customer. Returning to the app from the background does not advance the queue. Starting or resuming a campaign while the app is already open does not replace that launch's selection.

Select a campaign to see its audience and delivery results. Use the customer search and status filter to investigate a recipient, and refresh to load recent results.

• Queued: Waiting for an eligible launch or presentation.
• Viewed: The SDK confirmed that the content appeared.
• Clicked: The customer activated the campaign action.
• Dismissed: The customer closed the campaign.
• Unconfirmed: The app reserved the campaign for display but has not confirmed that it appeared.

Viewed includes customers who later clicked or dismissed, so these counts can overlap. Results sync when connectivity returns and can appear after the interaction.

All Customers lists SDK customers enrolled in segment-based campaigns, with their email, Last Viewed Campaign, and Up Next Campaign. Search by name or email, or filter by campaign and segment. The list retains campaign history; it is not a live list of every current segment member. Up Next Campaign reflects the next active queued campaign and can change when campaigns are paused or resumed.

• Pause Campaign stops new deliveries. Queued campaigns retain their position and become eligible again after Resume Campaign. Content already reserved by an app for display may still appear.
• Edit updates content for pending deliveries. Content already reserved by an app for display stays unchanged. If an edit invalidates the app's pending content, presentation waits until a later launch.
• After a campaign starts, its audience, presentation type, and push setting are fixed. Create another campaign to change these settings.
• Archive Campaign ends delivery and preserves results for review.

1. 01

   Prepare a test campaign

   Identify your test account in the app and confirm that it belongs to the test segment. Create a fresh campaign and verify that its review includes only the intended test recipients.

2. 02

   Check presentation and actions

   Start the campaign, fully quit the app, and launch it again. Confirm the card or banner appears after the signed-in screen is ready. Activate its action or dismiss it, then refresh the campaign results in BTX.

3. 03

   Confirm the campaign does not repeat

   Fully quit the app and launch it again. Confirm the same campaign does not return, then archive the test campaign.

If nothing appears, check the project's campaign access, SDK capability, signed-in identity, readiness signal, network connection, and earlier queued campaigns. An already viewed campaign cannot be reused to test first display.