- Experiment ID
2026-06-battlenet-social-sdk-migration- Experiment Type
- apex / user
- Previous Type
- apex / user
- Analysis Summary
- Keeps the path and messaging for moving Battle.net connections to the newer app-account model.
- Why It Matters
- Battle.net users may be asked to reconnect or migrate their account connection.
- Servers that rely on Battle.net linked roles may also need users to refresh those roles through the newer connection path.
- Detailed Description
- The default state retains the existing Battle.net connection entry.
- The comparison can replace it with the newer Battle.net app-account target and use migration messaging for the connection or linked roles.
- The current platform configuration still reads this experiment in the actual Battle.net replacement path.
- The two modified rows do not change the meaning of the enabled setting, so the established user explanation remains while timing and completion status remain unconfirmed.
- Focus Area
- Battle.net connection migration
- Importance
- high
- Default Config
{
"enabled": false
}- Variations
{
"0": {
"enabled": false
},
"1": {
"enabled": true
}
}- Previous Default Config
{
"enabled": false
}- Previous Variations
{
"0": {
"enabled": false
},
"1": {
"enabled": true
}
}