Help Shape Our Future

Your insights drive our innovation. Share your ideas and help us build the features that matter most to you.

In Progress

Custom Attribution: Choose Between First-Touch and Last-Touch

Right now, all affiliate programs in Affonso use last-touch attribution by default, meaning the most recent affiliate click before a conversion receives credit. I’m exploring whether it makes sense to give program admins the option to choose between last-touch and first-touch attribution, depending on what fits their strategy best. First-touch attribution would reward the affiliate who originally referred the user, even if another affiliate re-engages them later. This can be useful for longer sales cycles or content-driven discovery. If this would be useful for your program, feel free to upvote and add any thoughts in the comments.

Silvestro 8 months ago

1

In Progress

Traffic source control to block search engine referrals

Allow program owners to exclude or ignore affiliate traffic coming from major search engines such as Google, Bing, Baidu, and Yandex. This helps reduce fraud and prevents affiliates from claiming commissions on branded search traffic or paid ads that should not be commissionable. Why this is useful Some affiliates try to game programs by running search ads or ranking for brand keywords and then claiming referrals that would have converted anyway. Being able to ignore traffic from major search engines gives program owners more control and helps ensure commissions are paid only for genuine affiliate-driven referrals. Proposed behavior When enabled, referrals where the original traffic source is a major search engine would be ignored and not attributed to affiliates. This would apply to both organic search and search ads.

Silvestro 4 months ago

Planned

Automation Workflows

Introduce a workflow automation system that allows program owners to automatically trigger actions based on events or thresholds within their affiliate program. Currently, actions such as moving affiliates between groups (e.g., when they reach a certain number of sales) must be handled manually. A workflow engine would allow these actions to happen automatically and reduce operational overhead. Example Use Case: Tiered commission structures based on performance: Affiliate starts in Group A (20% commission) After 40 sales → automatically moved to Group B (30%) After 75 sales → automatically moved to Group C (40%) Goal: Allow program owners to automate affiliate management tasks and create scalable affiliate programs without manual intervention.

Silvestro 26 days ago

Planned

Custom Roles & Permission Management

Currently Affonso has two roles: Admin and Member. Both roles have full access to the platform, with the only difference being that Members cannot manage billing. It would be valuable to introduce custom roles with configurable permissions while keeping the existing defaults. Proposed structure: Default Roles (unchanged behavior) Admin – full access including billing Member – full access except billing management Custom Roles Program owners can create additional roles (e.g. Analyst, Finance, Affiliate Manager, etc.) Permissions can be configured per role Example permissions that could be configurable: View-only access Manage affiliates (add/edit/delete) Manage referrals Manage commissions Manage payouts Manage program settings Manage integrations Manage resources/creatives Manage users/team Manage billing This would allow teams to create read-only roles or restricted operational roles while preserving the simplicity of the existing Admin/Member roles.

Silvestro about 1 month ago

Planned

Improve filtering and prioritization in Affiliate Finder

The Affiliate Finder currently surfaces a large number of opportunities (e.g., 400+), which makes manual review time-consuming. LinkedIn results can include competitor employees, founders of unrelated companies, or profiles that are unlikely to be good affiliate partners. Improvements could include: Better filtering of LinkedIn opportunities (e.g., exclude competitor employees) Clearer prioritization or scoring of the most relevant prospects Reducing the initial result set to a smaller group of high-probability affiliates The goal is to surface fewer but more relevant opportunities so users can quickly identify the 10–20 best prospects without reviewing hundreds of entries.

Paul Boudet about 1 month ago

Advanced Affiliate Event Tracking

Problem: Experienced affiliates — especially those running paid campaigns — need deeper insight into what referred users do after landing on the site. Basic click tracking or conversions aren't enough for optimization or proving ROI. Requested Feature: Enable custom event tracking for affiliate-referred traffic. Let program owners define and report events like: “Add to cart” “Sign up” “Purchase” Custom user actions (e.g. “started building a landing page”) Proposed Solutions: Event API — allow developers to send events to Affonso via a JS function (e.g. affonso.track("Purchase", {value: 49})), similar to fbq from Facebook. UI-based Event Creator — provide a UI that loads the merchant’s site in an iframe and lets them visually tag DOM elements for events (e.g. like Reddit Pixel). Affiliate Dashboard Events View — affiliates can then see which events their users triggered to optimize their campaigns. Why It Matters: Helps pro affiliates justify spend on paid channels Increases trust and transparency in partner relationships Unlocks better analytics for both sides

Landy 3 months ago

Add proper test mode / sandbox for integrations

Currently, there is no dedicated test mode or sandbox environment to fully test affiliate tracking setups (e.g. with Stripe, Polar or Paddle). The only reliable way to test end-to-end is by using a 100% discount code in live mode. Provide a dedicated test mode or sandbox environment where users can: Simulate referrals, checkouts, and conversions Validate tracking (e.g. metadata, attribution) Test integrations without requiring live payment setups Current workaround: Use 100% discount codes in live mode Or manually inspect metadata in dev logs Notes / Use cases: Faster onboarding and debugging Safer testing without touching live environments Especially useful for new users setting up integrations for the first time

Silvestro 24 days ago