Understanding Marketing Insights in Xilnex for Lark

Overview

Marketing Insights brings your campaign, voucher, and outlet performance data into Lark automatically, so you're not stuck exporting CSVs and stitching spreadsheets together to know how a campaign is doing.

This article covers what you'll see once Marketing Insights is set up.

Before you begin

You'll need a Marketing Insights base already created. If you haven't set one up yet, see [Creating a Base in Xilnex for Lark].

What's inside your Marketing Insights base

Your base contains three tables:

Table	What it shows you
Campaigns	Campaign goals, start and end dates, and overall performance
Vouchers	Which vouchers are actively being used, and how they're performing
Stores	Which outlets are driving the most revenue

Example Voucher Master table.

How data gets here

Your Xilnex data syncs into Lark automatically at the 30 minutes interval. There's nothing to trigger manually. Your dashboard is ready with the previous day's activity each morning.

Automatic alerts and summaries

Campaign Expiry Alert: an optional notification sent to the assigned user a few days before a campaign ends, so there's still time to act.
Underperforming Vouchers Alert: a weekly check that flags vouchers with a low redemption rate.
End-of-Campaign Summary: once a campaign ends, an AI-generated summary is automatically written into that campaign's summary field in the Campaigns table. Nobody needs to write it up manually.

Setting permissions

This base is mainly used by the Marketing team, not individual outlet managers. Access is set up by your IT administrator in Lark, the same as any other base (see [Creating a Base in Xilnex for Lark] for the general steps). A few things specific to Marketing Insights are worth calling out:

Campaigns table: lock every field except Campaign Notification User. That's the one field meant to be edited, since it controls who gets the expiry alert. Everything else is synced from Xilnex and gets overwritten on the next sync if changed.

Vouchers and Stores tables: lock these, and only give edit access to a small group of trusted people, so the synced numbers don't get accidentally changed.

To allow individual outlet managers to see only their own store's performance, your IT administrator can setup row-level scoping. It isn't scoped that way by default.

Turn ON Advanced permissions

Set only 'Records related to members themselves' which will auto detect the 'Campaign Notification User' column as the only editable column. Click Save to apply changes.

Locking specific fields or records like this uses Lark's Advanced permissions feature, which needs a Lark plan that supports it. On workspaces without that plan, this level of control isn't available. You'll only be able to set broad view or edit access per table, not per field.

Good to know

There's nothing to configure day to day. Once the base is set up, everything above happens automatically.
Like other bases, only data from after the base was created will appear. Nothing from before that is backfilled
Lark's Advanced permission setting is only for paid Lark plans.