Milestone webhooks in batches, and Coming Soon access by role
Milestone webhooks can send scheduled batches, a role can see member emails and IDs in chat, and Coming Soon store items follow each role's access.
01 ·Milestone webhooks, one request each or in scheduled batches
A Milestone custom webhook can send in Batch as well as Singular, on the same scheduled delivery as Gamification and Spin the Wheel webhooks. A batch collects stage upgrades, group upgrades and stage downgrades and sends them in one POST at the end of each interval, from hourly to monthly in UTC. An admin sets how many events one request carries, up to 1,000, and the platform splits a busier interval across several requests. A milestone a client reaches twice arrives as two events, and Send Test posts a sample that grants no rewards.
In both modes, the community's own user identifier is available on every event, and the default body and the variable list include it. A body an admin has already written keeps its own fields.
A broker's CRM can take milestone progress on a schedule it chooses and match every event to the client record by the broker's own ID.
02 ·Member email and ID in channel profile popups, by role
A new role permission, off by default, shows a member's email, the community's user identifier, or both, in the member profile popup in any channel the role can open. The admin picks which of the two the role gets. Members' privacy choices still apply: an email a member has chosen to hide shows as asterisks. Clicking a value copies it.
Staff who answer clients in channels can match a member to the broker's own records from the conversation, and the admin decides which roles get that view.
03 ·Coming Soon store items follow each role's and user's access
Coming Soon categories and products, which launched on 28 Sep with access fixed at @all, view only, now take role and user access settings. While the status is on, an admin can give each role or user Full Access, View Only or Cannot View. Until launch the item is view only for anyone with access, and Cannot View keeps it out of sight. When Coming Soon is switched off, the saved access applies.
A broker can preview an upcoming reward to a VIP role and keep it from everyone else until it goes on sale.
04 ·Store widget settings, regrouped
The Store widget's settings are in three sections: Widget Header, Store and Purchase History. A widget can show the store, the purchase history or both, and with only one the tabs disappear. The balance bar's parts (community logo, community name, currency icon and currency name) each switch on separately.
In the Store section an admin picks the categories the widget shows, sets a maximum of 1 to 6 products a row and sizes the product card in pixels, 324 by 400 by default. Purchase History sets which order details and browsing controls clients see. A widget that follows the store settings keeps that link through layout-only edits.
A broker can fit the Store widget to the space its client portal gives it, and show only the categories and order details that belong there.
05 ·The Email Log over the logs API
The community logs API returns the Email Log as well, one record per recipient, with the sender, the recipient's roles and tags, a status of Sent, Failed or Queued, and any details. A batch ID narrows it to a single send. It comes back as JSON pages or a CSV file on the same terms as the other logs.
A data team can see which clients each email reached, and which failed, in the reporting that already pulls the other loyalty logs.
Salesforce connections can use a sandbox org: the Connect form asks for Production or Sandbox, and existing connections stay on Production.
19 OctThe Order History CSV export adds a Redemption Method column and a column for each redemption-method custom field, named by method and field.
19 OctSwitching a coin expiry between One-time and Cycle-based keeps the expiry form open with its entries.
19 OctWorkflows with a raw request body inside a router or error handler open in the editor and in run history.
19 OctData Workflows appears in the settings menu for every staff member with the Custom Workflows permission.
19 OctOpening a community with a very large member list takes less work.
19 Oct