Mobile Push Setup

Copy

• Copy for LLM

  Copy page as Markdown for LLMs
• View as Markdown

  Open this page as Markdown
• Open in ChatGPT

  Get insights from ChatGPT
• Open in Claude

  Get insights from Claude
• Connect to Cursor

  Install MCP server on Cursor
• Connect to VS Code

  Install MCP server on VS Code

Overview

Before you can send Mobile Push campaigns through Engage Studio, you need to configure Firebase Cloud Messaging (FCM) and integrate it with Treasure Data. This guide walks through the complete setup process for both Android and iOS platforms.

Prerequisites

• Firebase Project: A Firebase project with Cloud Messaging enabled
• Apple Developer Account: Required for iOS push notifications (APNs)
• Treasure Data Account: With appropriate permissions to configure integrations

Architecture Overview

Mobile Push notifications in Engage Studio work through the following flow:

1. Campaign Creation: You create a campaign in Engage Studio with target audience and content
2. Delivery Pipeline: Engage Studio sends device tokens and payload to Firebase Cloud Messaging
3. FCM/APNs: Firebase delivers notifications to Android (via FCM) and iOS (via APNs)
4. Mobile App: Your app receives the notification and tracks user actions
5. Event Tracking: App sends events back to Treasure Data for analytics

┌─────────────────┐
│ Engage Studio   │
│   Campaign      │
└────────┬────────┘
         │
         ▼
┌─────────────────┐
│  Firebase       │
│  Cloud          │
│  Messaging      │
└────────┬────────┘
         │
    ┌────┴────┐
    │         │
    ▼         ▼
┌────────┐ ┌────────┐
│ FCM    │ │ APNs   │
│Android │ │  iOS   │
└───┬────┘ └───┬────┘
    │          │
    ▼          ▼
┌──────────────────┐
│   Mobile App     │
│ (Customer-built) │
└────────┬─────────┘
         │
         ▼
┌─────────────────┐
│ Treasure Data   │
│  (Event Logs)   │
└─────────────────┘

Step 1: Firebase Project Setup

1.1 Create or Select a Firebase Project

1. Go to the Firebase Console
2. Click Add project or select an existing project
3. Follow the wizard to complete project creation

1.2 Register Your Android App

1. In the Firebase Console, click the Android icon
2. Enter your Android package name (e.g., com.example.myapp)
   • This must match the applicationId in your build.gradle file
3. Optionally enter app nickname and SHA-1 certificate
4. Click Register app
5. Download the google-services.json file
   • Place this file in your Android app's app/ directory
6. Follow the SDK setup instructions (covered in the Android Developer Guide)

1.3 Register Your iOS App

1. In the Firebase Console, click the iOS icon
2. Enter your iOS bundle ID (e.g., com.example.myapp)
   • This must match the Bundle Identifier in Xcode
3. Optionally enter app nickname and App Store ID
4. Click Register app
5. Download the GoogleService-Info.plist file
   • Add this file to your Xcode project root
6. Follow the SDK setup instructions (covered in the iOS Developer Guide)

Step 2: Apple Push Notification Service (APNs) Configuration

2.1 Create an APNs Authentication Key

1. Log in to the Apple Developer Portal
2. Navigate to Certificates, Identifiers & Profiles > Keys
3. Click the + button to create a new key
4. Enter a key name (e.g., "My App APNs Key")
5. Check Apple Push Notifications service (APNs)
6. Click Continue and then Register
7. Download the .p8 key file
   • Important: Save this file securely — you can only download it once

2.2 Upload APNs Key to Firebase

1. In the Firebase Console, go to Project Settings > Cloud Messaging
2. Under Apple app configuration, click Upload
3. Provide the following information:
   • APNs Authentication Key: Upload your .p8 file
   • Key ID: Found in the Apple Developer Portal under Keys
   • Team ID: Found in the Apple Developer Portal under Membership
4. Click Upload

Step 3: Integration Hub Configuration

To send push notifications from Engage Studio, you need to configure the Firebase integration in Treasure Data's Integration Hub.

3.1 Register Firebase Streaming Connector

1. Log in to Treasure Data Console
2. Navigate to Integration Hub > Catalog
3. Search for Firebase Cloud Messaging (Streaming Egress Connector)
4. Click Create Authentication
5. Configure the authentication:

6. Click Save

3.2 Configure Treasure Engage Connector

The Treasure Engage Connector is used to authenticate campaign delivery from Engage Studio.

1. Navigate to Integration Hub > Catalog
2. Search for Treasure Engage
3. Click Create Authentication
4. Configure the authentication:

5. Click Save

Step 4: Verify Configuration

4.1 Test Firebase Connection

You can verify your Firebase setup by sending a test notification:

1. In Firebase Console, go to Cloud Messaging
2. Click Send your first message
3. Enter a notification title and text
4. Click Send test message
5. Enter a device FCM token (you can get this from your app logs after implementing the developer guide)
6. Verify the notification appears on your device

4.2 Verify Integration Hub Authentication

In the Treasure Data Console:

1. Navigate to Integration Hub > Authentications
2. Verify both authentications appear in the list:
   • Firebase Cloud Messaging (Streaming Egress)
   • Treasure Engage
3. Check that their status shows as Active

Step 5: Mobile App Implementation

At this point, your Firebase and Treasure Data integrations are configured. The next step is to implement push notification handling in your mobile apps.

Security Best Practices

API Key Management

• Never commit API keys to source control: Use environment variables or secure key management services
• Rotate keys regularly: Change your Master API Key and Firebase service account keys periodically
• Use separate keys for development and production: Create distinct Firebase projects and Treasure Data write keys for each environment
• Restrict key permissions: Use write-only keys for app-side event tracking

Firebase Service Account Permissions

When generating your Firebase service account JSON:

1. Navigate to Firebase Console > Project Settings > Service Accounts
2. Click Generate new private key
3. Store the downloaded JSON file securely
4. Ensure the service account has only the minimum required permissions:
   • Firebase Cloud Messaging API: Enabled
   • Remove any unnecessary roles

Troubleshooting

Issue: iOS Notifications Not Received

Possible Causes:

• APNs key not uploaded to Firebase
• Bundle ID mismatch between Xcode and Firebase
• Notification permissions not granted on device
• App not properly registered for remote notifications

Solutions:

1. Verify APNs key is correctly uploaded in Firebase Console
2. Check Bundle ID matches exactly (case-sensitive)
3. Check notification permission status in iOS Settings > Notifications
4. Review implementation in iOS Developer Guide

Issue: Android Notifications Not Received

Possible Causes:

• google-services.json not added to project
• Package name mismatch
• Firebase Cloud Messaging not enabled
• Device offline or FCM token expired

Solutions:

1. Verify google-services.json is in the app/ directory
2. Check package name in build.gradle matches Firebase registration
3. Ensure FCM is enabled in Firebase Console
4. Request a new FCM token from the device
5. Review implementation in Android Developer Guide

Issue: Authentication Failed in Integration Hub

Possible Causes:

• Incorrect Master API Key
• Firebase service account JSON is invalid or expired
• Incorrect Firebase Project ID

Solutions:

1. Verify Master API Key is correct and active
2. Generate a new service account key from Firebase Console
3. Double-check the Firebase Project ID (found in Firebase Console > Project Settings)

Next Steps

After completing this setup:

1. Implement mobile app functionality:

   • Android Developer Guide
   • iOS Developer Guide

2. Create your first campaign:

   • See Mobile Push Campaign Overview

3. Set up event tracking:

   • See Push Events Table

Additional Resources

• Firebase Cloud Messaging Documentation
• Apple Push Notification Service Documentation
• Treasure Data Integration Hub