Start a conversation

Influitive Referral Points Mismatch and Negative Balance Caused by Referrals Reverting to “Submitted”

Contents

Overview

An advocate may be unable to redeem rewards if multiple referrals revert to "Submitted", triggering automatic point reversals (for example, -50) for the "Referral Verified" milestone and resulting in a negative points balance.

In Influitive, the hub’s display such as "50 points awarded 14 times" can be higher than the number of unique referrals because the same referral can reach (and re-reach) the same milestone multiple times when it is moved backward (Verified → Submitted) and forward again (Submitted → Verified).

Solution

Symptoms

  • Referral entries unexpectedly revert to "Submitted".
  • Points are deducted (e.g., -50 per referral) and the advocate’s balance becomes negative.
  • The hub appears to show repeated awards such as "50 points awarded 14 times", creating confusion about how many referrals exist.
  • The advocate cannot redeem rewards due to the negative points balance.

How Influitive referral points behave (key concept)

Influitive awards points based on referral campaign milestones. A single referral can reach the same milestone multiple times if it is moved backward and forward between statuses. Typical sequence:

  • Submitted → Referral Verified results in +50 (milestone award).
  • Referral Verified → Submitted results in -50 (milestone reversal).
  • Moving forward again to Verified results in +50 again.

Because of this, “points awarded N times” can be larger than the number of unique referral records.

Investigation workflow

1) Confirm the number of unique referral records in Influitive

Use the Referrals API to list referrals filtered by the advocate identifier (for example, contact email):

  • GET /referrals?contact_email=<advocate_email>

Record how many unique referral records exist, and capture their IDs and current milestone/status.

2) Explain why points were awarded multiple times

For each referral, review milestone history (for example, a field such as milestones_reached) to determine how many times "Referral Verified" was reached and how many times it was reversed.

3) Identify when and why deductions occurred

Use the Events API to locate milestone events showing negative points for the referral milestone:

  • Look for events like referral_milestone_reached where points = -50.
  • Correlate timestamps to detect batch changes (multiple referrals updated around the same time).

Observed platform behavior (example findings)

  • Platform data can show fewer unique referral records (for example, 9 unique referral records) than the hub’s “awarded” count (for example, 14).
  • The “50 points awarded 14 times” value reflects how many times the referral reached the "Referral Verified" milestone, not the number of distinct referrals.
  • A repeating milestone sequence may appear where referrals move back and forth: Submitted → Referral Verified (+50) and Referral Verified → Submitted (-50).
  • A batch of updates on <date> may move multiple referrals back to "Submitted", producing referral_milestone_reached events with points = -50.
  • If some referrals are moved forward again but others remain in "Submitted" (for example, 4 referrals), the advocate remains short by 200 points (4 × 50) compared to if those referrals were Verified.

Root cause

This behavior is expected when referral records are moved backward from "Referral Verified" to "Submitted". Influitive automatically reverses previously-awarded milestone points, which can temporarily or permanently reduce an advocate’s balance if the referrals are not advanced back to the Verified milestone.

Resolution (restore points by re-verifying the correct referrals)

If specific referrals should be in "Referral Verified", advance them back to that milestone.

Option A: Fix in the Referrals admin UI

  1. Go to your hub’s Referrals administration area.
  2. Locate the affected referrals (match by prospect identifier such as the referred person’s email).
  3. For each referral that should be verified, move/advance it to the "Referral Verified" milestone.
  4. Save/confirm changes.

Option B: Fix via API

  1. Identify each affected referral’s ID (from the list-referrals response).
  2. Advance the referral to the appropriate milestone using the campaign’s milestone API code:
PUT /referrals/<referral_id>/milestones/<milestone_api_code>

Important: <milestone_api_code> must match the milestone’s configured API code in your referral campaign settings.

Validation / confirmation steps

  1. Re-check the affected referrals and confirm their current milestone is "Referral Verified".
  2. Confirm the advocate’s points balance increased by 50 × (number of referrals re-verified).
  3. Confirm reward redemption is available again (no negative balance blocking redemption).
  4. Reconcile with Salesforce by comparing at the prospect (referred person) level against the Influitive referral list, since Salesforce may count “verified” and duplicates differently.

Frequently Asked Questions

1. How can “50 points awarded 14 times” occur if there aren’t 14 referrals?
The count reflects how many times the "Referral Verified" milestone was reached, not how many unique referral records exist. If a referral moves backward (Verified → Submitted) and then forward again (Submitted → Verified), the +50 milestone award can happen multiple times for the same referral, with matching -50 reversals when it moves back.
2. Why did the advocate’s balance go negative?
When a referral is moved from "Referral Verified" back to "Submitted", Influitive automatically reverses the previously-awarded milestone points (for example, -50). If several referrals are reverted (including via a batch update) and not moved forward again, the net result can be a negative balance.
3. How do I identify which referrals still need to be re-verified?
List referrals for the advocate via the Referrals API (or in the admin UI), then filter for those whose current status/milestone is "Submitted". Compare prospect identifiers (such as the referred person’s email) to your expected verified list.
4. Salesforce shows a different number of “verified referrals” than Influitive. Which is correct?
They can both be “correct” under different definitions. Salesforce may count “verified” differently and/or handle duplicates differently. The most reliable reconciliation method is to compare the referred-person (prospect) identifiers one-by-one against the unique Influitive referral records.
5. I advanced a referral back to “Referral Verified” but points didn’t change. What should I check?
Confirm the referral actually transitioned to the correct milestone, and confirm you used the correct milestone API code (if using the API). Also review the referral’s milestone history and events to ensure the +50 award event was generated after the transition.
Choose files or drag and drop files
Was this article helpful?
Yes
No
  1. Priyanka Bhotika

  2. Posted

Comments