What shipped, week by week

Launching a program usually means an empty dashboard and a cold-start problem. Discovery is an agent that solves the first mile for you.

• It searches, it doesn't look things up — give it a competitor URL or a few keywords and it runs live searches across the open web and YouTube, not a stale directory. More source adapters are in progress.
• Gate, then score, then spend — every candidate is filtered for relevance and scored against what you actually sell, with the reasoning shown. Enrichment only happens on prospects that survive, so you don't pay to research the ones the agent already ruled out.
• A real contact path or nothing — the contact stage pulls published emails and DM paths, and refuses the things that waste a week: placeholder addresses, a platform's generic inbox, a homepage standing in for a contact page. The queue can filter to only the prospects you can actually reach.
• Where each one came from — every prospect links back to the article or video it was found in, with the platform shown and a detail sheet on the row.
• Outreach written for you — a drafted, personal email per prospect, signed with your own first name, editable and saved. Approve, and they flow straight into your program's invite pipeline.
• Credit-metered, and honest about it — one credit buys one search, and a run issues roughly 5–12. Growth includes 100 credits a month, Scale 300, Max 750. Monthly credits expire at the end of the month; one-time credit packs never do, and a run that fails part-way refunds the difference.

Discovery is included from the Growth plan up. Full walkthrough on the Discovery page.

Getting affixo installed used to end with a paragraph telling you to go find your AI client's MCP settings. Now the app does it.

• One-click connector install — affixo generates the right thing for the client you picked: a deep link for Cursor and VS Code, a single command for Claude Code, Codex and Gemini CLI, and the exact settings path for Claude and ChatGPT. No install path ever contains an API key — that's enforced by a test, not a convention.
• ChatGPT is supported — as an MCP client in its own right, with the Developer-mode steps spelled out.
• Readable tool results — MCP tools now render as markdown in your client, with the raw JSON still one toggle away.
• Install prompts that know your setup — the AI prompt affixo hands you is generated from your workspace: your checkout pattern, your program's real details, your keys already filled in. Paste it into your coding agent and it installs tracking correctly the first time. An agent-skills collection is offered alongside it.
• A checklist that ticks itself off — Stripe, tracking and your first event verify themselves. The dashboard keeps a live listener up until tracking is confirmed working, so "did it install?" is answered on screen instead of days later by an empty report.
• ⌘K everywhere — a command palette over every settings page, screen and action, so finding "payout terms" doesn't mean remembering which of four groups owns it.

Setup steps and the full tool list are in the MCP docs and on the AI & MCP page.

A reporting pass and a money-correctness pass, shipped together because the second is what makes the first worth reading.

• Every report tab filters, sorts and exports — a shared toolbar across affiliates, links, performance, sources and sub-IDs, with click-to-sort column headers and CSV export on each. Affiliates with earnings but no recent clicks are no longer hidden from their own report.
• Calendar presets on the dashboard — This month, Last month and year-to-date, instead of counting back rolling days.
• Chargebacks stopped counting as revenue — a lost dispute no longer inflates revenue totals, bonus thresholds or the leaderboard. Two of the affected surfaces were awarding real money.
• Clawbacks that reverse — winning a dispute now releases the sub-affiliate parent's clawback too, and sub-affiliate overrides prorate on the net basis rather than the gross.
• Retroactive config changes stopped deleting history — editing a commission rule no longer removes commissions that were already earned under the old one.
• Every hold is on the record — a commission hold now stores why it was applied, by whom (the self-referral email and IP rules name themselves), and whether it's locked against the next recompute. "Did this pay out despite a fraud flag?" is answerable from the immutable ledger.
• Payouts close on the calendar — the monthly schedule now drafts one batch per calendar month, sweeping everything that matured during it, instead of quietly behaving like net-30. Reminders fire when the batch is created rather than on a daily poll, and a batch mid-transfer can no longer be cancelled or hand-marked as paid.
• Advanced revenue reports are admin-only — the deeper revenue views now require workspace admin.

More on commissions & payouts and fraud intelligence.

The marketplace stopped being a directory you had to sign in to see, and started being a place affiliates can find from a search engine.

• A page per program, indexed — every listing now has its own URL, with a public catalog, robots.txt and sitemap.xml. Affiliates searching for programs in your category can land directly on yours.
• A public window, not the whole house — anonymous visitors and crawlers see the same thing (no cloaking): program name, category, headline, commission and payout terms. The full description and your website link unlock on a verified email. That's enforced in the database, not the UI, so the catalog can't be scraped as a brand-bypass directory.
• One passwordless login, everywhere — the same email-code sign-in works whether an affiliate arrives at the marketplace, a program's portal or an invite link. Password reset now tells the truth about what it can and can't do.
• One list, one approval mode, one door — an affiliate who joins through the marketplace lands in the same roster as one you invited by hand, under the same approval setting. Banned, blocked and private programs have their join door closed rather than failing after the fact.
• A join screen worth landing on — a split-screen layout that renders your real logo and colours wherever you've set them (portal branding starts on Growth), instead of a generic affixo form.

More on the Marketplace page.

Two GoHighLevel-native pieces are now live, aimed at anyone running affiliates from inside GHL:

• Native GoHighLevel integration — run affiliates across every snapshot, course and SaaS offer you sell, tracked through the single Stripe account your GHL business already runs on. A one-tag script (no jQuery, no dependencies) binds a visitor's referral click to their email on GHL's order form, so server-side sales are resolved even where a URL-only tracker would miss them. More on the Integrations page.
• Migrate from GHL's Affiliate Manager — connect a read-scoped Private Integration Token and affixo imports your affiliates with their referral codes, campaigns, commission structures and program history. Each dataset is individually selectable, the import is idempotent, and the token is used for the import only — never stored.
• Every link keeps working — affixo natively reads the ?am_id= parameter GHL links already use, so nobody regenerates a link.
• Start at $0 owed — historical commissions import as history, not liability, so you can run both platforms in parallel through your cookie window and switch when you're ready.

Read the full comparison on the GoHighLevel Affiliate Manager alternative page.

Three features now public, all aimed at the same goal — making a program easier to grow:

• Affiliate Marketplace — a public directory at marketplace.affixo.dev where affiliates browse and apply to programs. Listings are moderated, applicants land in your admin console for approval, and discovery is one-way: your branded portal never shows competing programs. Listing is a paid-plan feature. More on the Marketplace page.
• Embeddable affiliate dashboard — render an affiliate's links, stats and earnings inside your own app via a short-lived, single-use ticket and a chromeless iframe. To your users it reads as a native "Refer & earn" page. Details on the Portals page.
• Non-cash rewards & fulfilment — pay partners in account credits, free months, gifts or swag at any scope a cash rule can have. A reward library keeps templates reusable (copy-on-assign, so edits never mutate live campaigns), and earned rewards flow through a fulfilment queue with fulfilment.* webhooks. See Commissions & Payouts.

Connecting your AI client to affixo no longer involves API keys or config files.

• One URL — add https://go.affixo.dev/mcp as a custom connector in Claude (Settings → Connectors) or Cursor (Settings → MCP).
• One-click OAuth — click Connect, sign in with affixo, and pick the workspace and access level (read-only, or read-and-configure) on a consent screen. Admin required to authorize.
• Scoped and revocable — each connection sees only the workspace it was granted, and you can revoke it from the dashboard at any time.
• Same guardrail as always — read-and-configure only; no tool can move money, and write tools ask for approval in your client before they run.

Setup steps and the full tool list are in the MCP docs and on the AI & MCP page.

In a commission model, the costliest fraud isn't the affiliate — it's the buyer who charges back after you've already paid commission on revenue you never keep. The new Buyer Risk List makes that a shared defense:

• Confirmed fraud only — a buyer is listed when a chargeback dispute is actually lost, not merely opened.
• Matched at the moment of sale — hashed email, card fingerprint and Stripe customer ID are checked as the Stripe event lands, so a repeat offender is flagged before the commission is paid, at every program on affixo.
• Card fingerprint is the anchor — it survives a buyer using a different email address at every merchant.
• Privacy-preserving by construction — signals are stored as one-way hashes and your program only ever sees an aggregate hit count and severity, never another program's data.
• Advisory-only — a hit raises an alert for your review; it never blocks a sale.

It joins the affiliate-side Network Risk List to complete the picture: confirmed fraud at one program now protects every other, on both sides of the transaction. More on fraud intelligence.

Switching from FirstPromoter no longer means breaking links or rebuilding your program by hand.

• Integrated API import — connect your FirstPromoter API key and affixo pulls campaigns, commission rules (including per-plan, recurring and step-down schedules), affiliates, referral links and slugs, coupon mappings, referrals, full commission and payout history, sub-affiliate hierarchies and tier rules. Credentials are used for the import only — never stored.
• Every link keeps working — referral slugs import unchanged and affixo natively reads FirstPromoter's ?fpr= / ?via= parameters, so nobody regenerates a link. The snippet even reads the FirstPromoter cookie already on a visitor's device, so clicks made before you switched still credit the right affiliate.
• Preview, then apply — a true dry-run shows exactly what will come across before a single record is written, and re-running never creates duplicates.
• Guided go-live checklist — Stripe and tracking verify themselves, affiliate email stays paused until you're ready, and a built-in announcement email (with mail-merge preview) goes out only when you say so. You start at $0 owed, so you can run both platforms in parallel while you verify.

Read the full story on the FirstPromoter alternative page.

You can now connect affixo to Claude or any MCP-capable client and manage your program conversationally.

• Query affiliates, conversions, clicks and campaigns in plain language.
• Configure — spin up or tune campaigns and commission rules by prompt.
• Triage fraud — ask for risky affiliates and get self-referral, velocity and coupon-leakage signals surfaced inline.

The MCP server is read-and-configure only — it never moves money. It's included on every plan, free tier included.

Attribution no longer depends on a single cookie.

• Precedence resolution — six methods (manual code → coupon → cookie/click → UTM → subscription → email match) evaluated first-match-wins, so a sale is credited once and never twice. Five of the six need no cookie; a device fingerprint and IP match re-identify cookieless returning visitors.
• Idempotent dedup — every conversion is keyed on its Stripe event ID, so duplicate webhooks can't double-count a sale.
• Lifecycle accuracy — refunds and chargebacks claw back, churn stops recurring commissions, and upgrades reprice automatically.

Read the deep dive on affiliate tracking.