Test Setup

1. Dashboard Setup#

1. Go to your Mobana Dashboard
2. Navigate to your app and copy your App ID
3. Note your redirect URL format: https://YOUR_APP_ID.mobana.ai/redirect

2. Create a Test Redirect URL#

Build a redirect URL with test UTM parameters:

https://YOUR_APP_ID.mobana.ai/redirect?utm_source=test&utm_campaign=my_test_campaign&utm_medium=manual&data={"promo":"WELCOME10"}

3. Run the Test#

1. Open the redirect URL on your test device — Use the device's native browser (Safari on iOS, Chrome on Android). This simulates a user clicking your campaign link.
2. You'll be redirected to the App Store / Play Store — This is expected behavior. The attribution data has been captured.
3. Launch your app — Make sure the SDK is initialized with debug: true.
4. Call getAttribution() — The SDK will retrieve the attribution data from your test click.

4. Verify Results#

import { Mobana } from '@mobana/react-native-sdk';

// Initialize with debug mode
await Mobana.init({
  appId: 'YOUR_APP_ID',
  debug: true,
});

// Get attribution (will show debug logs)
const attribution = await Mobana.getAttribution();
console.log('Attribution result:', JSON.stringify(attribution, null, 2));

// Expected output for successful attribution:
// {
//   "utm_source": "test",
//   "utm_campaign": "my_test_campaign",
//   "utm_medium": "manual",
//   "confidence": 1.0,
//   "data": { "promo": "WELCOME10" }
// }

What to look for:

• In your app logs: Debug output showing the attribution request and response with your test UTM parameters
• In the Dashboard: Navigate to Analytics → Attribution to see your test click recorded with the UTM values you used

Attribution is Sticky#

During development, use reset() to clear the cached state and test the attribution flow again:

// Clear attribution state to test again
await Mobana.reset();

// Now getAttribution() will perform a fresh lookup

Troubleshooting#

• Attribution returns null: Make sure you opened the redirect URL before launching the app. Call reset() and try again.
• Wrong attribution data: You may have a cached attribution from a previous test. Call reset() to clear it.
• No debug logs: Ensure debug: true is set in your init() config.
• Android-specific: Install Referrer attribution requires the app to be installed from a store context. For development, probabilistic matching is used instead.

1. Dashboard Setup#

1. Go to your Dashboard → Settings → Conversion Types
2. Add a test conversion type (e.g., test_event)
3. Optionally add a valued conversion type for testing revenue tracking

2. Track Test Conversions#

import { Mobana } from '@mobana/react-native-sdk';

// Track a test conversion
await Mobana.trackConversion('test_event');

// Track with a value
await Mobana.trackConversion('test_purchase', 9.99);

// Debug logs will confirm the conversion was sent

3. Verify Results#

What to look for:

• In your app logs: Debug output showing the conversion request was sent successfully
• In the Dashboard: Navigate to Analytics → Conversions to see your test events. They will be linked to the device's attribution if one exists.

Troubleshooting#

• Conversion not appearing: Check that the conversion type is registered in your Dashboard settings.
• No attribution link: Conversions are linked to attribution based on device ID. If attribution hasn't run yet, the conversion will still be recorded but won't have UTM data attached.

1. Dashboard Setup#

1. Go to your Dashboard → Flows
2. Create a new flow or use an existing one
3. Publish the flow — Draft flows are not accessible
4. Copy the Flow ID (visible in the flow settings or URL)

2. App Setup#

Ensure your app has the required setup for flows:

• • react-native-webview is installed
• • SDK is initialized with debug: true (optional, for development)
• • Your app is wrapped with MobanaProvider

import { MobanaProvider } from '@mobana/react-native-sdk';

export default function App() {
  return (
    <MobanaProvider>
      {/* Your app */}
    </MobanaProvider>
  );
}

3. Start a Test Flow#

import { Mobana } from '@mobana/react-native-sdk';

// Start a flow
const result = await Mobana.startFlow('your-flow-id');

console.log('Flow result:', result);
// { completed: true, dismissed: false, data: { ... } }
// or
// { completed: false, dismissed: true, data: null }

4. Verify Results#

What to look for:

• In your app: The flow should appear as a full-screen modal overlay. Interact with it to test navigation between slides.
• Flow result: When the flow completes or is dismissed, check the returned object for completed, dismissed, and any data you passed to complete().
• In your app logs: Debug output showing flow events (slide views, button clicks, completions)
• In the Dashboard: Navigate to Flows → Analytics to see engagement metrics for your test flow

Troubleshooting#

• Flow doesn't appear: Check that MobanaProvider wraps your app and the flow is published (not draft).
• White screen or loading: The flow content is being fetched. Use prefetchFlow() to avoid this delay.
• Permissions not working: Ensure the required native packages are installed (e.g., react-native-permissions) and permissions are configured in your iOS Podfile / Android manifest.
• Flow not found error: Verify the Flow ID is correct and the flow is published.