Conversiones

List the conversions send-back configuration per platform

crm.conversions.config.list

Returns one row per ad platform (meta, google, tiktok, linkedin) with how the CRM sends offline conversions back to it when deals change: whether sending is enabled, the mapping rules (trigger stage_entered/won/lost, event name or destination, value source), the grace window in minutes, the chosen pixel or ad account with the candidates found by the last connection check (the only values crm.conversions.config.update accepts), and that check step by step (each step with message, its result in words). configured: false means the platform has no saved configuration (defaults shown). Read-only; any CRM member can read it. 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 or fields are left out of the response (the permissions guide lists what each platform allows).

Alcance

crm:read

Permiso

Ver el módulo

Tool del MCP

crm_conversions_config_listEn la superficie completa; en la compacta, mb_execute_operation con id: "crm.conversions.config.list".

Costo declarado: hasta 2 lecturas y 0 escrituras por llamada (cuentan en el cupo diario).

Parámetros

Sin parámetros.

Respuesta

Errores

Ejemplo

curl "https://api.mb-suite.com/v1/crm/conversions/config" \
  -H "Authorization: Bearer $MB_API_KEY"

Probar con tu API key de prueba

Con una API key de prueba el pedido va siempre a tu organización de práctica: datos de ejemplo que puedes reiniciar.

curl "https://api.mb-suite.com/v1/crm/conversions/config" \
  -H "Authorization: Bearer $MB_TEST_KEY"

List conversion events sent to the ad platforms

crm.conversions.events.list

Lists the conversion events the CRM queued or sent back to the ad platforms (one per deal and rule), newest first, paginated by cursor, optionally for one platform: deal, rule, event name, value, status (queued, canceled, sending, sent, failed, retrying, skipped), skip reason, attempts, the platform's error and, for Google, the later ingest confirmation. Read-only history; any CRM member can read it. 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 or fields are left out of the response (the permissions guide lists what each platform allows).

Alcance

crm:read

Permiso

Ver el módulo

Tool del MCP

crm_conversions_events_listEn la superficie completa; en la compacta, mb_execute_operation con id: "crm.conversions.events.list".

Costo declarado: hasta 203 lecturas y 0 escrituras por llamada (cuentan en el cupo diario).

Parámetros

Respuesta

Errores

Ejemplo

curl "https://api.mb-suite.com/v1/crm/conversions/events" \
  -H "Authorization: Bearer $MB_API_KEY"

Probar con tu API key de prueba

Con una API key de prueba el pedido va siempre a tu organización de práctica: datos de ejemplo que puedes reiniciar.

curl "https://api.mb-suite.com/v1/crm/conversions/events" \
  -H "Authorization: Bearer $MB_TEST_KEY"

Update the conversions settings of a platform

crm.conversions.config.update

Updates the settings of one platform: the account or pixel chosen by hand (Meta pixel_id, Google customer_id, TikTok advertiser_id and pixel_code, LinkedIn account_id), only among the candidates found by the last connection check made in the app (crm.conversions.config.list shows them; another value is 400 account_not_linked or pixel_not_in_account), the grace window (0 to 60 minutes) and Google's default consent. Changing the LinkedIn account turns sending off and clears its rules' destinations; changing the TikTok advertiser clears its pixel. Does not enable sending (see crm.conversions.config.set_enabled). Owners and admins only. 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 (the permissions guide lists what each platform allows).

Alcance

crm:write

Permiso

Editar en el módulo · Solo owner, admin · Acción del CRM: manage_attribution

Tool del MCP

crm_conversions_config_updateEn la superficie completa; en la compacta, mb_execute_operation con id: "crm.conversions.config.update".

Costo declarado: hasta 2 lecturas y 1 escrituras por llamada (cuentan en el cupo diario).

Parámetros

Respuesta

Errores

Ejemplo

curl -X PATCH "https://api.mb-suite.com/v1/crm/conversions/config/{platform}" \
  -H "Authorization: Bearer $MB_API_KEY"

Probar con tu API key de prueba

Con una API key de prueba el pedido va siempre a tu organización de práctica: datos de ejemplo que puedes reiniciar.

curl -X PATCH "https://api.mb-suite.com/v1/crm/conversions/config/{platform}" \
  -H "Authorization: Bearer $MB_TEST_KEY"

Replace the conversion rules of a platform

crm.conversions.config.update_rules

Replaces the mapping rules of one platform (up to 30, evaluated by order: the first match wins): trigger stage_entered (with stage_id), won or lost, optional pipeline_id, the event name, value source (deal_value, fixed with fixed_value > 0, or none) and enabled. In an enabled rule the pipeline must exist and the stage must belong to it (or, without pipeline_id, to some pipeline): pipeline_not_found, stage_not_in_pipeline, stage_not_found. Google and LinkedIn rules need a destination_id among the verified conversion actions or rules; TikTok accepts only its standard events; Purchase on Meta and TikTok needs a value. Owners and admins only. 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 (the permissions guide lists what each platform allows).

Alcance

crm:write

Permiso

Editar en el módulo · Solo owner, admin · Acción del CRM: manage_attribution

Tool del MCP

crm_conversions_config_update_rulesEn la superficie completa; en la compacta, mb_execute_operation con id: "crm.conversions.config.update_rules".

Costo declarado: hasta 2 lecturas y 1 escrituras por llamada (cuentan en el cupo diario).

Parámetros

Respuesta

Errores

Ejemplo

curl -X POST "https://api.mb-suite.com/v1/crm/conversions/config/{platform}/rules" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "rules": []
}'

Probar con tu API key de prueba

Con una API key de prueba el pedido va siempre a tu organización de práctica: datos de ejemplo que puedes reiniciar.

curl -X POST "https://api.mb-suite.com/v1/crm/conversions/config/{platform}/rules" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "rules": []
}'

Turn conversions sending on or off for a platform

crm.conversions.config.set_enabled

Turns on (enabled: true) or off the sending of conversions to one platform. Turning it on requires a pixel or account chosen in the connection check made in the app (otherwise conversions_not_verified) and, when the platform has no rules yet, seeds a default one: won deal → Purchase with the deal value (Google and LinkedIn: their purchase-type conversion action or rule, or the first enabled one). From then on, each deal change that matches a rule sends a conversion with hashed contact data to the platform. Turning it off stops new sends; queued ones are skipped. The dry run runs the same check and says where it would send and which rules apply; outside the app, turning it on needs that dry run and its confirm_token (turning it off runs directly). Owners and admins only. 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 (the permissions guide lists what each platform allows).

Pide confirmación: primero dry_run: true (vista previa y confirm_token, que vale 10 minutos y una sola vez), después el mismo cuerpo con confirm_token. En unas pocas, solo con ciertos datos: la descripción dice cuándo. Por qué y cómo: Vista previa y confirmación. En esta, solo cuando: enabled is true (from then on, each deal change that matches a rule sends a conversion with hashed contact data to the ad platform).

Alcance

crm:write

Permiso

Editar en el módulo · Solo owner, admin · Acción del CRM: manage_attribution

Tool del MCP

crm_conversions_config_set_enabledEn la superficie completa; en la compacta, mb_execute_operation con id: "crm.conversions.config.set_enabled".

Costo declarado: hasta 2 lecturas y 1 escrituras por llamada (cuentan en el cupo diario).

Parámetros

Respuesta

Errores

Ejemplo

curl -X POST "https://api.mb-suite.com/v1/crm/conversions/config/{platform}/enabled" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "enabled": true,
  "dry_run": true
}'

Probar con tu API key de prueba

Con una API key de prueba el pedido va siempre a tu organización de práctica: datos de ejemplo que puedes reiniciar.

curl -X POST "https://api.mb-suite.com/v1/crm/conversions/config/{platform}/enabled" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "enabled": true,
  "dry_run": true
}'

Delete the conversions configuration of a platform

crm.conversions.config.delete

Deletes the whole configuration of one platform: the on/off switch, the rules, the chosen account or pixel, the health checks and the test state; sending stops. It does NOT disconnect the integration, does not touch conversion actions created in Google Ads and keeps the send history. There is no trash for this configuration (the audit log keeps a summary), so confirm with the user first; a dry run shows what would be lost (or that the platform has nothing saved). Owners and admins only.

Pide confirmación: primero dry_run: true (vista previa y confirm_token, que vale 10 minutos y una sola vez), después el mismo cuerpo con confirm_token. En unas pocas, solo con ciertos datos: la descripción dice cuándo. Por qué y cómo: Vista previa y confirmación.

Alcance

crm:write y «Permitir eliminar» (crm:delete en OAuth)

Permiso

Editar en el módulo · Solo owner, admin · Acción del CRM: manage_attribution

Tool del MCP

crm_conversions_config_deleteEn la superficie completa; en la compacta, mb_execute_operation con id: "crm.conversions.config.delete".

Costo declarado: hasta 2 lecturas y 1 escrituras por llamada (cuentan en el cupo diario).

Parámetros

Respuesta

Errores

Ejemplo

curl -X POST "https://api.mb-suite.com/v1/crm/conversions/config/{platform}/delete" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "dry_run": true
}'

Probar con tu API key de prueba

Con una API key de prueba el pedido va siempre a tu organización de práctica: datos de ejemplo que puedes reiniciar.

curl -X POST "https://api.mb-suite.com/v1/crm/conversions/config/{platform}/delete" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "dry_run": true
}'