SDK Initialisation
Owner: Technical
Priority: High
Realistic effort: 2–4 hours
Due: Set start date →
Not started
Guide
Live validation
SDK console
Sample projects
Timeline & reminders
Validation checklist
Auto-checking
All mandatory tasks validated → triggers SE sign-off → Salesforce updated → go-live confirmed
SDK Testing Console
Attribution Check
Direct connection to Singular Testing Console API (BETA). Register device → launch app → events stream in real time. Sessions auto-expire after 1 hour. Without an API key, demo mode loads sample events.
Time
Device
Event
Bundle
Flag
◎
No events yet
Register a device and launch your app
Auto-polling · refresh in 5s
Attribution Details API — verify which campaign/source attributed a device. Calls
GET /api/v1/attribution_details. Requires your Singular API key (same key used for the SDK console above).Check device attribution
◎
No attribution data yet
Enter a Device ID and click Check attribution
⚠️ Attribution data may take up to 24 hours to populate after install. For unattributed organic installs, the source will show as "Organic".
These sample projects demonstrate every mandatory and optional feature. Use them as reference while implementing. Each file shows the complete working code — replace
YOUR_SDK_KEY and YOUR_SDK_SECRET with your credentials from the Singular dashboard.Integration timeline
Realistic estimates based on Singular's official documentation + SE field experience
Set a start date and click Generate timeline
Active reminders & alerts
Auto-generated based on task status and due dates
Generate a timeline to activate reminders
⚙ What you need to configure to go live
Complete these backend configurations in parallel with SDK integration
Singular API Key Required for console
Used by the SDK Testing Console and Attribution Check tabs in this portal.
Dashboard → Settings → API Keys (top-right menu)SDK Key & Secret Required
Goes directly in your app code. Each platform (iOS / Android) has its own pair.
Dashboard → Apps → [App] → SDK KeysGoogle Play Licence Key Required — Android
Enables install validation and deep link integrity on Android. Without it, DDL may fail silently.
Dashboard → Apps → [Android App] → Licence KeyFCM HTTP v1 Service Account Required — Uninstall
Upload Firebase service account JSON (not legacy server key) for Android uninstall tracking.
Dashboard → Apps → [Android] → Configure UninstallAPNs .p8 Key Required — Uninstall iOS
Apple Push Notification service key for iOS uninstall tracking. Upload in Singular dashboard.
Dashboard → Apps → [iOS] → Configure UninstallUniversal Links / App Links Required — Deep links
iOS: AASA file hosted at
/.well-known/apple-app-site-association. Android: digital asset links verified domain. Configure BEFORE writing any deep link code.Dashboard → Apps → Configure Deep-Link URLsSingular Link Domain Required — Deep links
Your tracking subdomain used in SDK config and referral links.
Dashboard → Singular Links → Domains → yourapp.sng.linkMixpanel / CDP Partner Config If using Global Props
Add Mixpanel (or Segment / RudderStack) as an attribution partner so Singular forwards install data.
Dashboard → Attribution → Partner Configuration → Add PartnerSalesforce / CRM Tracker For SE tracking
Update your Salesforce opportunity with the onboarding task statuses (Task 4.1). When all 7 tasks pass the go-live gate, mark the opportunity as "Technical Win".
Dashboard setup items (deep links, uninstall, Google Play key) must be completed BEFORE writing the corresponding code — not after. Misconfigured dashboards are the #1 cause of failed go-live validations.