Lead360Support

Rewards Analytics

Interpret server-verified spend, visits, appointments, referrals, and reward history by contact.

How this fits into Lead360Explore the white label platformConnect client commerce, services, checkout, payments, and agency delivery.
Lead360 workflow mapRewards Analytics
  1. 01

    How Lead360 helps

  2. 02

    Read the page

  3. 03

    Ask360 on this page

  4. 04

    Confirm the result

A visual sequence for completing Rewards Analytics in the intended Lead360 business context.

How Lead360 helps

Rewards Analytics summarizes earning, redemption, balance, and program activity so teams can evaluate participation and financial exposure. It is most useful when report filters and reward event definitions are compared with the underlying customer and transaction records. Review source histories before making program changes.

When to use this area

Use Rewards Analytics to monitor program health, investigate changes, and support decisions about reward rules or campaigns.

Before you begin

  • State the question and comparison period.
  • Confirm timezone, event definitions, and included program rules.
  • Know whether reversals, expiry, and pending activity are included.

Read the page

  1. Search by contact name or phone.
  2. Compare verified activity, earned value, redeemed value, and current balances for the same contact.
  3. Investigate unexpected results in source appointments, orders, visits, or referrals before correcting anything.

Ask360 on this page

Ask360 can explain each metric and help analyze values you are authorized to see or provide. It does not expose payment details, export protected contact data, or adjust rewards or balances.

Confirm the result

A completed Rewards Analytics workflow should be visible in the product area that owns the final record. Use these checks before relying on the result or moving to the next customer-facing step.

  • Compare summary totals with sampled reward histories.
  • Separate issued, redeemed, expired, reversed, and outstanding value.
  • Document data latency and filter limits with any exported result.

Troubleshooting

Totals changed after the reporting period

Late events, reversals, identity corrections, or backfilled activity can change historical summaries. Inspect the underlying event history.

Outstanding value looks too high

Review duplicate issuance, inactive customers, expiry rules, pending redemptions, and the selected date filter.

An export differs from the screen

Confirm both views use the same timezone, date boundary, program filters, event states, and export generation time.

Frequently asked questions

What should I confirm before using Rewards Analytics?

State the question and comparison period. Confirm timezone, event definitions, and included program rules. Know whether reversals, expiry, and pending activity are included. Start with a small, reviewable change whenever the workflow can affect customers, money, published content, or shared records.

How does Lead360 help with Rewards Analytics?

Rewards Analytics summarizes earning, redemption, balance, and program activity so teams can evaluate participation and financial exposure. It is most useful when report filters and reward event definitions are compared with the underlying customer and transaction records. Review source histories before making program changes.

Continue with Lead360

Use this workflow in Lead360

Put this guide into practice with a 14-day free trial of Lead360 Pro early access, or continue learning through the related collection.

Try Early AccessLearn more about Commerce and Payments