Documentation

DocsIn-App Push

In-App Push Campaigns

In-App Push campaigns allow you to display targeted messages, modals, or banners directly inside your application while the user is actively using it. Unlike standard push notifications, in-app messages do not require explicit OS-level opt-in, making them a powerful tool for driving engagement.


1. Prerequisites

  • SDK Integration: The AlgorithmX Mobile SDK or Web SDK must be fully integrated and initialized within your application.
  • Event Tracking: Ensure your app is sending screen views and user interaction events to the AlgorithmX CDP.

2. Step-by-Step Guide

Step 1: Campaign Setup

Navigate to CAMPAIGNS > In-App Push and click + New Campaign.

In-App Push Creation

  1. Campaign Name: Provide an internal tracking identifier.
  2. Platform Target: Select whether this campaign will display on iOS, Android, or Web.

Step 2: Audience & Trigger Conditions

In-App messages trigger based on user behavior.

  1. Sent to Segment: Select the target audience (e.g., "Users who have not completed onboarding").
  2. Trigger Event: Choose the exact action that will trigger the message (e.g., App Opened, Reached Home Screen, or Cart Viewed).

Step 3: Message Design

  1. Layout Type: Select the visual format (Full Screen, Modal, Top Banner, or Bottom Banner).
  2. Content: Add an image, write your headline, and define the body text.
  3. Primary Action: Configure the button (e.g., "Upgrade Now") and define its Deep Link URL.

Step 4: Campaign Timing & Limits

  1. Start/End Date: Define the exact window the campaign is active.
  2. Frequency Capping: Set a limit (e.g., "Show maximum 1 time per user per day") to prevent spamming your customers.
  3. Click Publish.

3. Configuration Reference

| Field Name | Type | Description / Best Practice | | :--- | :--- | :--- | | Trigger Event | Dropdown | The exact SDK event that causes the message to appear. | | Layout Type | Picker | Choose the intrusiveness level. Best Practice: Use Modals for urgent updates, and Banners for subtle promotions. | | Deep Link URL | Text | The internal app route the user is taken to upon clicking the button (e.g., myapp://checkout). | | Frequency Capping | Number | Critical to ensure a positive user experience. Never leave this unlimited. |


4. Best Practices & Troubleshooting

Best Practices

  • Context is Key: Trigger the message at a logical moment. Don't show a generic promo modal the exact millisecond the app opens; wait until they reach the home feed.
  • A/B Testing: Always test different images and headlines.

Troubleshooting

[!WARNING] Message Not Appearing? If your in-app message isn't showing on your test device:

  1. Ensure your device falls into the targeted Segment.
  2. Verify that your SDK is initialized with the correct userId.
  3. Check if the "Frequency Cap" has already been reached for your test user.