Reward LinkedIn activity with XP, run LinkedIn under your own brand, and feed webhook data into member fields
Award XP for a like, comment, or repost on LinkedIn, run the LinkedIn connection under your own brand, and map incoming webhook data to a member field.
01 ·Award XP when a trader engages with a LinkedIn post
A broker connects a LinkedIn account, picks the page it draws from, and turns on social activities, which polls the latest eight posts and lets the broker choose which ones appear as quests. A trader connects their own LinkedIn account to take part, and from a post they can like, comment, or repost. Each action runs against LinkedIn and awards the XP set for it, with the button moving to a claimed state once it lands. A daily check re-reads the like, comment, and repost lists and confirms a trader who claimed XP is still in them.
A broker who posts on LinkedIn wants the audience it reaches to count toward the loyalty program, not sit apart from it. Tying XP to a like, a comment, or a repost folds LinkedIn reach into the earn-and-spend reward loop, and the daily re-check keeps the XP tied to activity that holds.
02 ·Present the LinkedIn connection under your own brand
The LinkedIn setting now carries three branding options for how a trader sees the connection step. Returning.AI branding uses the platform's own application, white-label branding runs on a broker's own LinkedIn application with their organisation ID keyed in, and a lite option presents the broker's name over a shared application. A broker picks the one that matches how they want to appear.
A broker building a community under their own name does not want a trader to meet a third-party brand at the connection step. Running the LinkedIn link on the broker's own application, or presenting their name over a shared one, keeps the loyalty program looking like the broker's own product end to end.
03 ·Map incoming webhook data to a member field
An incoming webhook can now write to a member's custom fields, not only feed a chat. In the webhook setup a broker picks a location: chat keeps the existing behaviour, and user fields opens a mapping panel. There a broker adds one or more mappings, each pairing a custom field with the incoming value that should fill it, and adds another row for the next field. Incoming data is queued and processed in turn so a burst of webhooks still lands.
A broker pushing data from their own systems wants it to land on the member record where the rest of the loyalty program reads from, not in a chat message. Mapping each incoming value to a custom field lets a broker keep a trader's record current from an outside source, which milestones and referral conditions can then act on.
04 ·Add a call-to-action button to a banner and cap how often it shows
The banner setting gained a call-to-action button and a set of display controls. A broker writes the button text and the link it opens, and positions it inline with the message or below it, aligned left, centre, or right. Display settings set a maximum number of times the banner shows per trader, how often it reappears, and a limit on call-to-action clicks, with advanced conditions deciding who sees it. The Banners list reports the clicks each banner's button drew.
A banner that runs without limit stops being read. Letting a broker attach a call-to-action and cap how often it shows makes the banner a measured prompt toward the next step, with the click count showing whether traders acted on it.
The Gamification Log gained a download link that exports the log to a CSV.
21 MarBadge management was carried over to the rebuilt community settings, with its member list set to load on scroll.
27 Mar