Unique user identifier of the agent client on behalf of which the request is made (Is required for the agent) To obtain a list of client users, you must use the method ""get.customer_users""
limit
number
no
Number of records returned. See section "Paging"
offset
number
no
Shift determines from which record number to return "limit" records. Default is "0". See section "Paging"
filter
object
no
See section "Filtering Criteria"
sort
array
no
See section "Sorting data"
date_from
iso8601
yes
YYYY-MM-DD hh:mm:ss
Start date and time of the reporting period.
date_till
iso8601
yes
YYYY-MM-DD hh:mm:ss
Sampling end date
include_tech_offline_messages
boolean
no
Include technical requests that are not customer communications
Response parameters
Name
Type
Valid values
Filtering
Sorting
Default response
Description
id
number
yes
yes
Unique offline message ID.
date_time
iso8601
YYYY-MM-DD hh:mm:ss
Date and time of receipt of the application
text
string
yes
Application text
communication_number
number
yes
yes
Call number. Calculated within persons.
communication_page_url
string
no
no
no
The URL of the page the visitor was on at the time of the call or the page of the visitor's last interaction before the call.
communication_type
enum
offline_message
Communication type.
communication_id
number
yes
yes
Unique communication ID.
is_agree_to_process_personal_data
boolean
yes
Denotes the client's consent to the processing of his personal data
is_agree_to_mailing
boolean
yes
Denotes the client's consent to advertising and information mailings
ua_client_id
string
Unique identifier in Universal Analytics
ym_client_id
string
Unique Yandex.Metrica user identifier
sale_date
iso8601
YYY-MM-DD hh:mm:ss
yes
yes
Trade date
sale_cost
number
yes
yes
Transaction amount
status
enum
processingprocessednot_processed
yes
yes
yes
Application status
process_time
iso8601
YYYY-MM-DD hh:mm:ss
Date and time when the application was submitted transferred to the status "Processed" (see parameter "status")
form_type
enum
Custom, Standard, DataAPI
yes
yes
yes
Type of form used to submit the offline message.
form_name
string
yes
yes
Name of the application form, if the form_name parameter is filled in when submitting the application to our service: https://www.callgear.com/support/api/javascript-api/
search_query
string
yes
Search query
search_engine
string
yes
Search engine name
referrer_domain
string
yes
Referrer domain
referrer
string
yes
Transition source
entrance_page
string
yes
Login page
gclid
string
yes
Google Click Identifier
yclid
string
yes
Yandex Click Identifier
ymclid
string
yes
Yandex Market Click Identifier
ef_id
string
yes
Used for markup links in the control system contextual advertising AdLense
Callback forms may have a field with a comment (text). If the user leaves a comment (text) when generating a call back, it will be displayed in this field.
Group selected by the visitor
group_id
number
yes
yes
Unique identifier group selected by the visitor
group_name
string
yes
yes
Name of the selected group visitor
Employee
employee_id
number
yes
yes
yes
Unique identifier employee who processed application
employee_full_name
string
yes
yes
Last name First name of the Employee, who processed the application
employee_answer_message
string
Answer from the employee who was sent to email address visitor email
employee_comment
string
Employee's comment when transferring the application to status "Processed" (see field "status")
Visitor properties that can be asked via personal office or using JavaScript API [method Comagic.setProperty(name, value);]
property_name
string
The name of the property that should be assigned to the visitor
property_value
string
Property value
Segments
segments
array
yes
Segments
segment_id
number
Unique identifier segment
segment_name
string
Segment name
UTM tags
utm_source
string
yes
Campaign source
utm_medium
string
yes
Campaign Channel
utm_term
string
yes
Campaign keyword
utm_content
string
yes
Campaign content
utm_campaign
string
yes
Campaign name
OS tags
openstat_ad
string
yes
Advertising ID announcements
openstat_campaign
string
yes
Advertising ID campaigns
openstat_service
string
yes
Service ID, service provider
openstat_source
string
yes
Site ID, section, page, place on the page on which it was shown corresponding advertisement
Hit attributes
attributes
array
first - First quality through - End-to-end first quality primary - Primary secondary - Secondary lost - Lost target - Target off-target - Not targeted quality - Quality rest - target repeat requests (requests made during the period of repeated requests configured for the site in the CallGear account).