administrators group

Paul Winterhalder

That patch has been deployed @jongdae-won - give it a try!

Paul Winterhalder

We have a patch being deployed today that will allow you to create promotions that will allow you to target both existing and new members of a segment. We plan to have that deployed by the end of the day.

We hope that this will address the primary issue.

Your latest message seems to indicate that even new users to a segment are not getting the promotion offer... that does seem odd. I will point out that segments only get refreshed nightly and upon login - so if a new stat meant that they should be added to a new segment - the new segment and/or promotion wouldn't be refreshed until they logged back in again...

Unless... your app is making this call before it brings up the store:
https://docs.braincloudservers.com/api/capi/appstore/refreshpromotions

Could that be [that specific] issue?

In any event - we are hopeful that the patch should address your primary concern. We'll post here once it has been deployed.

Paul.

Paul Winterhalder

Hi @dbgtdbz2 - we certainly don't have an api for that sort of thing right now.

Can you send a private chat in via the support system - addressing me - and give me a heads up of what you're up to?

Thanks!

Paul.

JasonL

I’ll forward your request to the team for review...

JasonL

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.

JasonL

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.

JasonL

Thanks for the suggestion and the explanation of the workflow benefit. I’ll bring this request to our team for review and follow up here...

JasonL

@noah The team is working on this, and we’ll share any progress here once there’s something concrete to report.

JasonL

Hi, thanks for the detailed report. At the moment, there isn’t a per-promotion exclusion toggle for deployments; the currently recommended way is to keep Preserve Products+Pricing & Promotions in the target environment. Your request for selective promotion exclusion makes sense. I’ll pass this along as a feature request for the team to consider.

JasonL

Hi @gyutaelee,

For one-way follow: brainCloud doesn’t have a built-in one-way “follow” graph, so you’ll need to implement your own follower/following system using one of the user data mechanisms (e.g. global or entity data) to track who follows whom. This keeps it independent of the Friends API, which is designed around mutual relationships. GetPresenceOfUsers() works with any valid profile IDs, it does not require a Friend relationship between the players to return presence info.
For the referral rewards question: I’m going to forward this to our team to review the best server-side approach for triggering rewards for both the referrer and referee once the milestone (like reaching level 3) is reached.

Thanks for the detailed explanation of your use cases.

administrators

Posts

Member List