Phonexa Updates: Improved Setup, Better Reporting, Smarter Rules, & Stronger Traffic Controls

A few things have changed across Phonexa lately. If you work with LMS Sync, Call Logic, iClear, or Lynx day-to-day, some of these have already shown up in your workflow. Here’s a rundown of what’s new.

Product Builder (LMS Sync & Call Logic)

A Redesigned Product Builder Experience

What’s New: The Product Builder has been reorganised. Product Configuration and Extra Fields used to live separately — now they don’t. Field creation got some structural cleanup too, and the interface is less of a maze than it used to be.

Purpose: The old layout had you going back and forth for no good reason. This just fixes that.

How Teams Use It: Product field management now happens entirely within the Product Configuration tab. If you’ve been working around the old layout, this one should feel noticeably more straightforward.

Learn More:

• Product Setup → Product Builder
• Product Setup → Product Configuration

Referral Report (LMS Sync & Call Logic)

Improved Visibility & Filtering for Referral Data

What’s New: Admins and publishers now land on different versions of the Referral Report. Filtering got cleaned up, and finding referral relationships or commission data no longer takes three more clicks than it should.

Purpose: One report trying to serve everyone equally usually ends up serving no one well. This one now adjusts to who’s looking at it.

How Teams Use It: Pull up the Referral Report when you need to get into the details of your Publisher Referral Program — who referred who, when they registered, what commissions look like. Your view will reflect your role automatically.

Learn More:

Publisher Report → Referral Report

Custom Report Columns (LMS Sync & Call Logic)

Role-Based Visibility for Custom Report Columns

What’s New: Custom columns in report templates now support role-based visibility. A few other improvements came along with it:

• Placeholders and available fields load automatically when you open the column editor — no extra steps
• Fields filter based on the roles you select, so you’re only seeing what’s relevant
• If someone doesn’t have access to a field, that column simply won’t show up for them

Purpose: It keeps report templates cleaner and makes sure people aren’t looking at data they don’t need — or worse, data they shouldn’t have access to.

How Teams Use It: When building or editing a custom column inside a report template, admins can assign access by role — Global Admin, LMS Admin, Support, Accounting, Publisher, and so on. The system takes it from there, filtering available placeholders and enforcing visibility rules automatically.

Learn More:

Reports → Custom Columns

Rule Conditions (iClear)

New Date-Based Conditions for Lead Processing

What’s New: iClear’s Advanced Rules now support a Date/Time Difference condition. In plain terms, you can now write rules that look at the gap between two dates and do something based on that. You pick a date field from the lead, a reference date to compare it against, and set your threshold in days, hours, or minutes.

Purpose: A lot of lead quality issues are actually timing issues. This gives you a way to act on that automatically instead of catching it manually after the fact.

How Teams Use It: A good example is moving service leads. If someone submits a lead with a move date that’s only two days out, that’s probably not workable. You can now set a rule that rejects or reroutes those automatically, based on whatever cutoff makes sense for your business.

Find it at: Product → Lead Processing Rules → Advanced Rules → Conditions.

Learn More:

iClear → Advanced Rules → Conditions

Rule Caps (iClear)

New Action-Trigger Caps

What’s New: There’s now a second type of cap in iClear. The original caps counted every time a rule was evaluated. The new action-trigger caps only count when the rule’s conditions are actually met and the action fires. The two work independently — having one doesn’t affect the other.

Purpose: If a bunch of leads are hitting a rule but failing the conditions, those shouldn’t count against your cap. Now they don’t.

How Teams Use It: Inside the Rule Caps section, you’ll see Action Daily Caps and Action Monthly Caps alongside what was already there. Set them the same way you would other caps — the difference is just what they’re counting.

Learn More:

iClear → Advanced Rules Configuration

Offer Targeting (Lynx)

iClear IP Scoring for Fraudulent Click Detection

What’s New: Lynx now connects with iClear’s IP Scoring, so you can run click traffic through a quality check before it affects anything meaningful. It looks at things like whether an IP belongs to a data centre, whether it’s coming through a proxy or VPN, TOR usage, fraud score, and country.

Purpose: Bad click traffic is a real problem in affiliate marketing and it’s not always obvious where it’s coming from. This gives you actual signals to work with instead of guessing.

How Teams Use It: Enable iClear IP Scoring inside Offer Targeting or Affiliate Rules when building out a Lynx offer. Score data sticks to click records, so over time you build up a clearer picture of where your traffic is actually coming from — and can use that to tighten targeting, rethink payouts, or adjust revenue group settings.

Learn More:

Lynx → Offer Configuration → Targeting

Lynx → Affiliates → Rules

Final Thoughts

At the end of the day, most of these changes solve problems that probably felt like just “the way things work.” Turns out they didn’t have to. If you’re a Phonexa client, it’s worth a quick chat with your Account Manager to see which of these fit into what you’re already doing.