Quick Start Guide

Get BoostOps® attribution tracking running in your Unity game. This guide covers the full setup: creating an account, connecting Firebase or Unity Analytics, installing the SDK, and verifying attribution is working.

Just Need Dynamic Links?

If you only want dynamic links (Universal Links/App Links), see the BoostLink® Quick Start instead. This guide is for full attribution tracking.

Prerequisites

Before you begin, you’ll need:

• Unity Project: Unity 2020.3 or later
• BoostOps Account: Sign up at app.boostops.io
• Analytics Platform: Firebase Analytics (GA4) or Unity Analytics
• Mobile Build Target: iOS and/or Android

Estimated Time: 15-20 minutes

Step 1: Create Your BoostOps Account

1. Visit app.boostops.io/sign-up
2. Sign up with your email or Google account
3. Verify your email address
4. Complete the onboarding flow:
   • Choose your role (Developer, Marketing, Executive)
   • Select goals (Attribution, Cross-Promo, Ad Tracking)
   • Create your studio

Step 2: Create Your First Project

A “Project” in BoostOps represents one game.

1. Click “New Project” in the dashboard
2. Enter your game name (e.g., “My Awesome Game”)
3. Add your app store information:
   • iOS: Bundle ID and App Store ID (optional)
   • Android: Package name (e.g., com.yourstudio.game)
4. Click “Create Project”

Step 3: Project Keys (Automatic)

BoostOps automatically generates project keys when you create a project. These keys authenticate your SDK to send attribution data to BoostOps.

You don’t need to manually copy keys - they’re automatically imported from the cloud when you connect your account in the Unity SDK.

Three Key Types:

• Live Key: Production builds (bo_live_...)
• Test Key: TestFlight/staging builds (bo_test_...)
• Dev Key: Development builds (bo_dev_...)

The SDK automatically selects the right key based on your build configuration.

Step 4: Connect Analytics (Choose One)

BoostOps needs to see install and revenue events from your analytics platform.

Option A: Firebase Analytics (Recommended)

If you use Firebase Analytics (GA4):

1. In BoostOps dashboard, go to Settings → Integrations → Firebase
2. Click “Connect Firebase”
3. Upload your Firebase service account JSON file
   • Get this from Firebase Console → Project Settings → Service Accounts
   • Click “Generate New Private Key”
4. BoostOps will discover your Firebase projects
5. Link your Firebase project to your BoostOps project

What BoostOps Tracks from Firebase:

• first_open event (install attribution)
• in_app_purchase event (revenue attribution)
• User properties (like user_engagement, retention)

Option B: Unity Analytics

If you use Unity Analytics:

1. In BoostOps dashboard, go to Settings → Integrations → Unity
2. Click “Connect Unity Services”
3. Enter your Unity Project ID and Service Account credentials
   • Get these from Unity Dashboard
4. Link your Unity project to your BoostOps project

What BoostOps Tracks from Unity:

• Install events
• Unity Monetization revenue (IAP, ads)
• Session data

Use Both

You can connect both Firebase and Unity Analytics. BoostOps will deduplicate events and give you the most complete picture.

Step 5: Install the BoostOps Unity SDK

From Unity Asset Store (Recommended)

1. Open Unity Package Manager (Window → Package Manager)
2. Search for “BoostOps SDK” in the Asset Store
3. Click Download then Import
4. Accept the import dialog (imports all files)

From Git URL (Alternative)

If you prefer Git:

1. Open Unity Package Manager
2. Click + → Add package from git URL
3. Enter: https://github.com/BoostOps/boostops-unity-attribution-sdk.git
4. Click Add

Verify Installation

After import, you should see:

• Assets/BoostOps/ folder (if from Asset Store)
• Or Packages/BoostOps SDK/ (if from Package Manager)
• Menu: Tools → BoostOps → Settings

Step 6: Configure the SDK

Sign In to Your BoostOps Account

1. In Unity, go to Tools → BoostOps → Sign In
2. Click “Sign in with BoostOps”
3. This opens a browser to authenticate
4. After signing in, Unity automatically imports:
   • Your studio configuration
   • All your projects
   • Project keys (live, test, dev)
   • Analytics connections

Automatic Project Detection

The SDK automatically detects which project to use based on your Unity configuration:

• Android: Detects project from package name (e.g., com.yourstudio.game)
• iOS: Detects project from bundle ID (e.g., com.yourstudio.game)

No manual project selection needed! The SDK matches your package name/bundle ID to the corresponding project in your BoostOps dashboard.

Configure Attribution Settings

In the BoostOps Settings panel:

Analytics Integration (required)

• Select: Firebase, Unity, or Both
• This tells the SDK where to send events

Attribution Window (optional)

• Default: 30 days
• How long after a click to attribute an install

Debug Mode (optional)

• Enable for development to see SDK logs
• Disable in production builds

Example Configuration

Analytics Integration: Firebase
Attribution Window: 30 days
Debug Mode: ✓ (dev builds only)

Note: Project is automatically detected from your package name/bundle ID - no manual configuration needed!

Step 7: Initialize the SDK

BoostOps SDK automatically initializes when your app starts. No code required!

Auto-Initialization (Default)

The SDK initializes automatically using your configuration from Step 6:

• Reads your selected project
• Uses the appropriate key (live/test/dev based on build type)
• Connects to your configured analytics platform

That’s it! No initialization code needed.

Verify Initialization

Build and run your game on a device (not in the Unity Editor). Check the device logs:

[BoostOps] SDK initialized successfully
[BoostOps] Project: My Awesome Game (auto-detected from com.yourstudio.game)
[BoostOps] Environment: LIVE
[BoostOps] Analytics: Firebase connected
[BoostOps] Ready to track attribution

Optional: Custom Configuration

If you need to customize behavior at runtime:

using BoostOps;

public class GameManager : MonoBehaviour
{
    void Start()
    {
        // Set custom campaign parameters (optional)
        BoostOpsSDK.SetCustomSource("my_campaign");

        // Enable debug logging (optional)
        BoostOpsSDK.SetDebugMode(Debug.isDebugBuild);
    }
}

Step 8: Test Attribution

Build and Test

1. Build your game for iOS or Android
2. Install on a real device (attribution doesn’t work in editor)
3. Launch the app for the first time
4. Check the BoostOps dashboard:
   • Go to Projects → Your Game → Attribution
   • Within 1-5 minutes, you should see a new install event
   • Check the Source: Should show “organic” for a fresh install

Test with a BoostLink

To test attribution from a campaign:

1. Create a BoostLink in the dashboard:
   • Go to Projects → Your Game → Dynamic Links
   • Click “Create Link”
   • Add campaign parameters: ?campaign=test&source=docs
2. Delete your app from the test device
3. Click the BoostLink on your device (via Messages, Mail, Notes, etc.)
4. Install from App Store/Play Store
5. Launch the app
6. Check Attribution dashboard - should show source: docs, campaign: test

Step 9: Track Revenue (Optional)

To attribute revenue to acquisition channels, send purchase events:

Using Firebase (Automatic)

If you already track purchases in Firebase, BoostOps will automatically see them:

// Your existing Firebase code
Firebase.Analytics.FirebaseAnalytics.LogEvent(
    "in_app_purchase",
    new Parameter("value", 4.99),
    new Parameter("currency", "USD"),
    new Parameter("transaction_id", transactionId)
);

BoostOps automatically links this revenue to the user’s attribution source.

Using BoostOps SDK (Direct)

Or track purchases directly:

using BoostOps;

void OnPurchaseComplete(string productId, decimal price, string currency)
{
    BoostOpsSDK.TrackRevenue(new RevenueEvent
    {
        ProductId = productId,
        Revenue = price,
        Currency = currency,
        TransactionId = GetTransactionId()
    });
}

Step 10: View Attribution Reports

Now that attribution is tracking, explore your data:

Attribution Dashboard

1. Go to Projects → Your Game → Attribution
2. See installs by channel:
   • Organic
   • BoostLink (campaign clicks)
   • Cross-Promo (from other games)
   • Paid Ads (if you connect ad networks)

Revenue by Channel

1. Go to Projects → Your Game → LTV
2. See lifetime value by acquisition source
3. Find your most profitable channels

Campaign Performance

1. Go to Projects → Your Game → Campaigns
2. See performance of BoostLink campaigns
3. Track clicks, installs, and revenue per campaign

Next Steps

🎉 Congratulations! Attribution is now tracking. Here’s what to explore next:

Connect Ad Networks (Optional)

See ad spend alongside attribution data:

• Apple Search Ads - Track ASA spend and keywords
• Google Ads - Connect Google Ads campaigns
• Facebook Ads - Track Facebook spend

Set Up Cross-Promotion (Optional)

Promote your games to each other:

1. Cross-Promotion Guide - Run campaigns between games
2. Create an “App Wall” to show your portfolio
3. Track cross-promo installs and revenue

Create More BoostLink Dynamic Links

Generate deep links for marketing:

1. BoostLink Guide - Complete deep linking guide
2. Create links for email, social, influencer campaigns
3. Track which channels drive the most installs

Invite Team Members

Add your team to the studio:

1. Go to Settings → Team
2. Click “Invite Member”
3. Assign roles: Owner, Admin, Developer, Marketing, Analyst, Viewer

Troubleshooting

SDK Not Initializing

Problem: No logs in console, attribution not tracking

Solutions:

• Verify you’re signed in (Tools → BoostOps → Settings)
• Check that your package name/bundle ID matches a project in BoostOps dashboard
• Test on a real device (attribution doesn’t work in Unity Editor)
• Check that Firebase/Unity Analytics is configured
• Enable Debug Mode in Settings to see detailed logs

Attribution Not Showing in Dashboard

Problem: Installed app, but no event in dashboard

Solutions:

• Wait 5-10 minutes (events can be delayed)
• Verify Firebase/Unity Analytics connection (Settings → Integrations)
• Check Firebase/Unity console - are events appearing there?
• Ensure app has internet connection during first launch

Revenue Not Attributed

Problem: Purchase events not linking to attribution

Solutions:

• Verify purchase events are being sent (check Firebase/Unity console)
• Ensure in_app_purchase event includes value and currency parameters
• Check that user installed within attribution window (default 30 days)

“Project Not Found” Error

Problem: SDK shows “Project not found” or “No matching project for package name”

Solutions:

• Verify your package name (Android) or bundle ID (iOS) matches a project in your BoostOps dashboard
• Check Tools → BoostOps → Settings - should show detected package name
• Go to BoostOps dashboard and verify project has correct package name/bundle ID configured
• Package names are case-sensitive and must match exactly (e.g., com.yourstudio.game)

Need Help?

Still stuck? We’re here to help:

• BoostLink Troubleshooting - Deep linking issues
• FAQ - Common questions
• Contact Support - Email or live chat

---

Ready to optimize your campaigns? Check out Attribution Reports to see which channels drive the most revenue.