Skip to main content
Altcraft Docs LogoAltcraft Docs Logo
User guideDeveloper guideAdmin guide
Company siteHelp center
English
  • Русский
  • English
v72
  • v74
  • v73
  • v72
Login
  • User documentation
  • FAQ
  • Altcraft glossary
  • Profiles and databases
  • Communication channels
  • Segmentation
  • Message templates
  • Campaigns
  • Automation scenarios
  • Market
  • Loyalty programs
  • Reports and analytics
  • Integrations
    • Action hooks
      • Altcraft Action Hooks
      • Action hooks event types
      • Action Hook Message Structure
      • JSON batch request (HTTP POST action hook)
      • Message to RabbitMQ broker
      • Message to RabbitMQ exchanger
      • Message to Kafka broker
      • Test event
    • Integration of third-party services using Albato
    • Facebook Ads Manager™
    • Google Ads Audiences
    • Yandex.Audience™
    • VK Ads™
    • Static segment synchronization
    • Yandex AppMetrica™
    • Tilda™
    • Lpgenerator™
    • WhatsApp
    • Viber*™ integration
    • Integration scope
    • Notify
  • Weblayers
  • Settings
  • API requests: where to start
  • Changelog
  • library
This is documentation for Altcraft Platform v72. This documentation is no longer maintained.
The information for up-to-date platform version at this page is available (v74).
  • Integrations
  • Action hooks
  • Message to RabbitMQ broker
Documentation for version v72

Message to RabbitMQ broker

Each single event will be sent immediately to the message broker queue. Both a local RMQ, which is part of the platform, and a broker located on an external host can be used.

In the settings, specify the broker's parameters:

  • host name
  • port number
  • username
  • password for authorization
  • virtual host name
  • name of the queue into which event messages will be sent.
caution

RabbitMQ user must have access to the selected virtual host. Create a virtual host and give the RabbitMQ user the right to use it right in RabbitMQ.

You are free to choose whether to set up RabbitMQ queue name: if it is not set - a queue will be named after event type.

Email link click message example.

{
"event_type": "click",
"event_date": "2018-03-04T13:13:19.034315796Z",
"list_id": 111,
"_xxh": "ad1850e0d1d9481e",
"_md5": "145bb30f7ddf1184cb560bc4b7705646",
"is_test": false,
"event_data": {
"browser": "Firefox",
"campaign_id": 973,
"city": "",
"country": "",
"device": "web",
"ip": "10.9.0.14",
"lat": 0,
"launch_id": "00000017000003cd5a9bf01a",
"link_url": "http://www.ford.com",
"lon": 0,
"message_id": 17,
"os": "Linux x86_64",
"postal_code": "",
"region": "",
"segment_id": 0,
"send_message_id": "5a9bf01a17_3cd_11_6f_0_2.5a8c045fc1dde44cbf718f78",
"tz": "",
"user_agent": "Mozilla/5.0 (X11; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0"
},
"custom_data": {
"email": "alice@example.org"
},
"account_id": 23
}
Last updated on Apr 23, 2023
Previous
JSON batch request (HTTP POST action hook)
Next
Message to RabbitMQ exchanger
© 2015 - 2025 Altcraft, LLC. All rights reserved.