A Snowflake data sync, UTM capture, and downloadable webhook history
Set up a Snowflake sync that maps fields and refreshes on a schedule, carry sign-up UTM tags into a webhook, and download incoming webhook history as a CSV.
01 ·Sync data in from Snowflake on a schedule
Snowflake joins the third-party integrations a broker can connect. After connecting, a broker maps a warehouse down through its database, schema, and tables, joins tables on a shared identifier where the data spans more than one, and points each Snowflake field at the member field it should fill. A sync interval sets how often the data refreshes, with a choice of two, six, or twelve hours or a custom time, and the sync runs on that schedule once the setup is saved. A custom-fields view lists every field and the integration it draws from.
A brokerage already keeps its trading and account data in a warehouse. Mapping those fields into a member's profile and refreshing them on a schedule means the loyalty program reads from the same numbers the back office trusts, which is the groundwork for rewarding real trading activity.
02 ·Carry sign-up campaign tags into a webhook
When a visitor lands on a community's domain with UTM tags on the link and goes on to join, those tags now travel with them. The source, medium, and campaign values are read on arrival and included in the webhook that fires when a member joins, so a broker's own systems see which campaign brought each new member.
A broker spends real budget pointing campaigns at the community, and the question afterwards is which one paid off. Passing the campaign tags through to the join webhook ties a new member back to the link they came from, which is what makes referral and acquisition spend measurable.
03 ·Download a community's incoming webhook history
The history of incoming webhooks can now be downloaded as a CSV. Each row carries the details that came in, the dispatch status, the reason where one did not go through, and the time it arrived, so a broker has a record to reconcile against the system that sent it.
Email templates gained a custom variable block in two kinds, text and HTML, each shown in the email only when it has content, with the HTML block expanding to a full editor and rendering on save.
28 JulA store voucher product can carry an optional redemption instruction, written in its settings and shown in the product details of a member's order history.
28 JulThe Customise User Profile settings now list every field from the member list, rather than a fixed set, as fields a broker can choose to display.
28 Jul