List which attribution fields have data on the deals
crm.attribution.facets
ReadIdempotentSince 2026-11-01
Tells which attribution fields are filled on the deals (count per field: platform, campaignName, adsetName, adName, formName, utmSource, utmCampaign, keyword, attributionMethod, matchConfidence, click ids…) with up to 200 distinct values each and their display label, plus the distinct countries and product lines. Use it before crm.analytics.pivot to choose attr.* dimensions and filter values that actually exist. Members without view_all_performance only see their own deals. Scans up to 30,000 deals. Through the API and the MCP it depends on the terms of LinkedIn: where they do not allow it, it answers 403 platform_terms_restricted (the permissions guide lists what each platform allows).
Scope
crm:read
Permission
View the module · CRM action: view_performance
MCP tool
crm_attribution_facetsOn the full surface; on the compact one, mb_execute_operation with id: "crm.attribution.facets".
Declared cost: up to 30003 reads and 0 writes per call (they count against the daily quota).
Click-to-WhatsApp attribution for a period of at most 400 days: per Meta ad (with campaign and placement), the WhatsApp conversations it started (leads), the deals created from meta_ads and how many were won, plus totals and conversion rate (won / leads); optionally for one pipeline. These are org-wide aggregates, exactly as in the app (no per-seller scoping). Up to 30,000 conversations and 30,000 deals are scanned; truncated: true means partial numbers. Ad spend is not included.
Scope
crm:read
Permission
View the module · CRM action: view_performance
MCP tool
crm_attribution_ctwaOn the full surface; on the compact one, mb_execute_operation with id: "crm.attribution.ctwa".
Declared cost: up to 60000 reads and 0 writes per call (they count against the daily quota).
Parameters
startintegerqueryrequired
Start of the date range, epoch ms (UTC).
endintegerqueryrequired
End of the date range, epoch ms (UTC), not before start.
pipeline_idstringqueryoptional
Only the deals of this pipeline (Pipeline id from crm.pipelines.list.).
MB Suite Pixel (web tracking) attribution for a period of at most 400 days: the website leads matched in the period (WhatsApp conversations paired with a click on the site and submissions of the organization's Web Forms, one lead each) grouped by platform, source and campaign, with the deals those leads generated and how many were won, paid vs organic (is_paid: an ad click id or a paid utm_medium), average match score (see match_score_avg) and counts by match confidence. A deal counts once, in the group of the first lead of the period that generated it (a prospect counts when converted; a merged deal counts as the deal it was merged into); archived deals, and the earlier deal a returning contact lands in, are left out. pipeline_id narrows the deals, not the leads. min_confidence drops weaker matches (default low = all). Org-wide aggregates, as in the app. Clicks are kept 90 days. Up to 30,000 clicks are scanned and the prospects and deals they point to are read by id; truncated: true means partial numbers. With LinkedIn or TikTok, their terms limit it through the API and the MCP: what they do not allow answers 403 platform_terms_restricted, and their records are left out of the response (the permissions guide lists what each platform allows).
Scope
crm:read
Permission
View the module · CRM action: view_performance
MCP tool
crm_attribution_web_trackingOn the full surface; on the compact one, mb_execute_operation with id: "crm.attribution.web_tracking".
Declared cost: up to 90000 reads and 0 writes per call (they count against the daily quota).
Parameters
startintegerqueryrequired
Start of the date range, epoch ms (UTC).
endintegerqueryrequired
End of the date range, epoch ms (UTC), not before start.
pipeline_idstringqueryoptional
Only the deals of this pipeline (Pipeline id from crm.pipelines.list.).
min_confidenceenumqueryoptional
Minimum confidence of the click → lead match: high, medium or low (default, every match). A web form submission is always high.
Revenue of won deals by channel or attribution hierarchy
crm.attribution.revenue
ReadIdempotentSince 2026-11-01
Revenue of the deals WON in a period of at most 400 days, converted to the org's display currency with the exchange rate of each win date: view by_channel groups it by origin channel (google, meta, tiktok, linkedin, whatsapp, web, booking, manual, csv, generic, other); view hierarchy returns flat rows channel → lead source → campaign with attribution method, match confidence and web traffic type, under the first-touch (default) or last-touch model. Each group carries up to 50 deal references (each with its own value and currency). Optional pipeline_id and owner_id; members without view_all_performance only get their own deals. Ad spend and ROAS are not included (they query the ad platforms). With Google Ads, LinkedIn or TikTok, their terms limit it through the API and the MCP: what they do not allow answers 403 platform_terms_restricted, and their records are left out of the response (the permissions guide lists what each platform allows).
Scope
crm:read
Permission
View the module · CRM action: view_performance
MCP tool
crm_attribution_revenueOn the full surface; on the compact one, mb_execute_operation with id: "crm.attribution.revenue".
Declared cost: up to 33403 reads and 0 writes per call (they count against the daily quota).
Parameters
startintegerqueryrequired
Start of the date range, epoch ms (UTC).
endintegerqueryrequired
End of the date range, epoch ms (UTC), not before start.
viewenumqueryoptional
by_channel (default): won revenue per channel with its deals; hierarchy: channel → lead source → campaign with method and confidence.
