Skip to app details
Back to app library
APPNEURAL APP FAMILYMarketing & Branding

Affiliates

Give referral partnerships a clear structure

Run referral programs with tracked links, commission rules, partner payouts, and fraud checks.

01 / OVERVIEW

See where it fits in your day.

Each domain runs a program with a currency, cookie window, hold period, minimum payout, first or last click and versioned terms. Commission rules pay a percentage or a fixed amount per product, per category or on everything, with volume tiers and recurring commission for subscriptions. Partners apply at partner.<domain>/join and, once approved, get a code and a link at /r/<code> that sets a first-party cookie and redirects, with an optional coupon code. Conversions arrive through POST /api/v1/conversions or a thank-you page snippet, idempotent by order id, and refunds reverse commission; self-referrals, bursts from one address and browser-only reports are held for review. The ledger moves commission from pending to approved after the hold (by cron) to paid in payout batches with UPI or bank details, a CSV export and the UTR. Partners sign in to /portal with an emailed one-time code to see their stats, links, coupon, sales, payouts and creatives. Claude drafts program terms, outreach emails and performance summaries. affiliates.appneural.com holds every domain; partner.<domain> holds one domain's program.

A LOOK INSIDEExample layout · sample content
A workspace for referral partners
Partner programTracked linksPayout context
Learning partnersaffiliate programsEXAMPLE
Product advocatescommission rulesEXAMPLE
Business referralstracked linksEXAMPLE
02 / CAPABILITIES

Built around the work you do.

What Affiliates does for you.

01

Partner onboarding

Support partner sign-ups and a partner portal.

02

Referral tracking

Use tracked links and conversion fraud checks.

03

Commission handling

Work with commission rules and partner payouts.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Affiliates. What you can do depends on your access in the app.

01

Define the program

Review the domain and commission rules.

02

Prepare partner access

Check the partner sign-up and portal experience.

03

Review referral activity

Inspect tracked conversions and payout context.

YOUR NEXT MOVE

Make Affiliates part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE— items
P2PARTIALLY VERIFIEDPUBLISHED
Overview

Purpose and boundaries

Each domain runs a program with a currency, cookie window, hold period, minimum payout, first or last click and versioned terms. Commission rules pay a percentage or a fixed amount per product, per category or on everything, with volume tiers and recurring commission for subscriptions. Partners apply at partner.<domain>/join and, once approved, get a code and a link at /r/<code> that sets a first-party cookie and redirects, with an optional coupon code. Conversions arrive through POST /api/v1/conversions or a thank-you page snippet, idempotent by order id, and refunds reverse commission; self-referrals, bursts from one address and browser-only reports are held for review. The ledger moves commission from pending to approved after the hold (by cron) to paid in payout batches with UPI or bank details, a CSV export and the UTR. Partners sign in to /portal with an emailed one-time code to see their stats, links, coupon, sales, payouts and creatives. Claude drafts program terms, outreach emails and performance summaries. affiliates.appneural.com holds every domain; partner.<domain> holds one domain's program.

Referral and affiliate programs for a connected domain: commission rules, partner applications, tracked links, conversions with fraud checks, a ledger with payouts and a partner portal.

Taking the money belongs to Payments; coupon codes belong to Coupons; paid creator campaigns belong to Influencers.

Priority
P2
Portfolio
Marketing & Branding
Capability
Marketing & Branding
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-16T04:17:19.075Z
Semantic inventory

Every number says what it counts

—Count unavailabletrackedEntityCount · catalog-api:unavailable
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

affiliate schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

affiliates.appneural.com DEPLOYED

affiliates.appneural.com

Worker
affiliate-catalog
Health
HEALTHY
Last deployment
2026-11-08 10:24:36
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

Repository provider is not connected. Existing references remain unverified.

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

No health checks have been recorded.
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is partially verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app