Developer Payload Example
1. A/B Test Analysis
Pass your experiment variant in the Developer Payload to segment sessions by test group and compare gameplay metrics across cohorts directly in the 6Labs dashboard.
Example payload
"variant": "variant_a or variant_b" }
What you can do
- Compare sessions side-by-side across
variant_aandvariant_b. - Identify which variant leads to fewer friction points or longer engagement.
- Use AI-powered agents to surface behaviour differences between cohorts without manual review.
2. User Segment Behaviour
Tag sessions with your user classification to understand how different player types interact with your game.
Example payload
"days_since_install": 45 }
What you can do
- Filter the dashboard by segment (
new,returning,whale) to review segment-specific sessions. - Detect onboarding friction that only affects new players.
- Understand what high-value players do differently compared to churned users.
3. Campaign Attribution
Include acquisition channel and campaign ID so gameplay behaviour can be traced back to specific marketing campaigns.
Example payload
"campaign_id": "camp_summer_2026" }
What you can do
- Correlate campaign spend with actual in-game behaviour, not just install counts.
- Identify which acquisition channels bring players who engage deeply versus those who churn quickly.
- Surface sessions from a specific campaign to validate creative messaging alignment with gameplay expectations.
4. Friction Point Detection
Combine user segment and progression data in the Developer Payload to pinpoint exactly where specific player groups drop off.
Example payload
"level": 3,
"tutorial_completed": false }
What you can do
- Filter sessions by players who did not complete the tutorial to observe their experience.
- Use SixthSense agents to detect common patterns in sessions where players stopped playing.
- Validate fixes by comparing post-patch sessions with the same segment tag.
5. Feature Validation
Tag sessions with a feature flag or build version to validate whether a newly shipped feature is working as intended for real players.
Example payload
"feature_flag": "new_inventory_ui" }
What you can do
- Review sessions from build
2.4.1to see how players interact with the new inventory UI. - Compare behaviour before and after the feature release using sessions.
- Quickly identify regressions by reviewing sessions tagged with the feature flag during rollout.
Passing the Developer Payload
The Developer Payload is a single string parameter. The example payloads above are illustrative JSON — serialize your metadata to a JSON string before passing it to Init() or StartSession(). For example, in Unity (C#):
string payload = JsonUtility.ToJson(myData);
// or, with Newtonsoft.Json: JsonConvert.SerializeObject(myData)
SixLabsSDK.Instance.StartSession(inGameId, payload);
See the Unity SDK or Unreal SDK documentation for the exact method signatures.
Table of Contents
Table of Contents
Document Rev. 1.0