Works with what you already have
Your store, app, messengers, CRM, ad accounts and data warehouses. Only what already works and is connected in the interface is listed here.
Website and store
Events, orders and the catalog reach the platform without development: with a store plugin or a couple of lines of code.
JS tracker
Page views, carts, orders, UTM tags, web push, widgets, forms and chat with one script. Works in single-page apps too.
WooCommerce
A WordPress plugin: server-side orders and statuses, customers and consents, the catalog, store emails, search, points and promo codes.
Magento 2 and Adobe Commerce
A module with the same scope, installed with Composer.
1C-Bitrix
A module for 1C-Bitrix Site Manager with the same scope.
1C: in-store receipts
An extension for 1C retail products sends in-store receipts, so offline purchases land in the customer profile.
PHP and Laravel
A library for the whole API and a Laravel package: a tracker directive, an event queue and catalog sync.
Tilda, InSales, Google Tag Manager
The tracker is added as a code snippet: the help center has step-by-step guides for site builders and GTM.
Product feeds
The catalog from YML, Google Merchant, CSV or JSON on a schedule, or through the API.
Mobile apps
The SDKs collect app events and receive push and in-app messages.
Android and iOS
Native SDKs in Kotlin and Swift: events, screens, user sign-in and an offline event queue.
Flutter and React Native
The same scope for cross-platform apps.
Firebase Cloud Messaging and APNs
Mobile push for Android and iOS through your own Firebase and Apple keys.
In-app messages
A modal, a banner or a full screen inside the open app.
from the Growth plan
Messaging channels
Every channel is connected in the interface with your own keys, and messages go out under your name.
Email
The platform’s own mail service sending from your domain (DKIM, bounces, complaints, a suppression list) or your SMTP server.
SMS
SMS.ru, SMSC.ru, Twilio or your gateway’s HTTP API.
from the Growth plan
WhatsApp
WhatsApp Business Cloud API: templates, product carousels and forms.
from the Growth plan
Viber
Messages by phone number through SMSC.ru, Infobip or your own HTTP API.
from the Growth plan
Telegram, MAX and a Viber bot
Bots connected by token: campaigns, journeys and replies to customers.
VK, Instagram and Facebook Messenger
Messages on behalf of your community, business account and page.
from the Growth plan
Web Push
Browser notifications on your own keys, with no third-party services.
Apple Wallet and Google Wallet
A loyalty card with points and a tier in the phone wallet — and one more messaging channel.
from the Growth plan
Webhook
A signed request to your server — for your own notification system.
Live chat
Questions from every channel land in one operator inbox, and the reply goes back where the question came from.
Messengers and social networks
Telegram, WhatsApp, Viber, MAX, VK, Instagram Direct and Facebook Messenger in the operator inbox.
from the Growth plan
Support mailbox
An IMAP mailbox or inbound webhooks from Postmark, SendGrid, Mailgun and Cloudflare Email Workers.
from the Growth plan
Helpdesks and your own bots
Chat event webhooks and a conversations API — for an external support system or your own bot.
CRM
Contacts and deals become profiles and events, and segments go back to the CRM.
- amoCRM
- Kommo
- Битрикс24
- HubSpot
- Pipedrive
- Zoho CRM
- Odoo
- Salesforce
- Microsoft Dynamics 365
from the Growth plan
Two-way sync
Contacts, leads and deals go into profiles and events; segments go back to the CRM as a tag, a field or a list.
Journey steps
A journey creates a deal, moves its stage or assigns a task to a manager.
Advertising
Segments become ad audiences, and purchases return to the ad accounts as conversions.
- Meta
- Google Ads
- Яндекс Аудитории
- Яндекс Метрика
- VK Реклама
from the Growth plan
Audiences
Segments go to Meta, Yandex Audiences, VK Ads and Google Ads and stay up to date on their own.
Server-side conversions
Purchases are sent to Meta Conversions API, Yandex Metrica, Google Ads and VK Ads.
Data and warehouses
Data comes in from files and your warehouses and goes out to where your analysts work.
File import
Profiles from CSV and Excel, in-store receipts as a file.
Scheduled sources
A file by URL, a file from S3 or a Google Sheet: CSV, JSON and JSON Lines.
from the Growth plan
Reading from warehouses
PostgreSQL, ClickHouse, BigQuery and Snowflake: a table or your own query, changed rows only.
on the Enterprise plan
Export to warehouses
S3, Google Cloud Storage, BigQuery, Snowflake, ClickHouse and PostgreSQL.
on the Enterprise plan
Moving from other platforms
The built-in migration moves your data without developers and keeps syncing changes while you switch your site and campaigns.
- Mindbox
- Customer.io
- Retail Rocket
from the Growth plan
What is moved
Profiles, consents, segments, events, orders and email templates.
AI assistants
The platform and your store are available to AI assistants over MCP — with the same permissions as the key or the user.
Project MCP server
Claude and ChatGPT connect to the project as a connector; Claude Code, Cursor and other MCP clients use a key. There is a read-only mode.
from the Growth plan
Your store in shopper assistants
ChatGPT and Claude find products in your catalog, answer questions about them and lead to a purchase.
from the Growth plan
Store data for the chat AI bot
The bot sees orders, delivery and stock from your store; ready in the WooCommerce, Magento 2 and 1C-Bitrix modules.
API and webhooks
Everything in the interface is available to your systems.
REST API
Events, profiles, segments, journeys, campaigns, the catalog, loyalty and chat; described in OpenAPI.
Transactional messages
A message to one customer with an API request: an order confirmation, a code, a delivery status.
Webhooks
A journey step, an audience export and chat events send signed requests to your server.
Don’t see the integration you need?
Tell us what you need to connect: a lot can be done with the API, webhooks and data sources.
Try it on your own data
14 days on the Growth plan, no card required: up to 1,000 profiles and 500 emails a day.