Take your app to the next level with Affise MMP (Mobile Measurement Partner)
Join Now ⚡

01 · Affiliate Managers

Stop Exporting CSVs: How Affiliate Managers Run Their Day by Just Asking Affise

Stop exporting CSVs. Start asking questions.

Every affiliate manager knows the Monday morning routine. You open Affise, pull last week's numbers, export them to a spreadsheet, compare them to the week before, and figure out which partners are up, which are down, and who's gone silent. Then you do it all over again to check for trafficback issues and make sure payouts are ready. By the time you finally have the full picture, the whole morning is gone.

The Affise MCP changes that. Instead of clicking through dashboards and exporting data, you ask a question in plain English and get the answer back in seconds. It connects your AI assistant (Claude, Cursor, Continue.dev) directly to Affise, so the assistant can query your live Affise data on your behalf.

This article shows you what that actually looks like, with real examples of the tasks you handle every day as an affiliate manager.


Meet the Affise MCP

The Affise MCP is a bridge between Affise and AI tools that support the Model Context Protocol. You type a question in plain English. The AI figures out which Affise data to pull, fetches it, and returns a clear answer. No API calls, no exports, no pivot tables.

It works with Claude (claude.ai), Cursor, and Continue.dev. The setup takes about two minutes via OAuth. Once connected, your AI assistant can see your live Affise data for the duration of the session.


What You Can Do

Morning Portfolio Scan

Instead of opening Affise, exporting stats, and loading them into a spreadsheet, you ask:

"Top 20 partners by revenue last week vs the week before."
"Top 10 partners by clicks last month."
Affiseaffise_stats</>
Affise Stats
top partners · this week vs last
affiliate.loginthis_weeklast_weekdeltaconversions
NorthPeak Media913.51640.20+42.7%31240
BlueOrbit Ads402.33511.90-21.4%8110
Halcyon Media328.00190.40+72.3%1800
Skylark Digital305.55402.10-24.0%1402
Vertex Reach220.7196.00+129.9%990
Amberline Ads154.60240.30-35.7%1600
PixelForge98.9188.10+12.3%60
Solace Media88.200.00new800
8 of 42 partners
The Monday portfolio scan as it renders — week-over-week revenue per partner with the delta, sortable by any column. Anonymized demo data.

The AI pulls stats for both periods, ranks partners, and shows the delta. You see immediately who grew, who dropped, and who stopped sending traffic. A scan that used to take 30 minutes of export-and-eyeball work takes a few seconds.


The 360° Partner Deep-Dive

The portfolio scan tells you who to look at. The next question is always why, and answering it used to mean re-running the same export five times with a different grouping each time: by offer, then by country, then by device, then by day, then by sub ID. With the MCP, you just ask for the whole picture, one angle after another, in the same conversation:

"Full performance for partner 3554 last 30 days: clicks, conversions, revenue, and CR."
"Now break that partner down by offer, then by country, then by device and OS."
"Show partner 3554's daily trend for the last 30 days."
"Conversions by goal for partner 3554 last month, and the top sub2 and sub5 values."

Each answer slices the same partner along a different dimension: offer, geo, device, OS, browser, goal, sub ID, and time — so you build a complete profile without leaving the chat. Affise exposes all of these as stat dimensions, and the AI picks the right one for each question.

When you have enough angles, let the assistant aggregate them into a single read:

"/analyze_stats on partner 3554's last 30 days across all those breakdowns."
Affiseaffise_stats_raw · /analyze_stats</>
Partner Profile
partner 3554 · last 30 days · 360° breakdown
Clicks per day
040k80k120k160k8.0611.0614.0617.0620.0623.0626.0629.062.075.078.06: 10k9.06: 13k10.06: 22k11.06: 19k12.06: 27k13.06: 31k14.06: 49k15.06: 41k16.06: 63k17.06: 89k18.06: 110k19.06: 101k20.06: 84k21.06: 82k22.06: 91k23.06: 106k24.06: 101k25.06: 113k26.06: 131k27.06: 143k28.06: 121k29.06: 112k30.06: 119k1.07: 129k2.07: 131k3.07: 121k4.07: 99k5.07: 100k6.07: 96k7.07: 115k
Confirmed vs declined conversions per day
ConfirmedDeclined
02k4k6k8k8.0611.0614.0617.0620.0623.0626.0629.062.075.078.06: confirmed 1.6k9.06: confirmed 1.7k10.06: confirmed 1.8k11.06: confirmed 1.5k12.06: confirmed 1.2k13.06: confirmed 1.6k14.06: confirmed 2.1k15.06: confirmed 1.9k16.06: confirmed 1.7k17.06: confirmed 1.9k18.06: confirmed 2k19.06: confirmed 2.1k20.06: confirmed 2.4k21.06: confirmed 2.6k22.06: confirmed 2.8k23.06: confirmed 3k24.06: confirmed 3k25.06: confirmed 3.1k26.06: confirmed 3k27.06: confirmed 3.1k28.06: confirmed 4.2k29.06: confirmed 4.4k30.06: confirmed 5.2k1.07: confirmed 4.9k2.07: confirmed 5k3.07: confirmed 5.1k4.07: confirmed 5k5.07: confirmed 4.8k6.07: confirmed 4.5k7.07: confirmed 4.2k8.06: declined 3.4k9.06: declined 3.2k10.06: declined 2.6k11.06: declined 1.9k12.06: declined 1.3k13.06: declined 1.2k14.06: declined 1.5k15.06: declined 2.1k16.06: declined 2k17.06: declined 1.7k18.06: declined 1.6k19.06: declined 1.5k20.06: declined 1.7k21.06: declined 2k22.06: declined 2.1k23.06: declined 1.9k24.06: declined 1.6k25.06: declined 1.5k26.06: declined 2k27.06: declined 2.1k28.06: declined 4.5k29.06: declined 6.2k30.06: declined 6.5k1.07: declined 6.2k2.07: declined 7k3.07: declined 7.2k4.07: declined 6k5.07: declined 5.3k6.07: declined 6k7.07: declined 5.2k
Confirmed revenue, $ per day
$0$50$100$150$200$250$300$3508.0611.0614.0617.0620.0623.0626.0629.062.075.078.06: $609.06: $4610.06: $9011.06: $8012.06: $6313.06: $4714.06: $15715.06: $17716.06: $9817.06: $8418.06: $7719.06: $8020.06: $14021.06: $15822.06: $19023.06: $16024.06: $16325.06: $14026.06: $10727.06: $9828.06: $12529.06: $12830.06: $2501.07: $1772.07: $2423.07: $3284.07: $2485.07: $2656.07: $3107.07: $201
Top offers · by confirmed earning
offer.idoffer.titlestatusclicksconversionsconfirmed.earningcr
48021StreamVibe_IN_NR_CPIactive3000891105591010.2011.90
48010WalletPro_IN_AOS_CPIactive22182929957919.9512.11
48033CreditGo_CPA_IDactive1200421948825.201.62
47915TripEasy_IN_AOS_CPIdisabled2065312289630.310.87
47788FreshCart_CPA_IDactive99146795323.6038.39
48044GameLoop_SOI_BRactive335001210289.003.61
By country · top 8
countrytraffic.rawconversionsconfirmed.countcr.confirmed
IN2116832177485808163.82
ID129969874357464.42
CL400121190719070.48
US166522120.72
SG139342920.86
AE110341513.64
NP1381753.62
GB33839.09
By device · top 8
osdevicetraffic.rawconversionsconfirmed.countcr.confirmed
AndroidOPPO90674259442309733.42
AndroidRealme54814940077200283.65
AndroidXiaomi2832912305395553.37
AndroidInfinix1352262117888726.56
AndroidTecno1094241743968506.26
AndroidVivo211223709633861.60
AndroidiTel32420488619836.12
AndroidSamsung176423455217631.00
Analysis summary
  • India drives ~91% of confirmed conversions (80,816 of ~88,600); Indonesia is a distant second.
  • OPPO and Realme together account for ~57% of confirmed conversions — the rest is a long tail of budget Android brands.
  • StreamVibe_IN_NR_CPI carries the click volume; WalletPro_IN_AOS_CPI brings the most confirmed revenue.
  • Declined conversions climb sharply after Jun 28 (peaking ~7k/day) while confirmed plateaus near 5k — worth a quality check before payout.
daily trend + 3 breakdowns · 1 partner
The 360° partner deep-dive as it renders in a UI-capable client — daily trend charts plus offer, geo, and device breakdowns and an analysis summary, all from one conversation. Partner and offer names are anonymized; the daily series is illustrative.

The analysis pulls the threads together: which offers carry the partner's volume, which geos convert and which leak, whether performance is trending up or cooling off, and which sub IDs (campaigns, creatives) actually drive quality. For the full quality picture you can pull the partner's other facets into the same conversation too:

"For partner 3554, also show trafficback reasons, retention rate, and time-to-action last 30 days."

By the time you finish, you have a 360° view of one partner: volume, quality, geo mix, device mix, and trend aggregated from every dimension Affise tracks, assembled in a couple of minutes instead of a morning of exports.


Conversion Checks Before Payouts Go Out

When payout day arrives, you can pull raw conversion records to see exactly what cleared and what did not:

"Approved conversions from yesterday for partner 193 in the US."
"Last 100 conversions for partner 3554 with payouts and statuses."

The affise_conversions_raw tool returns per-event data: status, payout, affiliate, geo, and device. This means you can reconcile what you track against what the partner expects before invoices go out, without switching tools or writing a single query.


Tracking Links on Demand

When a new partner asks for a tracking link, or when you are setting up a new campaign, you no longer need to navigate through the Affise interface to build the URL:

"Generate a tracking link for offer 95119 and affiliate 3554 with sub1: campaign_x and sub2: creative_y."
Affiseaffise_offer_tracking_link</>
Affise Tracking Link
Tracking link generated successfully
offer × affiliate × sub1, sub2
The tracking-link widget as it renders in a UI-capable client — the offer, affiliate, and sub-ID parameters shown as chips, with the finished URL ready to copy. The tracking domain is anonymized for this demo.

The AI builds the link with the correct offer, affiliate, and sub ID parameters and returns it ready to copy. If the partner or offer details are not in your head, you can look them up first:

"Get partner 3554 detail."

The AI fetches the partner record, and you confirm you have the right person before generating the link.


Trafficback: Who Is Sending Junk and Why

Trafficback is one of the harder things to investigate in Affise because the data lives across multiple dimensions. You can ask:

"Show trafficback for the last 7 days, broken down by reason."
Affiseaffise_trafficback</>
Trafficback
by reason · last 7 days · 11,501,422 total
reasontypetrafficbacksharedistribution
overcap cap 11,170,878 97.13%
mistargeting-country targeting 203,072 1.77%
mistargeting-os targeting 49,181 0.43%
mistargeting-region targeting 38,434 0.33%
inactive-offer offer 28,505 0.25%
non-unique-click click 5,820 0.05%
mistargeting-city targeting 3,198 0.03%
disabled-affiliate affiliate 1,996 0.02%
mistargeting-ip targeting 296 <0.01%
invalid-offer offer 38 <0.01%
invalid-affiliate affiliate 2 <0.01%
mistargeting targeting 1 <0.01%
mistargeting-device targeting 1 <0.01%
Analysis summary
  • ~97% of all trafficback is overcap — clicks hitting offers that already reached their cap. Raising caps or rebalancing volume recovers almost all of it.
  • The next largest bucket is mistargeting-country (1.8%), then OS and region — a geo/targeting-rule problem, not a partner-quality one.
  • Offer, affiliate, and click reasons are negligible (<0.3% combined) — nothing to chase there this week.
13 reasons · 1 slice
The trafficback breakdown as it renders in a UI-capable client — wasted clicks grouped by reason, with each reason's share of the total. Follow up with /analyze_trafficback for the write-up. Real reason data; you can slice the same query further by geo or partner.

The AI returns a breakdown by reason with each reason's share of the wasted traffic, plus an analysis summary. From there you can slice the same query further by geo, offer, or partner to see who and where the waste concentrates. You can follow up in the same chat:

"/analyze_trafficback on the last result."

That analysis highlights which partners to investigate further, which reasons suggest technical issues versus policy violations, and where to focus your cleanup effort.


Sub ID Attribution and Retention

When a partner asks which of their campaigns are actually converting, or you want to understand which creatives are bringing quality traffic, sub ID breakdowns answer the question directly:

"Show retention rate for last 30 days by offer."
"Break down conversions last month by sub2 for partner 3554."
Affiseaffise_stats_raw</>
Affise Stats
by sub2 · partner 3554 · last 30 days
sub2clicksconversionsconfirmed.countconfirmed.earningcr
fb_promo_win8421021401980812.402.35
tt_ugc_v35133016101502640.102.93
push_am_2128900940610205.500.47
native_lot922140705668288.203.02
ig_story_a40120512470190.001.17
search_brand6180430415176.306.72
pop_mix9654038812041.000.12
(unknown)18300966018.500.33
Analysis summary
  • search_brand and native_lot9 convert best (6.72% and 3.02% CR) — low volume, high quality. Ask the partner to scale these.
  • push_am_2 and pop_mix are volume without quality (0.47% and 0.12% CR) — most of the clicks, few confirmed. Candidates to cap or cut.
  • ~2% of confirmed conversions carry no sub2 label ((unknown)) — worth fixing the tracking macro so attribution is not lost.
8 of 8 sub2 values · 1 partner
A sub2 breakdown for one partner — which campaigns/creatives actually convert, sortable by any column. sub2 values are anonymized illustrative tracking tokens.

You can also look at time-to-action patterns to understand conversion quality across different traffic sources. The AI handles the dimensional breakdowns and surfaces which sub IDs are performing, so you can have an informed conversation with the partner about where to scale and where to cut.


Results You Can See, Not Just Read

In clients that support MCP UI apps, the answers don't arrive as a wall of text; instead, they render as interactive components right inside the chat. A portfolio scan or a partner deep-dive comes back as a sortable, paginated stats table you can eyeball in a second. A generated tracking link renders as a copy-ready card. An offer lookup shows up as scannable offer cards. In clients without UI support, the exact same data comes back as clean text, so you lose nothing either way.

Here is the same "top partners" answer as it actually renders. Click a column to sort, type to filter:

Affiseaffise_stats_raw</>
Affise Stats
page 1 · 20/page
affiliate.idaffiliate.logintraffic.rawtotal.earningtotal.countconfirmed.countconfirmed.earningdeclined.countcr
2195NorthPeak Media824544913.5083813631240812.4412104.62
2575BlueOrbit Ads47686402.325102398110380.106402.15
160Halcyon Media98430328.0021101800300.251402.14
3897Skylark Digital189576305.5516251402291.00880.86
3992Vertex Reach4665220.71251128990210.504424.18
2951Amberline Ads640200154.6019801600148.001900.31
2842PixelForge34398.912716092.00520.70
3311Solace Media1205088.2094080082.00607.80
2210Onyx Partners3562072.901980160068.001905.55
3148Quanta Media3513610061.102820240058.002100.008
2134Driftwood Media048.16736530045.00300.00
4012Lumen Partners9644.375373041.00338.54
2668Kestrel Ads512033.1021017530.00184.10
3402Terra Ads154027.3013011025.00128.44
4005Cobalt Digital139136022.0024920020.50220.017
2876Meridian Ads16918.6395121017.0017.10
3970Nimbus Performance24314.44806613.10832.92
4120Zephyr Reach76012.75443811.5035.79
3855Cedar Performance2209.1528248.40212.72
2779Ironwood Digital349325.047236104.80552.07
20 of 87 rows · 9 columnsEmpty columns dropped: traffic.uniq, traffic.revenue, traffic.charge, traffic.earning, total.charge, total.null, total.revenue, confirmed.charge, confirmed.null, confirmed.revenue, pending.charge, pending.earning, pending.null, pending.revenue, pending.count, declined.charge, declined.null, declined.revenue, hold.charge, hold.earning, hold.null, hold.revenue, hold.count, views, ctr, ecpm, impressions.revenue
How the same answer renders as the stats-grid widget in a UI-capable client — sortable columns, live row filter, and empty columns auto-dropped. Affiliate names are anonymized for this demo.

From Ad Hoc to a Repeatable Workflow

The MCP is not a one-shot query tool. It is a conversation. After the initial answer, you can follow up, dig deeper, or pivot to a related question without starting over.

You might ask for last week's top partners, notice one of them dropped 40%, then immediately ask for their recent conversions to see if it is a volume issue or a quality issue. The AI holds the context from the previous answers, so you can ask "how do their recent conversions look?" and it understands which partner you mean.

Over time, you will develop a set of questions you run every Monday morning or every Friday before payout is approved. Those questions become part of your daily routine, and the routine gets faster because the AI already knows what you tend to ask next.


Getting Connected

Setup takes about two minutes. Open the quickstart guide for step-by-step instructions for Claude, Cursor, and Continue.dev.

For Claude, you add a custom connector pointing to https://mcp.affise.com/mcp and authenticate with one click via OAuth in your browser. After that, your AI assistant has access to your Affise data for the session.

For teams, a static API key option is also available if you prefer not to use OAuth.


Start Asking

If you manage an affiliate program on Affise, the data you need is already there. The MCP gives you a faster way to get at it: ask in plain English, get the answer, act on it.

Open the quickstart guide and connect in the next two minutes. Your Monday morning will look different next week.