Phonexa Updates: Buyer Type Distribution, Registration Verification, Traffic Quality Tagging & TBO Bank

October brought changes across LMS Sync, Call Logic, E-Delivery, Books360, Lynx, and a few platform-wide settings. Here’s what changed.

Publisher Distribution by Buyer Types (LMS Sync & Call Logic)

Control Which Buyer Types Receive Publisher Traffic

What’s New: We’ve added Publisher Distribution by Buyer Types, so you can now set which buyer types a publisher’s traffic is allowed to reach. There are two fields:

• Allowed Buyer Types: the publisher’s traffic can only go to campaigns whose buyer type is on this list.
• Blocked Buyer Types: the publisher’s traffic never goes to campaigns whose buyer type is on this list.

If the same type is selected in both, Blocked takes priority.

Purpose: Allow/Deny Lists already control access at the campaign level, but that means opening every campaign a publisher should or shouldn’t reach. Buyer types flip that around. They’re labels you create and use as filters, so you set the rule once on the publisher, whether the goal is to send traffic only to specific buyer types or to keep certain buyers out.

How You Can Use It:

• Turn the feature on in Project Settings, under Additional Components.
• Once it’s enabled, a new Distribution by Buyer Type section appears under Publisher, in the Advanced tab.
• That’s where you pick the buyer types to allow or block for that publisher.
• Matching campaigns follow the rule from there, no need to edit each one.

Learn More:

• Buyer Types
• Publisher Configuration → Distribution by Buyer Type

Campaign Redesign (LMS Sync & Call Logic)

An Improved Campaigns Section

What’s New: We’ve redesigned the Campaigns section as part of ongoing usability and navigation improvements. That includes:

• Layout: a redesigned UI that’s cleaner and more intuitive
• Structure: better-organised tabs and new blocks
• Naming: clearer names throughout the section

How You Can Use It: Open Campaigns and you’ll see the new layout. Settings and actions are organised differently, so it’s worth a quick look around the first time.

Learn More:

• LMS Sync → Campaign Configuration
• Call Logic → Campaign Configuration

Data Lists (LMS Sync & Call Logic)

Daily Archives, Ready to Download

What’s New: Data Lists can now collect records continuously and make them available as ready-to-download daily archives.

• Records can be added through the platform, through an automated rule, or sent in directly.
• Each completed day is packaged into a downloadable file on the lists screen.
• Live Download lets you grab the data available at that moment, without waiting for the collection period to end.
• Older archives are removed automatically once they pass the retention window.
• Every record added is logged for traceability.

Purpose: For teams that regularly need large volumes of traffic data, Data Lists collect the selected records continuously and prepare a downloadable archive for each completed day. Unlike Lead Export, which limits exports to a two-month date range, or API Access, which needs an integration your team builds and maintains, there’s no new request and approval each time.

How You Can Use It: Say a data analyst needs the previous day’s post details every morning. They open the list, select the day they need, and download it, even when a single day holds close to a million records.

Learn More: Extra Fields → Data Lists

Prefetch Filtering (LMS Sync & E-Delivery)

Clicks That Come From People, Not Browsers

What’s New: Redirect links and E-Delivery tracking events are no longer registered when a browser pre-loads a link in the background instead of a person actually clicking it. Only genuine visitor clicks are recorded. This is available on demand.

💡 What does prefetch mean? Some browsers pre-load a link in the background before anyone actually clicks it, for example when a visitor simply hovers over it, so the page opens faster if they do click.

Purpose: Automatic browser activity shouldn’t show up as engagement. Filtering it out keeps click counts accurate, so payouts and conversion rates aren’t inflated.

How You Can Use It: Since it’s available on demand, your Customer Lifecycle Manager can help you set it up. Once it’s on, click reports reflect only real visitor activity, with nothing padded by background browser requests.

Call Tracking Summary (Call Logic)

What’s New: The Call Tracking Summary report is now faster to filter, easier to read, and more complete on export.

• New and improved filters for tracking pool, product, and the exact number displayed to each visitor
• Expanded visitor-level details on where traffic came from and how it behaved
• Exports that carry the complete data set, including full timestamps and expanded columns

Purpose: When you’re reviewing call sessions, you need to isolate traffic without selecting a publisher first, and the data needs to hold up once it leaves the platform, for reconciliation or fraud review.

How You Can Use It: Open the report and filter by tracking pool, product, or the exact number displayed to each visitor. Use the visitor-level details to validate traffic quality and attribution, then export the full data set, timestamps included, for reconciliation or fraud review.

Learn More: Reports and Analytics → Call Tracking Summary

Registration Verification (Platform-Wide)

Anti-Fraud Checks on Every Sign-Up Point

What’s New: Registration Verification applies anti-fraud checks to every registration point in the platform: publisher, buyer, advertiser, affiliate, and employee registrations. That includes sign-up forms and publisher registration requests that previously had no protection, as well as the API. The available checks are:

• Good Bots Check and Data Centres IP Check: identify automated and hosting-provider traffic
• Email Domain Validation: verifies the domain exists, with a configurable minimum domain age in months
• Mail Exchange (MX): validates MX records, with an optional keyword blocklist
• Restrict Dots in Email: sets a maximum number of dots allowed in an address
• Disallow “+” in Email: blocks alias-based registrations

Purpose: Admins need protection against fraudulent sign-ups. Bad actors register large volumes of publisher accounts from data centre IPs, using disposable domains and email aliases built with dots or “+” to confirm multiple accounts from one mailbox.

How You Can Use It: Go to General → Security and find the new Registration Verification block. The policy is configured once and enforced identically everywhere, the API included.

Learn More: Project Settings → Security

Payment Integration with TBO Bank (Books360)

ACH Payments, With an Approval Step Built In

What’s New: TBO Bank is now a supported payment method in Books360, enabling ACH bank-to-bank transfers for both vendor payouts and customer invoice payments. TBO Bank can be enabled separately for Vendor Payouts and Customer Payments. Every transaction is created in a pending state and needs approval before it’s processed, with approval requests sent to designated notification emails.

Purpose: Paying publishers and vendors, and collecting from buyers, through direct bank transfer instead of card processing cuts transaction fees on high-volume payouts. The approval step makes sure mass payouts and customer charges get reviewed before any funds move.

How You Can Use It: Configure it under Account → Settings → Payment Methods. Each of the two uses needs a Merchant ID, API login, and API password. Sandbox mode lets you validate the integration before you process live transactions.

Learn More: How to Set Up TBO Bank as a Payment Method

Agent Commission Settings (Lynx)

Commission Rates Set Per Relationship

What’s New: Lynx Agent commission settings now support flexible, per-relationship configuration.

• Referral percentages can be set individually per Affiliate instead of one shared value across all affiliates.
• Commissions can be configured globally or per agent, with high-priority Affiliate and Advertiser overrides for exceptions.
• A new Revenue-based commission calculation option for Affiliates bases agent earnings on the revenue generated.
• Priority is applied in this order: Overrides → Agent Settings → Global Settings.

Purpose: Agent commissions often need to be set at the individual Affiliate and Advertiser level, not as one shared referral percentage across the whole network.

How You Can Use It: Set different rates per agent, and add an override for a specific Affiliate or Advertiser when an exception comes up, without changing the agent’s overall configuration. For revenue-based deals, agent payouts can be calculated from the revenue their referred Affiliates generate.

Learn More:

• Manage Advertiser Users
• Manage Affiliate Users

Traffic Quality Scoring and Tagging (Lynx)

Label Click Quality Without Rejecting Anything

What’s New: A new Traffic Quality setting analyses click quality without rejecting traffic. When it’s on, each click is automatically labelled Good, Suspicious, High Risk, Fraud, or Unknown, based on the fraud scoring services you have active.

• In the Clicks Report, labels appear as colour-coded values, with a hover tooltip showing the details behind each rating.
• In the Performance Report, Traffic Quality is available as an optional grouping, column, and filter, along with a new optional Reject % column.

Purpose: An affiliate manager needs a way to show a publisher how much of their traffic is low quality, without blocking any clicks.

How You Can Use It: Turn on the Traffic Quality setting, then group the Performance Report by Traffic Quality. From there, an affiliate manager can share a breakdown of what share of a publisher’s clicks were flagged as high risk or fraudulent, and use it as evidence in the conversation about traffic sources.

Learn More: Offer Configuration

Questions?