Bonus Report — Transaction Tags

Bonus Report — Transaction Tags Analytics

The Tags tab in IZI’s Bonus Report shows the structure of your bonus transactions broken down by the labels you assign at the point of processing. Instead of a single “total top-ups” figure, you see exactly how much came through a promotion, how much from corporate clients, and how much from manual compensation credits. Navigate to Analytics → Bonus Report → Tags to open it.

To get value from this report you need two things: a consistent transaction tag practice — labels your admins apply to each operation — and an understanding of how to interpret each row. The report answers three owner-level questions: where your revenue structurally comes from, how disciplined your tagging is, and how a specific promotion affected your average order value (AOV) — the mean amount per transaction.

What you see in the report

The page opens with a table where each row is one tag. For each tag you get:

Column	What it means
Tag	The label name you defined in the tags directory
Operations	How many transactions carried this tag during the period
Amount	Total volume of operations with this tag
Avg. transaction	Amount ÷ operations — mean top-up size for this tag
Share	Percentage of all operations in the period
No tag	Separate row: operations processed without any label

The date range selector at the top supports single-day, weekly, and custom ranges. For multi-location operators, you can view a single club or a consolidated network view.

How to read the data: three key lenses

Promotion effectiveness

If you use a promo tag or a campaign-specific label, compare its average transaction value against the baseline AOV for untagged operations in the same period. Three scenarios:

• Tagged AOV above baseline → the promotion is increasing top-up size; customers load more money, not just more often.
• Tagged AOV close to baseline → the promotion drives traffic volume but does not move the transaction amount.
• High operation count under the tag but small revenue share → either the promotion is niche, or tagging is incomplete.

Parametric benchmark: if your baseline AOV for the period is X and promotion-tagged transactions average AOV × 1.15–1.25, the campaign is working on ticket size. If the multiplier stays below 1.05 despite meaningful bonus budget, revisit the promotion threshold or mechanics.

Compensation monitoring

A compensation or manual_credit tag covers operations where an admin credits a customer to resolve a complaint or technical failure. A healthy level is occasional and scattered. If this tag’s share exceeds 3–5% of all operations and concentrates around a single admin or a single shift window, open the Shift Report and investigate who and when.

High compensation counts from one staff member do not automatically indicate abuse — they may simply be handling peak hours when hardware is less stable. But the pattern is worth examining rather than ignoring.

Revenue channel structure

If you tag corporate or partnership top-ups as corporate or b2b, the report shows you the real contribution of that channel. This matters when deciding whether to expand a partnership program: a corporate tag that consistently delivers above-average AOV and a growing share of operations is a signal the channel merits investment.

The “No tag” row — your discipline indicator

The No-tag row shows operations processed without any label. This is unstructured traffic: it counts toward total revenue but cannot be broken down analytically.

Practical threshold: a No-tag share under 10–15% is acceptable — some standard top-ups simply do not need a label. If the share climbs above 20–25%, the tagging protocol is breaking down and you need to address it with your team.

Steps when No-tag share is high:

1. Open Club → Transactions with the “No tag” filter and see which operation types are slipping through unlabeled.
2. If they are routine top-ups with no promotional context — simplify your protocol: reserve tags for non-standard operations only.
3. If promotional top-ups are going untagged — run a team briefing. Tagging criteria should be written into the shift handover checklist, not left to individual memory.

Comparing periods: tracking trends

IZI lets you pull the Tags report for any date range. A practical comparison framework:

What to compare	How to set it up
Promotion vs. control window	Promotion dates vs. the equivalent period the previous month
Rising compensation share	Last 30 days vs. prior 30 days
Seasonal cross-check	Current month vs. same month last year

For club networks, compare tag profiles across locations. It is normal for locations to have different tag distributions — different audiences, different promotion cadences. An anomaly is one location running 3–4× the compensation rate of the others.

Building tag discipline from scratch

A useful Tags report starts not in the CRM but in your shift protocol. Without that foundation, the analytics will be incomplete regardless of how capable the software is.

Step 1 — minimal tag set. Start with 5–7 tags, each with a clear application rule. A practical starter set:

Tag	When to apply
promo	Any top-up made during an active promotional campaign
compensation	Manual credit issued for a technical failure or customer complaint
corporate	Top-up from a corporate account or partner
tournament	Payment or credit tied to a tournament event
promo-code	Top-up where a promotional code was redeemed

Step 2 — write it into the shift instructions. One sentence per tag with a concrete trigger, not “roughly when there’s a promo” but “apply the promo tag on any top-up processed during an active campaign as listed on the board.”

Step 3 — weekly check. Once a week, open the Tags tab and look at the No-tag row. A downward trend means discipline is improving. An upward trend means you need a team conversation.

Tags are created and managed in Club → Transactions → Tags. You can deactivate outdated labels there — historical data for them is preserved, but admins can no longer apply them to new operations.

How Tags connects to other reports

Tag analytics works best as part of a wider picture:

• Bonus Report — Operations — detailed credit and debit history per transaction. When you spot an anomaly in Tags, go here for the underlying records.
• Shift Report — see which shift and which admin account for an unusual concentration of compensations or atypical operations.
• AOV — the average transaction value metric that tags let you calculate separately for each revenue channel.
• Bonus Balance — what happens to the customer’s account balance after a tagged transaction is processed.

---

Three weeks of consistent tagging generate enough data for a first structural conclusion: which channels and campaigns are genuinely moving revenue, and which are creating the appearance of activity without driving the numbers.