Articles on: API

Ratio Comparison Node

The Ratio Comparison node divides one number about a post's author by another, and compares the result against a value you set. Use it for things a single threshold can't express: "at least twice as many followers as accounts followed", rather than "at least 500 followers".


You'll find it in the editor's Rules menu (the filter icon), on the Basic tab under Attribute.


Fields


The node reads left to right, like a sentence:


  1. The attribute on top of the division.
  2. ÷ the attribute underneath.
  3. An operator: at least, at most, above or below.
  4. The value to compare the ratio against. It can be a decimal, such as 0.5 or 2.5.


Only numeric attributes can be divided, so the attribute lists are shorter than in Attribute Comparison:


  • Account Age (days)
  • User Followers
  • User Following
  • User Post Count


A new node starts as User Followers ÷ User Following at least 2.


Things to know


  • Nothing matches when the bottom value is zero. An account that follows nobody has a following count of 0, so there's no meaningful ratio. The post is excluded, not treated as infinite.
  • There's no "is exactly". A ratio is a decimal, so an exact match would almost never happen.


Examples


  • Skip follow-for-follow accounts: User Followers ÷ User Following at least 0.5.
  • Established posters: User Post Count ÷ Account Age (days) at least 1, for accounts that average at least one post a day.
  • Accounts people seek out: User Followers ÷ User Following at least 10.


Combine it with your other rules in a Logic node, the same as any other condition. Use Debugging a Post to check how a particular account's post fares.

Updated on: 18/10/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!