Registration Steps

1. Navigate to Developer Tools → Testing Console in Singular platform
2. Click Add Device button
3. Select Device Type from dropdown:
   • Android: Prefer Google Advertising ID (GAID/aifa), AppSetID (asid), or AndroidID (andi) in that order
   • iOS: Use IDFA when available (requires ATT consent), otherwise use IDFV
4. Enter Device ID captured from device
5. Provide distinctive Device Name for easy identification
6. Click Save Device to complete registration

Android Device Identifiers

Recommended Method: Use Singular Device Assist app (Android) to retrieve GAID/aifa.

Alternative Method: Enable Singular SDK logging and capture identifier from Android LogCat:

SingularConfig config = new SingularConfig(SdkKey, SdkSecret)
    .withLoggingEnabled()
    .withLogLevel(1);

Sample LogCat Output:

2023-06-01 15:48:32.224 27442-27560/com.singular.test D/Singular: DeviceInfo [worker] - andi : 8868adc2f7ffffff
2023-06-01 15:48:32.224 27442-27560/com.singular.test D/Singular: DeviceInfo [worker] - asid : 12dc3652-5e46-f2bb-a93a-b3c092ffffff
2023-06-01 15:48:32.224 27442-27560/com.singular.test D/Singular: DeviceInfo [worker] - aifa : 3bbc76b0-cebb-4a9f-b6ec-10ca1affffff

iOS Device Identifiers

IDFA Capture: Use when ATT framework implemented and tracking authorized.

Method 1: Singular Device Assist app (iOS) - grant tracking permission when prompted.

Method 2: Log IDFA in Xcode debug console:

// Example in Swift
print("IDFA", ASIdentifierManager.shared().advertisingIdentifier.uuidString)

// Example in Objective-C
NSString *IDFA = [[[ASIdentifierManager sharedManager] advertisingIdentifier] UUIDString];
NSLog(@"IDFA: %@", IDFA);

IDFV Capture: Use when ATT not implemented or tracking not authorized.

// Example in Swift
print("IDFV", UIDevice.current.identifierForVendor!.uuidString)

// Example in Objective-C
NSString *IDFV = [[[UIDevice currentDevice] identifierForVendor] UUIDString];
NSLog(@"IDFV: %@", IDFV);

Purpose

Validate custom user ID properly transmitted to Singular for cross-device user tracking and analytics.

Testing Procedure

1. Register device in Testing Console
2. Open app on test device
3. Trigger action that sends user ID (e.g., login) if not sent automatically
4. Expand event details in Testing Console and verify custom_user_id field contains expected value

Troubleshooting

If custom user ID not appearing:

• Verify method setting user ID actually called at appropriate time in app flow
• Add Singular SDK event named "setting_custom_user_id" for visibility in Testing Console
• Check SDK logs for user ID assignment confirmation

Purpose

Verify event tracking implementation sends events with correct names and attributes to Singular.

Testing Procedure

For each event implemented in SDK integration:

1. Trigger event in app and verify event appears in Testing Console with correct name
2. Click event row to expand details and confirm Event Data section contains expected attributes

Troubleshooting

If event not appearing:

• Verify app opened after device completely registered in Testing Console
• Check Export Logs for event (available after ~3 hour delay)
• Confirm event triggering code executed properly in app

Additional Resources

• Understand Event Measurement
• Singular Standard Events Reference

Purpose

Validate revenue tracking implementation correctly reports purchase amounts, currency, and additional revenue details.

Testing Procedure

For each revenue event type implemented:

1. Trigger revenue event in app and verify event appears in Testing Console
2. Expand event row and confirm following fields present:
   • pcc - Currency code (e.g., USD, EUR)
   • r - Revenue amount
   • Additional revenue event attributes if implemented

Additional Resources

• In-App Purchase Validation FAQ

Purpose

Verify deep linking implementation correctly handles Singular Links and directs users to intended in-app destinations.

1. Set Up Test Destination

1. Navigate to Settings → Apps in Singular platform
2. Find app and click to open configuration
3. Add deep link destination matching destination handler code in SDK integration recognizes

2. Create Test Link

1. Go to Attribution → Manage Links and select app
2. Click Create Link
3. Under Link Type, select "Custom Source" and under Source Name, select "Email"
4. Provide link name
5. Expand Link Settings and Redirects section
6. Select test destination from Deep Link dropdown
7. Enter website URL in Fallback Destination for Other Platforms field
8. Click Generate and copy link from Click-Through Tracking Link field

3. Test Link Functionality

1. Ensure app installed on test device
2. Email copied link to test device
3. From device, open email and click link - app should open displaying intended page/content
4. In Testing Console, verify Deep Link value appears in Session arguments

Android Testing Alternative

Test Android deep links using ADB (Android Debug Bridge) for command-line validation.

Prerequisites:

• Install ADB (included in Android SDK platform tools)
• Enable Developer Options and USB debugging on device
• Connect device to computer via USB

Test Command:

adb shell am start -W -a android.intent.action.VIEW -d "https://yourdomain.sng.link/xxxxx?_dl=yourapp://deeplink"

Troubleshooting

Issue: Deep link opens new app instance instead of switching to existing instance.

Solution: Add following to activity in AndroidManifest.xml:

android:launchMode="singleTask"

See Google's <activity> documentation for launchMode options.

Purpose

Verify deferred deep linking properly handles links clicked before app installation, directing users to intended destination on first launch.

Testing Procedure

1. Check session event in Testing Console to confirm deferred deep linking enabled
2. Set up test destination and link following deep linking steps above
3. Uninstall app from test device
4. Reset device Advertising Identifier
5. Add new identifier to Testing Console
6. Email deep link to device and click link from device
7. Link should redirect to app store - install app (for local builds, sideload from Android Studio or Xcode instead of store version)
8. After installation, open app - should display intended page/content specified in deep link
9. In Testing Console, verify deferred deep link value appears in first session event

Purpose

Validate uninstall tracking implementation correctly detects and reports app uninstalls for churn analysis.

Prerequisites

Before testing, verify:

• FCM/APNS token sent to Singular (see Android SDK: Tracking Uninstalls and iOS SDK: Tracking Uninstalls)
• FCM Server Key (Android) or iOS Push Certificate entered in App Configuration page

Testing Procedure

1. Install app on real device (not emulator)
2. Open app so install registered with Singular
3. Uninstall app from device
4. Verify uninstall event using one of following methods:
   • Export attribution logs and find uninstall event (may take couple days to appear)
   • If postbacks configured to internal BI system, receive postback about uninstall
   • Contact Singular Support or Customer Success Manager for validation assistance

Common Causes

If device registered and no events appearing in Events Log, verify following:

• Live Monitoring Required: Testing Console only shows events live when device selected and 🟢 Live indicator visible. Does not retrieve historical events
• App Opened: Ensure app opened on test device to generate session event
• Events Triggered: If testing specific events, ensure triggering actions performed in app
• Device ID Accuracy: Double-check correct device ID entered in Testing Console
• Device ID Type: For iOS without ATT prompt, cannot use IDFA - must use IDFV instead

SDK Version 12.0.0+

Starting from Singular SDK 12.0.0, no need to test _InstallReferrer event. Once app pushed to store, SDK places _InstallReferrer data in first session automatically. Only need to verify session appears in Testing Console.

SDK Version <12.0.0>

For older Android SDK versions, still need to check _InstallReferrer event in Testing Console for proper installation attribution.

Verification Steps

Double-check IDFA accuracy:

• Use Singular Device Assist app (iOS) with tracking permission granted
• Log IDFA in Xcode debug console
• Check Export Logs (after 1+ hour) with "App Tracking Transparency status" field - value 0 (Undetermined) means ATT prompt not shown

Configuration Checks

1. Device Settings: Verify Settings → Privacy → Tracking shows "Allow Apps to Request to Track" enabled
2. ATT Prompt: Confirm ATT prompt appeared during testing - if not shown, IDFA not tracked
3. Reset IDFA: If device used previously, reset advertising identifier via Settings → Privacy → Tracking
4. SDK Version: Verify latest Singular SDK version integrated correctly
5. SDK Initialization: Confirm SDK initialized in AppDelegate or SceneDelegate per documentation
6. Check Errors: Review Xcode console for SDK initialization or tracking errors

If issues persist after following steps, consult Apple ATT documentation or contact Singular integration engineer.

Deletion Process

1. Click Edit icon next to device in Testing Console
2. In sidebar that appears, click Delete Device
3. Deletion clears all event logs and removes device's attribution data from Singular

See also: How to reset device for install attribution testing

Reset Requirements

To re-test SDK integration with same device, remove locally cached data from device and clear device's attribution in Singular platform.

Android Reset Steps

1. Close app and confirm not running (use Force Stop if available)
2. Go to Settings menu
3. Navigate to Apps, long press on app, select App Info
4. Select Storage and click Clear Cache and Clear Data
5. In Testing Console, select device and click Edit icon, then Delete Device to remove attribution

iOS Reset Steps

1. Close app and uninstall from device
2. In Testing Console, find device and click Edit icon, then Delete Device to remove attribution

Events Log Interface

After registering device and sending events, events appear in Testing Console Events Log with real-time updates.

Event Details

Click event row to expand and view complete event details as sent from app, including all parameters and attributes.

Resolution Priority

Must resolve before production release - these issues prevent core functionality.

Common Error Issues

• No Sessions Received: SDK not initialized or not sending data to Singular
• Invalid SDK Keys: Incorrect SDK key or secret configured
• Platform Mismatch: App reporting wrong platform identifier

Resolution Approach

1. Review Error Description for specific guidance
2. Consult SDK integration guide for affected platform
3. Verify SDK configuration and initialization code
4. Re-test using Testing Console after fixes
5. Run new SDK Audit to confirm resolution

Resolution Priority

Should resolve for best practices - integration functions but improvements recommended.

Common Warning Issues

• No Custom User ID: Custom user ID not implemented for cross-device tracking
• Revenue Tracking Issues: Revenue events not following best practices
• Missing Event Attributes: Events tracked without recommended attributes

Resolution Approach

1. Assess business impact of missing feature
2. Review implementation documentation for feature
3. Implement if feature aligns with requirements
4. Test implementation using Testing Console

Resolution Priority

Review and decide - optional features that may not apply to specific use case.

Common Info Issues

• Deferred Deep Linking Disabled: DDL may not be relevant to marketing strategy
• Uninstall Tracking Not Configured: Uninstall tracking optional based on requirements
• Optional SDK Features: Additional features not critical for basic functionality

Resolution Approach

1. Review Validation Name to identify optional feature
2. Determine if feature relevant to business requirements
3. If not relevant, safely ignore issue
4. If relevant, implement following SDK documentation