brainCloudAdmin group

Paul Winterhalder

Hi @gyutaelee ,

Use the direct global property call from the bridge. It will return secret properties.

https://docs.braincloudservers.com/api/cc/bridge/getglobalproperty

i.e. bridge.getGlobalProperty(propname);

I hope that helps!

Paul.

Paul Winterhalder

Hi Jongdae,

Great questions!

Before I answer them, though - heads up that we have an update to LiveOps campaigns coming next week. It provides a great analytics screen for campaigns, so you can see how they are impacting player engagement, monetization, retention, etc.

That said, you are pointing out some additional caps that we'll want to address quickly:

The management APIs for campaigns are following in a future release - but we can see about getting some APIs that specifically target updating the custom JSON for campaigns and scenarios. I'm going to see if I can slip that into next week's release.
Right now campaign enrollment is only triggered upon login. We're planning to add an optional "trigger": true flag ot the getMyCampaigns() call, though - which would allow games to make that call periodically (i.e., after the player finishes a "match," perhaps), as makes sense on a per-game basis. Longer-term, we are considering adding an RTT channel that clients could listen to to be notified of when a new campaign launches...
Feature maturity - with the 6.0.1 update that we're releasing, the feature is mature enough to build upon. We'll continue to extend it, but we can do so without invalidating the foundation we have built.
Cross-environment campaign management - we'll be adding some features to allow easy importing / exporting of campaigns between environments. Plus the S2S management api will help too... All coming this fall!

I hope that helps,

Paul.

Paul Winterhalder

Hi @noah ,

brainCloud 6.0.1, which will be released next week, adds new data stream events for virtual item purchases.

We'll keep #2 and #3 in mind as we continue to evolve things going forward.

Thanks for pointing out MongoDB CDC - I wasn't familiar with that capability before. We'll take a harder look at it.

Cheers!

Paul.

Michael Costa

Thanks for letting us know and your own solutions! We'll see if we can patch this into the JsonFx library we're using for future versions of brainCloud to avoid these edge cases.

johnh

Created case 14475

johnh

Added case 14474

JasonL

Thanks for the detailed report, you haven't missed anything, the current AuthenticateApple implementation only accepts a single Apple client ID. It performs a strict equality check on the token's aud claim, so there's no built-in way to configure multiple valid client IDs. The implementation may be accepting a list of client IDs and checking membership instead of a single value. I'll forward this request to the team for consideration.

JasonL

Thanks for the suggestion, you’re correct that current segment criteria only support value comparisons and simple membership/range checks, so there’s no explicit “attribute does not exist / is not set” operator, nor any way to reference segment membership (e.g., “is in segment X” / “is not in segment X”) in segment definitions, so we don’t currently have a real workaround that delivers the exact semantics you’re asking for, I’ll forward your request to the team for consideration.

Paul Winterhalder

Hi @moondory77 ,

The work on this is running in our development environment. The Builder API support is in place - and we're currently looking at the possibility of adding it as a new tab in the Deployment screen of the Portal.

Paul.

Paul Winterhalder

Hi,

Apologies for the slow response.

We don't have any calls that could directly handle a "file" of profileIds. We do have a few "toBatch" calls that are callable from S2S though - so you could probably have an offboard system make those calls - and call braincloud to send the notifications in batches.

Where are these profileIds coming from? An offboard analytics system of some sort?

To answer your questions:

We are planning a revamp of our notifications system and it's APIs. I'll add this conversation so that it will be considered as we're planning that.
As mentioned above, using one of the "Batch" calls would make the most sense - and keep your API counts reasonable
There's an API call to call the SendRichPushNotificationWithParams, plus a second api call for the sending the push notification itself. So that would be <numReceivers> x 2 for API costs. Less if called from within a script. But the *Batch() calls would be
Substitutions and custom metadata/custom data - the current APIs don't - so you'd probably need to handle those client side. Are the substitutions highly personal - like player's name?

I hope that helps to clarify things,

Paul.

brainCloudAdmin

Posts

Member List