Flow Conditions

Advanced targeting rules for commission flows

Do you need conditions?

Most programs don't need conditions at all. If you want all affiliates to earn a flat 20% commission, just create a simple flow with no conditions — done.

Use conditions only when you want commissions to change automatically based on performance. Common reasons:

Reward your top affiliates with a higher rate once they hit a revenue milestone
Give a bonus commission on a customer's first purchase, then a lower rate on renewals
Apply different rates for customers in specific countries

If none of these apply to you, skip this page and use a simple flow instead.

What are Flow Conditions?

Understanding conditional logic for commission flows

Flow Conditions are advanced targeting rules that allow you to automatically apply different commission rates based on specific criteria. They work like filters that determine which affiliates qualify for a particular flow.

How Conditions Work:

Each flow can have multiple conditions
All conditions must be met (AND logic)
Conditions are evaluated at the time of each conversion
Inactive conditions are ignored during evaluation

When to Use Conditions

Use conditions to create sophisticated commission structures like "20% commission only for affiliates with annual sales over $50,000" or "Bonus flow for affiliates who referred 100+ customers."

Condition Types

All available condition types organized by category

Partner Conditions

Affiliate Performance

Based on the affiliate's historical performance and metrics

PARTNER_TOTAL_REVENUELifetime revenue generated

Example: Total revenue ≥ $50,000 (target high-performing affiliates)

PARTNER_CUSTOMER_COUNTTotal customers referred

Example: Customer count ≥ 100 (reward prolific referrers)

PARTNER_TRANSACTION_COUNTTotal transactions processed

Example: Transaction count ≥ 500 (volume-based qualification)

PARTNER_AVERAGE_TRANSACTION_VALUEAverage sale amount

Example: Average transaction ≥ $200 (target high-ticket affiliates)

PARTNER_ACTIVE_CUSTOMERSCurrently active customers

Example: Active customers ≥ 50 (reward customer retention)

PARTNER_DAYS_SINCE_FIRST_SALEPartner tenure

Example: Days since first sale ≥ 365 (loyalty bonus for 1+ year affiliates)

PARTNER_MONTHLY_REVENUERevenue in current month

Example: Monthly revenue ≥ $5,000 (performance-based tiers)

Customer Conditions

Individual Customer Metrics

Based on the specific customer's attributes and behavior

CUSTOMER_TOTAL_PAIDLifetime value of customer

Example: Customer total paid ≥ $1,000 (bonus for high-value customers)

CUSTOMER_TRANSACTION_COUNTNumber of purchases

Example: Customer transactions ≥ 5 (repeat customer bonus)

CUSTOMER_IS_ACTIVEActive subscription status

Example: Customer is active = true (only pay for active subscribers)

CUSTOMER_COUNTRYGeographic location

Example: Customer country = "US" (US-only commission flow)

CUSTOMER_DAYS_ACTIVESubscription duration

Example: Days active ≥ 30 (bonus after 30-day trial period)

Transaction Conditions

Specific Sale Attributes

Based on the specific transaction being processed

TRANSACTION_AMOUNTSale value

Example: Transaction amount ≥ $500 (higher commission for big sales)

TRANSACTION_PRODUCT_IDSpecific product sold

Example: Product ID = "premium-plan" (premium product bonus)

TRANSACTION_BILLING_TYPEPayment schedule

Example: Billing type = "ANNUAL" (bonus for annual subscriptions)

TRANSACTION_IS_FIRST_PAYMENTNew customer indicator

Example: Is first payment = true (new customer acquisition bonus)

Condition Operators

How to compare values in your conditions

Operators define how the condition value is compared. Choose the right operator based on the type of comparison you need.

EQUALS

Exact match

Example: Country = "US"

NOT_EQUALS

Exclude specific value

Example: Country ≠ "US"

GREATER_THAN

Value must be larger

Example: Total revenue > 50000

GREATER_THAN_OR_EQUAL

Value must be at least

Example: Customer count ≥ 100

LESS_THAN

Value must be smaller

Example: Days active < 30

LESS_THAN_OR_EQUAL

Value must be at most

Example: Transaction amount ≤ 100

BETWEEN

Value in range (inclusive)

Example: Total revenue between 10000 and 50000

IN

Match any in list

Example: Product ID in ["basic", "pro", "enterprise"]

NOT_IN

Exclude all in list

Example: Country not in ["CA", "MX"]

Adding Conditions to a Flow

Step-by-step guide to creating conditional flows

Open Flow Editor

When creating or editing a flow, scroll down to the "Advanced Conditions" section.

Add Condition

Click "Add Condition" button. A new condition row appears.

Select Condition Type

Choose from Partner, Customer, or Transaction conditions based on what you want to target.

Choose Operator

Select how you want to compare the value (equals, greater than, between, etc.).

Enter Value(s)

Enter the threshold or target value. For BETWEEN operator, you'll enter two values (min and max).

Add Description (Optional)

Add notes to help remember why this condition exists. Useful for team collaboration.

Add More Conditions (Optional)

Partner Average Transaction Value ≥ $500

AND

Condition 2

Partner Active Customers ≥ 25

AND

Condition 3

Partner Days Since First Sale ≥ 180

Result: 22% commission for established affiliates (6+ months) with $500+ average order value and 25+ active customers

How Multiple Conditions Work (AND Logic)

Understanding condition evaluation

When you add multiple conditions to a flow, ALL conditions must be true for the flow to apply. This is called AND logic.

Example Flow with 3 Conditions:

Partner Total Revenue ≥ $10,000
Partner Customer Count ≥ 50
Partner Days Since First Sale ≥ 90

Important: All Must Pass

An affiliate will only qualify for this flow if they have $10K+ revenue AND 50+ customers AND been active for 90+ days. If even one condition fails, the flow won't apply.

Future Enhancement: OR Logic

Currently, only AND logic is supported. In the future, you'll be able to create OR conditions (e.g., "revenue ≥ $10K OR customer count ≥ 100") and complex nested logic.

Best Practices

Tips for creating effective conditions

Start Simple, Add Complexity Gradually

Begin with 1-2 conditions and test thoroughly before adding more. Complex condition sets can exclude more affiliates than you expect.

Use Descriptions Liberally

Add descriptions to every condition explaining the business reasoning. Your future self (and team members) will thank you when reviewing flows months later.

Monitor Affiliate Qualification Rates

After creating conditional flows, check how many affiliates qualify. If too few match, your thresholds might be too strict.

Create Fallback Flows

Always have a default flow with no conditions for affiliates who don't match any conditional flows. This ensures everyone gets paid something.

Test with Realistic Data

Before activating a flow, verify it works as expected. Check which affiliates would qualify based on current data.

Deactivate vs Delete

Instead of deleting conditions you might need later, toggle them inactive. This preserves historical configuration for future reference.

Be Aware of Data Freshness

Partner metrics (total revenue, customer count, etc.) are calculated based on database records. There may be slight delays during high-volume periods.

Communicate Changes to Affiliates

When creating performance-based flows or changing conditions, let your affiliates know. Transparency builds trust and motivates better performance.

Important Notes

Condition Evaluation Timing

Conditions are evaluated when assigning affiliates to flows, not on every transaction. Changes to conditions may require re-assigning affiliates to see effects.

Inactive Conditions

Inactive conditions are completely ignored during evaluation. This is useful for temporarily testing different condition sets without deleting existing rules.

Numeric Value Format

For numeric conditions (revenue, amounts, counts), always use decimal numbers without currency symbols or commas. Example: 50000 not "$50,000" or "50,000".

String Value Matching

String comparisons (like product IDs, countries) are case-sensitive. "US" is different from "us". Use exact values as they appear in your system.

Boolean Values

For boolean conditions (Is Active, Is First Payment), use "true" or "false" (lowercase) as values.

Next Steps

Now that you understand conditions, here are some suggested next steps:

Create Your First Conditional Flow

Go to Flows page and try adding conditions to a flow

Learn About Flow Modes

Understand Simple vs Advanced flows and when to use each

Review Partner Performance

Check metrics to help decide condition thresholds

Need Help?

If you have questions about conditions or need assistance setting up complex scenarios, contact support or check the community forums for examples from other users.