Case 13660 - investigating

Yes, the behavior you’re describing is expected with the current implementation. RefreshMySegments, RefreshPromotions, and login will not attach the promotion to users who are already in the segment, because the system is designed to only grant automated promotions when the user enters the segment (i.e., when it shows up in enteredIds). The fact that Reset Segments or Re‑evaluate All Segments fixes it is also expected, because those actions force the user back through the segment‑entry logic.

We’re working on a fix to make this smoother. The practical effect going forward will be that, when a new automated promotion is created or attached to an existing segment, the next segment refresh will automatically apply it to all currently‑eligible users in the background, without you needing to reset or re‑evaluate segments manually. This should make the behavior more predictable, especially when you have a large number of existing users already in that segment.

Case 13633 - [implementing]

Our automated promotions were designed to pull members of a segment into a promotion, which is why they can trigger notifications. When an automated promotion fires for a user, they can be notified, and that notification is intended to draw them back into the game. So startTime is effectively the wall‑clock time when the batch job processes that user, not when the user logs in. A user who never logs in will have their promotion silently expire in the background.

I’ve forwarded your request to our team to see if we can look at adding a flag that lets developers specify that an automated promotion should only trigger on login, which would likely align well with the kind of “starter‑package” use case you described.

@gyutaelee I will investigate the Per Promotion Deployment option you requested.

As I was working on this I thought there may be a workaround for you that you would like. This could work for your team with minimal effort and on your current version of brainCloud portal.

My solution hides the promotion so that only users you flag as TESTERS will see it.

This would let your PROD testers gain the benefit of the no-ads promotion without disrupting your monetization.

Within Automatic Promotions, there is the option to Target members of any of these segments.

cb1f4861-16f8-432a-bb22-4b71dc0b0ce1-image.png

Within Scheduled Promotions, there is the option to Offer this promo to: Only users in:

2a5f3a28-91ba-4f2c-bb1c-5a2c04ead1e5-image.png

Advancing to App > Design > Segmentation > Segments we can create a segment that filters to players that are flagged as Testers.

59f8d7bc-3640-450f-ab67-086af9b8acdd-image.png

Now, segments need to have at least one more criteria, so let's choose something like has logged in at least 1 time.

d86e5f6d-ded8-4c7e-ab26-1c07f9813f0e-image.png

Save this Segment

IMPORTANT! Add the segment to your Promotion
This will limit the promo to only eligible users. Noone else sees it!
7aca6582-cff3-4469-ae98-6339b341ba06-image.png

Next we will need to flag some users as Testers. For a DEV app, the easiest way to do this is to go to the User Browser, RECENTLY ACTIVE and pick players (your testers) with recent activity.

ec366981-f641-4833-87f2-64798766555c-image.png

GO TO USER to bring up their user summary and check the IsTester checkbox.
d1094afd-ca63-4ce6-8070-477c879fb1d4-image.png

Testers get a special icon
e02b71bc-db5b-4127-a6a7-1528697aee6f-image.png

Next, we will return to Segments.

Segments are automatically processed overnight, but you can Refresh Segments immediately with the REFRESH SEGMENTS button. Please note: refreshing segments processes every player so this process can take a while and preferably left to low-traffic times of day.

e306d8e0-553d-475c-a780-43fbed29a271-image.png

After processing completes, we can check the cohort of testers by returning to the User Browser choosing BROWSE, and Browse Within A Segment.

43a330f6-e572-4b0b-a8ca-c0d631e63240-image.png

These are my Testers, so everything worked.
a8b56bbb-536c-447b-9e7d-a8d8236ff165-image.png

Since only testers are eligible for the promotion, you are free to deploy it to PROD without affecting your monetization. And the PROD Testers you select will be able to gain the workflow benefit of no ads.

Could you let me know if this solution solves your problem?

Let me know if you have any questions,
Regards
John
-Design

@Paul-Winterhalder , could you please respond to @noah 's inquiry?

It's been resolved. Thank you for your response!

Hey, thanks for reaching out. To answer your main question directly: yes, brainCloud's lobby and matchmaking system can trigger an Edgegap server deployment automatically. You do not need to build a custom C++ room server to make this work.

https://github.com/getbraincloud/examples-cpp/tree/develop/relaytestapp

The relaytestapp example on the develop branch of examples-cpp is a working client example that does exactly what you are describing. It uses brainCloud lobbies and matchmaking to find a match, and once the lobby is ready to launch, brainCloud handles spinning up the Edgegap server and passes the connection details back to all players through RTT.
The server configuration you see in the screenshot is what ties everything together on the brainCloud side. That entry defines which Edgegap application to deploy, which regions to consider based on the selected beacons, and the credentials needed to make the deployment call. Once that server is linked to a lobby type, the entire launch sequence is handled for you.
The relaytestapp is a solid starting point to see this end to end.
Screenshot 2026-05-07 at 12.13.17 PM.png

@Paul-Winterhalder Hello! Here is my app Id "15675

Thanks @Brad-Hester !

We’re planning some major changes to our push notification system, it’s more than just adding a few titles and content fields to the templates. It's not a near-term, stay tuned!

Agreed @armitage - the bulk messaging feature is planned for the use case you describe... (and yup - still coming 🙂 ).

There are multiple leaderboards in the game separated by region, but aside from the region itself, they all use the same settings.

When creating them initially, cloning works fine. However, after they have been created, if I need to adjust various options, I have to edit each leaderboard one by one.

The main problem is that every time I save a change, the “Updated successfully” popup appears and covers the edit button, which makes consecutive edits across multiple leaderboards very inconvenient.

It would be much more efficient if there were a way to edit multiple leaderboards with identical settings at the same time. At the very least, moving the success popup to a location where it does not block the button would greatly improve usability.

Symptom
After updating from 5.9.2 to 5.9.3, iOS/iPadOS experiences gradual performance degradation during extended play sessions, eventually leading to app termination
This issue did not occur on 5.9.2
Suspected Code
In BrainCloudComms.cs - HandleResponseBundle, the following line was added in 5.9.3:

jsonData = JsonWriter.Serialize(JsonReader.Deserialize(jsonData));
Concerns
This performs a full deserialize → reserialize on every API response
Immediately after, DeserializeJsonBundle parses the same data again — effectively parsing every response twice
Each response generates a large number of temporary objects (Dictionary, List, boxed values, strings) that are immediately discarded
On iOS with IL2CPP (Boehm GC), could this repeated allocation/deallocation pattern cause managed heap growth over time?
Question
Could this code potentially contribute to memory-related issues on iOS during extended play sessions?

You can find the Knowledge Base link on our documentation site, which is linked to https://getbraincloud.com/.9b4015ab-4420-4d80-9368-5accf73b92c8-image.png

based on meta=false and script=false as a result, I only want to distribute items and products.
Please provide a sample body.

Hi,

This limit is adjustable on a per-app basis. I have reached out for more information (via email) to confirm how many divisionsets would satisfy your requirements.

Paul.

Hi @jesgonzalez ,

Yes - unfortunately, you need to use AuthenticateExternal. We do not have official middleware status with Xbox. We've been trying for years - but as anyone who has dealt with Xbox in recent years knows, they are extremely resource-constrained.

Paraphrasing our most recent interactions

Due to extremely limited resources and a couple of years of re-orgs, Microsoft won't adopt or support new tools or technologies unless we can prove there’s a clear and active need from developers working on officially approved Xbox titles.

(We actually had been making progress on this a few months ago - but then the personnel we were working with got laid off... So now we're at the back of the bus again.)

Unfortunately, our lack of status means we can't provide clear details on how to do it, but we do have some service partners / contractors / consultants we can refer you to who can quickly connect you. If you want to reach out to us via our Support widget, we can put you in touch with them.

Oh - and be sure to mention this situation to your Xbox account rep (if you are lucky enough to have one). It's only via pressure from the dev community that we're going to get unblocked in this area!

Paul.

Note - the system allows a maximum of 15 anonymous ids. If you exceed that, it will delete the oldest ids to keep you at 15.

[Background - this used to be totally unlimited - but they really added up for some apps - so we implemented this behaviour and set the max of 15 as being "more than reasonable enough to handle all use cases!" 🙂

Paul.

Hi @bkmitchell ,

thanks for reaching out.

Unfortunately our built-in relay server tech doesn't support what you need for Unity WebGL multiplayer.

Most brainCloud devs implementing your use case would integrate with Photon or Edgegap for their multiplayer for this reason. They both work well and work well with brainCloud!

[PS - This is an area of ongoing development for us though and we aim to fill this gap in the future. I can't comment on timelines for that though...]

Paul.