Create a Sales Intelligence Trace: crm.tracking.trace.add
If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect to the MCP server so that the assistant can utilize the official REST documentation.
Scope:
crmWho can execute the method:
- any user can create a trace
- a user with permission to modify the object can link the trace
The method crm.tracking.trace.add creates a Sales Intelligence trace and returns its identifier.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
TRACE* |
JSON string containing trace data. You can retrieve a ready-to-use value on the website via If you create
In this example, only one UTM parameter is passed to the trace: |
|
ENTITIES |
Array of objects to be linked with the trace (detailed description) If |
Parameter ENTITIES
|
Name |
Description |
|
TYPE* |
CRM object type. Possible values:
|
|
ID* |
CRM object identifier. You can retrieve the identifier using the crm.item.list method with The user must have modification rights for the specified object |
Code Examples
How to Use Examples in Documentation
Example of creating a Sales Intelligence trace, where:
TRACE— JSON string with theutm_sourceUTM parameter and the valuegoogle-mapsENTITIES— contact and lead linked to the trace
curl -X POST \
-H "Content-Type: application/json" \
-d '{
"TRACE": "{\"tags\":{\"list\":{\"utm_source\":\"google-maps\"}}}",
"ENTITIES": [
{
"TYPE": "CONTACT",
"ID": 17
},
{
"TYPE": "LEAD",
"ID": 1000739
}
]
}' \
"https://**put.your-domain-here**/rest/**user_id**/**webhook_code**/crm.tracking.trace.add.json"
curl -X POST \
-H "Content-Type: application/json" \
-d '{
"TRACE": "{\"tags\":{\"list\":{\"utm_source\":\"google-maps\"}}}",
"ENTITIES": [
{
"TYPE": "CONTACT",
"ID": 17
},
{
"TYPE": "LEAD",
"ID": 1000739
}
],
"auth": "**put_access_token_here**"
}' \
"https://**put.your-domain-here**/rest/crm.tracking.trace.add.json"
// This snippet is an ES module: top-level await requires type="module" or a bundler.
// $b24 is an already-initialized SDK instance (see the SDK "Get started" guide).
import { Text } from '@bitrix24/b24jssdk'
import type { B24Frame } from '@bitrix24/b24jssdk'
declare const $b24: B24Frame
try {
const response = await $b24.actions.v2.call.make<number>({
method: 'crm.tracking.trace.add',
params: {
TRACE: '{"tags":{"list":{"utm_source":"google-maps"}}}',
ENTITIES: [
{
TYPE: 'CONTACT',
ID: 17,
},
{
TYPE: 'LEAD',
ID: 1000739,
},
],
},
requestId: Text.getUuidRfc4122()
})
// The payload is available only on a successful response
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
} else {
const result = response.getData()!.result
console.info('Created trace ID:', result)
}
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
<!-- Load the SDK (UMD build); it is exposed as the global B24Js -->
<script src="https://unpkg.com/@bitrix24/b24jssdk@1/dist/umd/index.min.js"></script>
<script>
async function addTrackingTrace() {
try {
// Initialize the SDK inside a Bitrix24 frame
const $b24 = await B24Js.initializeB24Frame()
const response = await $b24.actions.v2.call.make({
method: 'crm.tracking.trace.add',
params: {
TRACE: '{"tags":{"list":{"utm_source":"google-maps"}}}',
ENTITIES: [
{
TYPE: 'CONTACT',
ID: 17,
},
{
TYPE: 'LEAD',
ID: 1000739,
},
],
},
requestId: B24Js.Text.getUuidRfc4122()
})
// The payload is available only on a successful response
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
return
}
const result = response.getData().result
console.info('Created trace ID:', result)
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', addTrackingTrace)
</script>
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.crm.tracking.trace.add(
trace="{\"tags\":{\"list\":{\"utm_source\":\"google-maps\"}}}",
entities=[
{
"TYPE": "CONTACT",
"ID": 17
},
{
"TYPE": "LEAD",
"ID": 1000739
}
],
)
result = bitrix_response.response.result
print(result)
except BitrixAPIError as error:
print(
"Bitrix API Error",
f"error: {error.error}",
f"error_description: {error.error_description}",
sep="\n",
)
except BitrixSDKException as error:
print(f"Bitrix SDK Error: {error.message}")
except Exception as error:
print(f"Unexpected error: {error}")
try {
$response = $b24Service
->core
->call(
'crm.tracking.trace.add',
[
'TRACE' => '{"tags":{"list":{"utm_source":"google-maps"}}}',
'ENTITIES' => [
[
'TYPE' => 'CONTACT',
'ID' => 17,
],
[
'TYPE' => 'LEAD',
'ID' => 1000739,
],
],
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error adding trace: ' . $e->getMessage();
}
BX24.callMethod(
'crm.tracking.trace.add',
{
TRACE: '{"tags":{"list":{"utm_source":"google-maps"}}}',
ENTITIES: [
{
TYPE: 'CONTACT',
ID: 17
},
{
TYPE: 'LEAD',
ID: 1000739
}
]
},
function(result)
{
if (result.error())
{
console.error(result.error());
}
else
{
console.info(result.data());
}
}
);
$result = CRest::call(
'crm.tracking.trace.add',
[
'TRACE' => '{"tags":{"list":{"utm_source":"google-maps"}}}',
'ENTITIES' => [
[
'TYPE' => 'CONTACT',
'ID' => 17,
],
[
'TYPE' => 'LEAD',
'ID' => 1000739,
],
],
]
);
echo '<pre>';
print_r($result);
echo '</pre>';
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "crm.tracking.trace.add", b24.Params{
"TRACE": "{\"tags\":{\"list\":{\"utm_source\":\"google-maps\"}}}",
"ENTITIES": []b24.Params{
{
"TYPE": "CONTACT",
"ID": 17,
},
{
"TYPE": "LEAD",
"ID": 1000739,
},
},
})
if err != nil {
return fmt.Errorf("crm.tracking.trace.add: %w", err)
}
var newID b24.ID
if err := json.Unmarshal(res.Result, &newID); err != nil {
return fmt.Errorf("parse response: %w", err)
}
fmt.Println("id:", newID)
Response Handling
HTTP status: 200
{
"result": 1581,
"time": {
"start": 1786711683,
"finish": 1786711683.296598,
"duration": 0.296597957611084,
"processing": 0,
"date_start": "2026-08-14T15:48:03+03:00",
"date_finish": "2026-08-14T15:48:03+03:00",
"operating_reset_at": 1786712283,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Identifier of the created trace |
|
time |
Information about the request execution time |
Error Handling
HTTP status: 400
{
"error": "ERROR_CORE",
"error_description": "Parameter `TRACE` required."
}
|
Name |
Description |
|
error |
String error code. It may consist of digits, Latin letters, and underscores |
|
error_description |
Textual description of the error. The description is not intended to be shown to the end user in its raw form |
Possible Error Codes
|
Status |
Code |
Description |
Value |
|
|
|
Parameter |
The |
|
|
|
Can not parse JSON in parameter |
The value |
|
|
|
Wrong TYPE in parameter |
An invalid |
|
|
|
Wrong ID in parameter |
An incorrect |
|
|
|
You have no access to entity |
No permission to modify the object specified in |
Statuses and System Error Codes
HTTP Status: 20x, 40x, 50x
The errors described below may occur when calling any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The current method is not permitted for calls using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The HTTPS protocol is required for method calls |
|
|
|
The REST API is blocked due to overload. This is a manual individual block; please contact Bitrix24 technical support to lift it |
|
|
|
The REST API is only available on commercial plans |
|
|
|
The user associated with the access token or webhook used to call the method lacks the necessary permissions |
|
|
|
The manifest is not available |
|
|
|
The request requires higher privileges than those provided by the webhook token |
|
|
|
The provided access token has expired |
|
|
|
The user does not have access to the application. This means that the application is installed, but the portal administrator has restricted access to this application to specific users only |
|
|
|
The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the "Temporary closure of the public part of the site" option. Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site |