Integration Utmstat
and MD5 hash
Using the API without a programmer.
Connection in 5 minutes, 30 days for tests.
Use it for free for 30 days, all functions are available without restrictions
80 673 722
Webhooks have been accepted
138 044 346
Actions have been done
2000+
Customer consultations
200+
Connectors with services
600+
Events and actions
| ID | Название |
event_name
|
Event code |
id
|
Application ID |
project_id
|
Project ID |
status_id
|
Status code |
status_name
|
Status |
amount
|
Sum |
type.id
|
The code of the client's contact method |
type.name
|
The name of the client's contact method |
contact.id
|
Contact ID |
contact.phone
|
Telephone |
contact.email
|
|
contact.name
|
Name |
fields.order_price.value
|
Potential revenue by application |
source.first_click.utm.utm_source
|
Utm source in the "First Click" attribution |
source.first_click.utm.utm_medium
|
Utm medium in the "First Click" attribution |
source.first_click.utm.utm_campaign
|
Utm campaign in the "First Click" attribution |
source.first_click.utm.utm_content
|
Utm content in the "First Click" attribution |
source.first_click.utm.utm_term
|
Utm term in the "First Click" attribution |
source.first_click.ppc.campaign_id
|
The campaign ID in the "First click" attribution |
source.first_click.ppc.group_id
|
The ID of the group in the "First click" attribution |
source.first_click.ppc.ad_id
|
The ad ID in the "First click" attribution |
source.first_click.ppc.phrase_id
|
The ID of the phrase in the "First click" attribution |
source.first_click.ppc.keyword
|
The keyword in the attribution is "First click" |
source.first_click.device.device_type_id
|
The device type code in the "First click" attribution |
source.first_click.device.device_type_name
|
The name of the device type in the "First click" attribution |
source.first_click.device.device_id
|
The device code in the "First click" attribution |
source.first_click.device.device_name
|
The name of the device in the "First click" attribution |
source.first_click.device.screen_resolution
|
Screen resolution in the "First click" attribution |
source.first_click.site.domain
|
Domain in the "First click" attribution |
source.first_click.site.url
|
Url in the "First click" attribution |
source.first_click.site.url_path
|
Url without parameters in the "First click" attribution |
source.first_click.geo.country_id
|
Country code by SxGeo in the "First click" attribution |
source.first_click.geo.country_name
|
Country name by SxGeo in the "First click" attribution |
source.first_click.geo.region_id
|
The SxGeo region code in the "First Click" attribution |
source.first_click.geo.region_name
|
The name of the region according to SxGeo in the "First click" attribution |
source.first_click.geo.city_id
|
The SxGeo area code in the "First Click" attribution |
source.first_click.geo.city_name
|
The name of the city according to SxGeo in the "First click" attribution |
source.first_click.clients_id.utmstat_client_id
|
Client id for utmstat in the "First click" attribution |
source.first_click.clients_id.google_client_id
|
Client id for google analytics in the "First click" attribution |
source.first_click.clients_id.yandex_client_id
|
Client id for yandex. metrica in the "First click" attribution |
source.first_click.clients_id.facebook_client_id
|
Client id for Facebook in the "First click" attribution |
source.first_click.date.created_at
|
The date the click was created in the "First click" attribution |
source.first_click.date.timestamp
|
Timestamp of creating a click in the "First click" attribution |
source.last_significant_click.utm.utm_source
|
Utm source in the "Last significant Click" attribution |
source.last_significant_click.utm.utm_medium
|
Utm medium in the "Last significant Click" attribution |
source.last_significant_click.utm.utm_campaign
|
Utm campaign in the "Last Significant Click" attribution |
source.last_significant_click.utm.utm_content
|
Utm content in the "Last significant Click" attribution |
source.last_significant_click.utm.utm_term
|
Utm term in the "Last significant Click" attribution |
source.last_significant_click.ppc.campaign_id
|
The campaign ID in the "Last significant Click" attribution |
source.last_significant_click.ppc.group_id
|
The ID of the group in the "Last significant click" attribution |
source.last_significant_click.ppc.ad_id
|
The ad ID in the "Last significant click" attribution |
source.last_significant_click.ppc.phrase_id
|
The ID of the phrase in the "Last significant click" attribution |
source.last_significant_click.ppc.keyword
|
The keyword in the attribution is "Last significant click" |
source.last_significant_click.device.device_type_id
|
The device type code in the "Last significant click" attribution |
source.last_significant_click.device.device_type_name
|
The name of the device type in the "Last significant click" attribution |
source.last_significant_click.device.device_id
|
The device code in the "Last significant click" attribution |
source.last_significant_click.device.device_name
|
The name of the device in the "Last significant click" attribution |
source.last_significant_click.device.screen_resolution
|
The screen resolution in the "Last significant click" attribution |
source.last_significant_click.site.domain
|
The domain in the "Last significant click" attribution |
source.last_significant_click.site.url
|
Url in the "Last significant click" attribution |
source.last_significant_click.site.url_path
|
Url without parameters in the "Last significant click" attribution |
source.last_significant_click.geo.country_id
|
The country code according to SxGeo in the "Last significant click" attribution |
source.last_significant_click.geo.country_name
|
The name of the country according to SxGeo in the "Last significant click" attribution |
source.last_significant_click.geo.region_id
|
The SxGeo region code in the "Last significant Click" attribution |
source.last_significant_click.geo.region_name
|
The name of the region according to SxGeo in the "Last significant click" attribution |
source.last_significant_click.geo.city_id
|
The SxGeo area code in the "Last significant Click" attribution |
source.last_significant_click.geo.city_name
|
The name of the city according to SxGeo in the "Last significant click" attribution |
source.last_significant_click.clients_id.utmstat_client_id
|
Client id for utmstat in the "Last significant click" attribution |
source.last_significant_click.clients_id.google_client_id
|
Client id for google analytics in the "Last significant Click" attribution |
source.last_significant_click.clients_id.yandex_client_id
|
Client id for yandex.metrica in the "Last significant click" attribution |
source.last_significant_click.clients_id.facebook_client_id
|
Client id for Facebook in the "Last significant Click" attribution |
source.last_significant_click.date.created_at
|
The date the click was created in the "Last significant click" attribution |
source.last_significant_click.date.timestamp
|
Timestamp of click creation in the "Last significant Click" attribution |
You can add any fields that are available in the webhook.
Field description page
| ID | Название |
event_name
|
Event code |
id
|
Application ID |
project_id
|
Project ID |
status_id
|
Status code |
status_name
|
Status |
amount
|
Sum |
type.id
|
The code of the client's contact method |
type.name
|
The name of the client's contact method |
contact.id
|
Contact ID |
contact.phone
|
Telephone |
contact.email
|
|
contact.name
|
Name |
fields.order_price.value
|
Potential revenue by application |
source.first_click.utm.utm_source
|
Utm source in the "First Click" attribution |
source.first_click.utm.utm_medium
|
Utm medium in the "First Click" attribution |
source.first_click.utm.utm_campaign
|
Utm campaign in the "First Click" attribution |
source.first_click.utm.utm_content
|
Utm content in the "First Click" attribution |
source.first_click.utm.utm_term
|
Utm term in the "First Click" attribution |
source.first_click.ppc.campaign_id
|
The campaign ID in the "First click" attribution |
source.first_click.ppc.group_id
|
The ID of the group in the "First click" attribution |
source.first_click.ppc.ad_id
|
The ad ID in the "First click" attribution |
source.first_click.ppc.phrase_id
|
The ID of the phrase in the "First click" attribution |
source.first_click.ppc.keyword
|
The keyword in the attribution is "First click" |
source.first_click.device.device_type_id
|
The device type code in the "First click" attribution |
source.first_click.device.device_type_name
|
The name of the device type in the "First click" attribution |
source.first_click.device.device_id
|
The device code in the "First click" attribution |
source.first_click.device.device_name
|
The name of the device in the "First click" attribution |
source.first_click.device.screen_resolution
|
Screen resolution in the "First click" attribution |
source.first_click.site.domain
|
Domain in the "First click" attribution |
source.first_click.site.url
|
Url in the "First click" attribution |
source.first_click.site.url_path
|
Url without parameters in the "First click" attribution |
source.first_click.geo.country_id
|
Country code by SxGeo in the "First click" attribution |
source.first_click.geo.country_name
|
Country name by SxGeo in the "First click" attribution |
source.first_click.geo.region_id
|
The SxGeo region code in the "First Click" attribution |
source.first_click.geo.region_name
|
The name of the region according to SxGeo in the "First click" attribution |
source.first_click.geo.city_id
|
The SxGeo area code in the "First Click" attribution |
source.first_click.geo.city_name
|
The name of the city according to SxGeo in the "First click" attribution |
source.first_click.clients_id.utmstat_client_id
|
Client id for utmstat in the "First click" attribution |
source.first_click.clients_id.google_client_id
|
Client id for google analytics in the "First click" attribution |
source.first_click.clients_id.yandex_client_id
|
Client id for yandex. metrica in the "First click" attribution |
source.first_click.clients_id.facebook_client_id
|
Client id for Facebook in the "First click" attribution |
source.first_click.date.created_at
|
The date the click was created in the "First click" attribution |
source.first_click.date.timestamp
|
Timestamp of creating a click in the "First click" attribution |
source.last_significant_click.utm.utm_source
|
Utm source in the "Last significant Click" attribution |
source.last_significant_click.utm.utm_medium
|
Utm medium in the "Last significant Click" attribution |
source.last_significant_click.utm.utm_campaign
|
Utm campaign in the "Last Significant Click" attribution |
source.last_significant_click.utm.utm_content
|
Utm content in the "Last significant Click" attribution |
source.last_significant_click.utm.utm_term
|
Utm term in the "Last significant Click" attribution |
source.last_significant_click.ppc.campaign_id
|
The campaign ID in the "Last significant Click" attribution |
source.last_significant_click.ppc.group_id
|
The ID of the group in the "Last significant click" attribution |
source.last_significant_click.ppc.ad_id
|
The ad ID in the "Last significant click" attribution |
source.last_significant_click.ppc.phrase_id
|
The ID of the phrase in the "Last significant click" attribution |
source.last_significant_click.ppc.keyword
|
The keyword in the attribution is "Last significant click" |
source.last_significant_click.device.device_type_id
|
The device type code in the "Last significant click" attribution |
source.last_significant_click.device.device_type_name
|
The name of the device type in the "Last significant click" attribution |
source.last_significant_click.device.device_id
|
The device code in the "Last significant click" attribution |
source.last_significant_click.device.device_name
|
The name of the device in the "Last significant click" attribution |
source.last_significant_click.device.screen_resolution
|
The screen resolution in the "Last significant click" attribution |
source.last_significant_click.site.domain
|
The domain in the "Last significant click" attribution |
source.last_significant_click.site.url
|
Url in the "Last significant click" attribution |
source.last_significant_click.site.url_path
|
Url without parameters in the "Last significant click" attribution |
source.last_significant_click.geo.country_id
|
The country code according to SxGeo in the "Last significant click" attribution |
source.last_significant_click.geo.country_name
|
The name of the country according to SxGeo in the "Last significant click" attribution |
source.last_significant_click.geo.region_id
|
The SxGeo region code in the "Last significant Click" attribution |
source.last_significant_click.geo.region_name
|
The name of the region according to SxGeo in the "Last significant click" attribution |
source.last_significant_click.geo.city_id
|
The SxGeo area code in the "Last significant Click" attribution |
source.last_significant_click.geo.city_name
|
The name of the city according to SxGeo in the "Last significant click" attribution |
source.last_significant_click.clients_id.utmstat_client_id
|
Client id for utmstat in the "Last significant click" attribution |
source.last_significant_click.clients_id.google_client_id
|
Client id for google analytics in the "Last significant Click" attribution |
source.last_significant_click.clients_id.yandex_client_id
|
Client id for yandex.metrica in the "Last significant click" attribution |
source.last_significant_click.clients_id.facebook_client_id
|
Client id for Facebook in the "Last significant Click" attribution |
source.last_significant_click.date.created_at
|
The date the click was created in the "Last significant click" attribution |
source.last_significant_click.date.timestamp
|
Timestamp of click creation in the "Last significant Click" attribution |
You can add any fields that are available in the webhook.
Field description page
| ID | Название |
event_name
|
Event code |
scoring.rmf_rate
|
RFM Analysis result Code |
scoring.interest_rate
|
Interest rating from 0 to 100 |
scoring.recommendation
|
Recommendation for the manager |
contact.id
|
Contact ID |
contact.name
|
Name |
contact.email
|
|
contact.phone
|
Telephone |
geo.sx_geo_country_id
|
Country code by SxGeo |
geo.sx_geo_country_name
|
Country name by SxGeo |
geo.sx_region_id
|
The region code according to Sx Geo |
geo.sx_region_name
|
The name of the region according to SxGeo |
geo.sx_geo_city_id
|
The area code according to SxGeo |
geo.sx_geo_city_name
|
The name of the city according to SxGeo |
visit.last_visited_at
|
Date of the last visit |
visit.last_visited_days_ago
|
How many days have passed since the last visit |
visit.is_visit_after_last_lead
|
Was there a visit after the last request |
visit.last_7_days_visited_count
|
How many consecutive days has the client visited the site in the last 7 days |
crm.leads.last_lead_created_at
|
Date of the last application |
crm.leads.last_lead_created_days_ago
|
How many days have passed since the last request |
crm.leads.last_lead_updated_at
|
The date of the last update of the application |
crm.leads.last_lead_updated_days_ago
|
How many days have passed since the last update of the application |
crm.leads.last_lead_status_id
|
The status code of the last application |
crm.leads.last_lead_status_name
|
Name of the status of the last application |
crm.leads.last_lead_source_id
|
Code of the application receipt method (call/chat/form) |
crm.leads.last_lead_source_name
|
Name of the application receipt method (call/chat/form) |
crm.leads.last_lead_amount
|
Potential revenue from the application |
crm.leads.last_lead_url
|
The URL of the site where the client left the last request |
crm.leads.last_lead_external_manager_id
|
Manager code from an external CRM (amoCRM/Bitrix24) |
crm.leads.last_lead_external_manager_name
|
The name of the manager from the external CRM (amoCRM/Bitrix24) |
crm.leads.last_lead_external_manager_email
|
Email of the manager from an external CRM (amoCRM/Bitrix24) |
crm.leads.last_lead_external_crm_entity_id.Bitrix24
|
Application ID in Bitrix24 |
crm.leads.last_lead_external_crm_entity_id.AmoCRM
|
Application ID in amoCRM |
crm.leads.last_lead_external_crm_entity_id.RetailCRM
|
Application ID in retailCRM |
crm.leads.last_lead_external_crm_entity_type_id
|
The loyalty code in the external CRM (lead/transaction) |
crm.leads.last_lead_external_crm_entity_type_name
|
The name of the entity in the external CRM (lead/transaction) |
crm.leads.leads_count
|
Total customer requests |
crm.sales.last_sale_created_at
|
The date of creation of the last application that was closed for sale |
crm.sales.last_sale_created_days_ago
|
How many days have passed since the last order closed for sale |
crm.sales.last_sale_amount
|
Revenue from the last sale |
crm.sales.sales_count
|
Total sales by customer |
crm.sales.ltv
|
The client's LTV |
You can add any fields that are available in the webhook.
Field description page
If you haven't found the right event, but the service has the right webhook, then use the universal connector "Incoming webhook". It will be possible to tie the logic of bundles to any field that comes in the webhook.
| ID | Название |
value
|
Meaning |
| Answer fields | |
hash
|
Hash |
Integration setup plan
Utmstat with MD5 хеш
Popular automation tasks that customers solve through us
Add all customer-friendly referral methods in 5 minutes for free
Pass conversion in Yandex metric and google analytics without sophisticated services, end-to-end Analytics and buy other people's rooms
From the website, call tracking, any service, to any stage of the transaction in CRM for full-fledged analytics
The most useful reports based on the yandex.Metrica api, monitoring the availability of important goals, and automatic hints on numbers in reports
Create deals on applications from the website, messengers, and webhooks from other services
Create deals on applications from the website, messengers, and webhooks from other services
With the ability to do analysis through ChatGPT and other LLMs to find customer needs, evaluate the work of managers
Collect audience bots or target customers, and adjust advertising campaigns in Yandex. Direct, Google Ads and Facebook Ads
We are a no-code service and have experience consulting 1000+ clients. We will suggest optimal solutions on how to automate your tasks using AI and no-code.
Support for any telephony and chat service that has webhooks. Analytics inside ApiMonster, it is not necessary to create a ChatGPT, CRM and Google sheets account.
Create, train, and connect a ChatGPT assistant to process incoming requests to respond to clients within a minute based on information from your documentation.
Create, train, and connect a ChatGPT assistant to process incoming requests to respond to clients within a minute based on information from your documentation.
Pass conversion in Yandex metric and google analytics without sophisticated services, end-to-end Analytics and buy other people's rooms
The most useful reports based on the yandex.Metrica api, monitoring the availability of important goals, and automatic hints on numbers in reports
Collect audience bots or target customers, and adjust advertising campaigns in Yandex. Direct, Google Ads and Facebook Ads
From the website, call tracking, any service, to any stage of the transaction in CRM for full-fledged analytics
From the website, call tracking, any service, to any stage of the transaction in CRM for full-fledged analytics
From the website, call tracking, any service, to any stage of the transaction in CRM for full-fledged analytics
Receive applications from the Vkontakte lead form and send them to CRM, google sheets and any services that have a connector or a suitable API.
Receive applications from the Facebook lead form and send them to CRM, google sheets, and any services that have a connector or a suitable API.
Create deals on applications from the website, messengers, and webhooks from other services
Create deals on applications from the website, messengers, and webhooks from other services
With the ability to do analysis through ChatGPT and other LLMs to find customer needs, evaluate the work of managers
Create, train, and connect a ChatGPT assistant to process incoming requests to respond to customers within a minute based on information about your services or products.
From the website, call tracking, any service, to any stage of the transaction in CRM for full-fledged analytics
From the website, call tracking, any service, to any stage of the transaction in CRM for full-fledged analytics
From the website, call tracking, any service, to any stage of the transaction in CRM for full-fledged analytics
With the ability to do analysis through ChatGPT and other LLMs to find customer needs, evaluate the work of managers
Download applications from the website, marketplaces, expenses from Yandex. Direct and other advertising services.
Automatic creation of an order in CDEK and assignment of a track number. Support from CDEK managers.
Automatic order creation in DPD and assignment of a track number. Support from DPD managers.
Automate responses to reviews in marketplaces using standard responses or using a ChatGPT assistant trained on your data.
Orders - delivery and pickup, generation of a YML feed of dishes for uploading to Tilda
Personally in the bot or in a general chat with the managers.
Notify your customers about the status of orders or important events.
Automate the addition of candidate responses to your CRM
ApiMonster is a ready-made set of connectors with powerful data movement logic configuration capabilities. By using ApiMonster, you will skip the difficult and expensive stage of developing your connectors.
ApiMonster is a ready-made set of connectors with powerful data movement logic configuration capabilities. By using ApiMonster, you will skip the difficult and expensive stage of developing your connectors.
Set up backup monitoring of the availability of your sites and API with a telegram notification to quickly find out if something has fallen.
They trust us
Ready-made connectors and tools
Connectors and tools
More than 200 services + any api/webhook service.
If there is no connector for the service, but it has an api and webhooks, then you can connect via universal connectors: Incoming webhook, Outgoing webhook, JavaScript.
Cases
ai
More detailed
AI seller based on ChatGPT for Avito
Logistics
More detailed
As we have sent 133,702 orders to SDEK
End-to-end analytics
More detailed
How to connect 1C, ERP, and anything else to end-to-end analytics
CRM
More detailed
How to create a deal in CRM using no-code using the example of amoCRM
Web analytics
More detailed
Ultra-accurate conversion rate to yandex.Metrica without duplicates
Call tracking
More detailed
Dynamic call tracking for Yandex.Metrica based on your telephony
DWH
More detailed
Uploading data to ClickHouse using the example of expenses from Yandex.Direct
Payments
More detailed
We receive payment notifications from Point Bank and make receipts.
End-to-end analytics
More detailed
Download costs of Yandex Direct / VK ADS in Google Sheets
Web analytics
More detailed
How to correctly pour 1 653 109 conversion Yandex Metric and Google analytics 4
No-code
More detailed
How to make a free no-code service for clients of an advertising agency or saas service
No-code
More detailed
Client: CDEK
Уважаемые коллеги и партнеры из команды API Monster Хочу выразить искреннюю благодарность за ваше неоценимое сотрудничество и выдающуюся работу, которую вы проделали. Благодаря вашему профессионализму и высокому уровню компетентности, нам удалось значительно улучшить наши процессы и достичь поставленных целей.
Ваши идеи и подходы к решению задач стали незаменимыми в нашей работе. Каждый из вас внес свой уникальный вклад, и совместные усилия принесли впечатляющие результаты. Я особенно ценю вашу отзывчивость и готовность идти навстречу, когда возникали сложности. Это создало обстановку доверия и взаимопонимания, что стало важным аспектом нашего успешного взаимодействия.
Мы уверены, что для дальнейших достижений нам предстоит продолжить сотрудничество, и с нетерпением ждем новых возможностей для совместной работы. Спасибо вам за преданность делу, упорство и креативный подход. Вы — настоящая команда профессионалов. Надеюсь на развитие наших отношений и новые успехи впереди.
Client: 165908
All services are collected in one place. Stable work. Great support. Request processing speed.
Client: 164149
Prompt, clear and well-coordinated work of managers, 100% fulfillment of a given task.
Client: 156985
There are no problems with integration, and if problems arise, they help to solve them. Excellent service!
Client: 162147
Apimonster — really helps to quickly connect different services without difficulties and programmers. Simple and clear, saves time and effort. Great for making work easier and faster.
Client: 161883
I just started using it, I needed to integrate the responses with Avito, I wrote, created an application, they sent me a chat with a specialist very quickly, and they integrated it for free within 30 minutes. I'm thrilled. Very high quality, fast, everything works! I'm surprised that...
Client: 161104
The service specialists really understand the need and try to implement it. Because the available tools were not enough, they even made improvements for me - very cool!
Client: 158789
Tariffs, availability of the right bundle, good support, availability of a free trial period.
Client: 157577
Everything is working well.
Client: 149523
Integration of ozone and DPD delivery service, everything was set up promptly, there are no complaints. I can't mention any technical aspects, but I hope the guys know what they're doing.
Client: 149643
We connected it quickly and in a very organized manner, and immediately debugged it on 1 order. Very convenient service, full unloading, taking into account the specifics and wishes. Thanks!
Client:
We have already connected the second store in Ozone in the office of Apimonstr for loading orders before delivery to the Sdec. It is very convenient, the order was taken to Ozone, after 3 minutes it is ready for delivery to the Sdec, nothing else needs to be filled in manually. My money for the service of an Aptmonster in mesya...
Client: 141238
Good integration of SDEC with ozone. Fast and convenient.
Client: 149000
The support is the best of all. It was set up automatically quickly and on a turnkey basis. Most importantly, it's free) I went to work on ozone through sdek for a long time, the guys, with the help of their service and perseverance in terms of doing everything quickly, convinced me to start working yesterday! That 's why...
Client: 148976
We just connected it, and I'll just say one thing. It's just the highest level, as integration with marketplaces is something. I definitely recommend it. Managers and ATI specialists are masters of their craft, there was a task that I only understood in my head that it was possible...
Client: 148061
Everything is working correctly, and this is the most important thing.
Client: 143197
Many services are already connected to apimonster, there are templates and configuration instructions. Plus, support helps you solve a turnkey task! It's very convenient!
Client: 143071
Sdec is cheaper than using ozone.
Client: 142338
speed of execution, individual approach, chat support, good service to attract customers, we will contact you
Client: 140964
Excellent integration system. The team promptly set up the OZON-SDEK data exchange, everything works without errors. great time savings on order processing, which makes life easier)