Complete Guide to Jivo Chat: Setup, API, and CRM Data Transfer

When migrating to a new CMS or launching a project, it's easy to lose the context of client conversations. JivoSite solves this, but standard installation often fails: user data isn't transferred, auto-invitations aren't tailored, and in SPAs the chat may not load after route changes. Professional setup boosts chat conversion by up to 25% and reduces operator response time by 40%. Without integration, up to 30% of leads are lost due to lack of context — our integration cuts this to 5%, which at average order value yields significant additional revenue. A Jivo chat increases conversion 3x compared to traditional feedback forms. Our Jivo chat integration service ensures seamless connection and typically costs from $200 to $800. Professional integration is 2x more effective than DIY in terms of lead retention.

Problems solved by Jivo integration

Loss of dialog context: without CRM data transfer, operators spend up to 2 minutes clarifying details, reducing customer satisfaction. Incorrect routing: when a chat reaches the wrong specialist, response time increases and leads are lost. Lack of analytics: without integration with telephony and CRM, you cannot measure chat effectiveness. A well-executed Jivo chat integration eliminates these problems.

Passing user data to Jivo

Jivo API allows passing arbitrary data via setContactInfo and setCustomData. According to Jivo API Reference (see official docs), setContactInfo supports up to 10 custom fields. This solves context loss: the operator sees name, email, phone, order history, and cart. Proper identification cuts request processing time in half compared to manual entry.

// Identify authorized user
window.jivo_api?.setContactInfo({
    name: user.name,
    email: user.email,
    phone: user.phone,
    description: `ID: ${user.id}, orders: ${user.orders_count}`
});

// Custom data (displayed to operator)
window.jivo_api?.setCustomData([
    {title: 'Cart', content: `${cartTotal} ₽`},
    {title: 'Plan', content: user.plan}
]);

Configuring auto-invitations and routing

Auto-invitations are configured in the Jivo dashboard. We recommend showing the invitation after 15 seconds on the site, excluding checkout pages, and for returning visitors showing it immediately. Routing by operator groups speeds up response: we set up groups by topic and workload, and if no operators are free, a queue with notification. This retains up to 80% of leads that would otherwise be lost during long waits.

Jivo integration with CRM

Jivo has built-in integrations with Bitrix24, AmoCRM, and others, as well as an open REST API for custom sync. We configure real-time dialog and contact data transfer. After each chat, a deal with the conversation history is created in the CRM, eliminating information loss. Additional triggers can be set: for example, automatically sending an SMS notification to the manager upon receiving a lead.

How we integrate Jivo

1. Architecture audit — determine how the site loads (SSR, SPA), what user data is available.
2. Script installation — insert code considering the framework. Example for React/Next.js:

// components/JivoChat.tsx
useEffect(() => {
    const script = document.createElement('script');
    script.src = `//code.jivosite.com/widget/${process.env.NEXT_PUBLIC_JIVO_ID}`;
    script.async = true;
    document.body.appendChild(script);
    return () => document.body.removeChild(script);
}, []);

3. Data transfer — configure setContactInfo after user authentication.
4. Auto-invitations — define rules in the Jivo panel.
5. Routing — distribute chats among operators and groups.
6. Testing — verify script, data transfer, behavior on mobile.
7. Warranty — we provide 14 days of support after integration.

What's included

• Audit of current site architecture and available data.
• Jivo script installation with SPA support (React, Vue, Angular).
• Configuration of user data transfer (name, email, phone, custom fields).
• Auto-invitation setup according to specified scenarios.
• Dialog routing by groups and operator skills.
• CRM integration (Bitrix24, AmoCRM, custom via API).
• Testing of all scenarios and mobile devices.
• Integration documentation and operator training.
• 14 days of technical support after launch.

Comparison: DIY vs Professional Integration

Typical integration mistakes

Timeline and pricing

Typical integration takes 3 to 8 hours depending on complexity (CRM presence, custom fields, number of operators). Pricing is calculated individually after an audit. Request a consultation to get a quote for your project.

Why choose us

• 5+ years of experience in web development and integrations.
• Over 50 successful projects, including e-commerce stores and services.
• We use the official JivoSite API and follow best practices.

Get a free audit of your site — write to us.

Email Campaign Integration: Why Does It Often Break?

We’ve observed that a trigger email sent 10 minutes after registration converts 4–5 times better than the same email sent after 24 hours. This isn’t a marketing myth—it’s mechanics: while the user is still warm, while they remember the context. But most integrations with email services are built like this: form submits → synchronous HTTP request to API → if the API is slow, the user waits 3 seconds → the email either goes out or doesn’t, nobody knows. In one project, we saw a 30% drop in conversion simply because the email service responded with 504 and Laravel’s queue driver wasn’t configured. Lost emails often hit customers silently – no log, no alert, just a missing order confirmation.

If you’re facing lost emails or spam folder issues, order an audit of your current integration – we’ll find bottlenecks within 2 days.

Providers and Their APIs

Unisender — a Russian provider popular in the SMB segment. REST API, simple. Adding a contact: importContacts, sending a transactional email: sendEmail. Important: for transactional emails (order confirmations, password resets), Unisender Go is a separate service with a different API and separate pricing. Mixing bulk and transactional mailings in one stream is bad for domain reputation. Unisender Go handles up to 1000 requests per second.

SendPulse — provides email, SMS, web push, Viber, and Telegram bots through a unified API. Convenient for projects requiring an omnichannel approach. Automation 360 is a visual chain builder; you can trigger automation via API events. The PHP SDK (sendpulse/rest-api-php-sdk) is maintained but updated irregularly – better to use Guzzle directly.

Mailchimp — a choice for international audiences and marketing teams accustomed to the Mailchimp ecosystem. Transactional email via Mandrill (a subsidiary service). Marketing API v3 for list, tag, and campaign management. Webhooks for opens, clicks, unsubscribes, bounces.

SMS. For Russia: SMSCenter, MTS Exolve, Devino Telecom, SMS Aero. Their APIs are similar: a send method with phone, message, sender parameters (sender name must be registered separately with the operator). One nuance: the sender name must be registered through the aggregator with a contract – otherwise SMS won’t be sent on MTS/MegaFon/Beeline networks.

How to Build an Integration That Doesn’t Lose Emails?

Separate Transactional and Marketing Streams

Transactional emails (order confirmations, password resets, delivery status) go through a dedicated sender domain or subdomain tx.example.com. Marketing campaigns go through mail.example.com or news.example.com. If a marketing campaign receives many spam complaints, it should not affect the reputation of the transactional stream. According to SendGrid documentation, transactional messages should be sent through a dedicated IP pool to prevent cross-contamination.

Queue and Retry

Any call to the email API goes through a queue (Laravel Queue, Bull, Celery). If Unisender returns a 503, the job retries after 5 minutes, then 15, then 60. After 5 failed attempts, it goes to a dead letter queue with an alert. The user already received their 200 OK and knows nothing about the issue. This approach reduces bounce rate on projects to 0.5%.

Example Laravel job:

public function handle(): void
{
    try {
        $response = Http::post(config('services.unisender.email_url'), $this->params);
        if ($response->failed()) {
            $this->release(300); // retry after 5 min
        }
    } catch (\Throwable $e) {
        $this->release(300);
    }
}

Templates

We store templates in code (Blade, Twig, React Email), not in the provider’s interface. Reasons: versioning via Git, browser preview without sending, testability. For complex templates with dynamic content — react-email with export to HTML via @react-email/render.

Validation and Consent

Before adding a contact to a list — double opt-in (confirmation email). Store the confirmation timestamp in your own database. Upon unsubscription — synchronously unsubscribe both at the provider and in your database. Ignoring webhook unsubscriptions is a direct path to account suspension at the provider. All processes comply with Федеральный закон № 152-ФЗ «О персональных данных».

Deliverability Monitoring and DKIM Setup

Connect provider webhooks for events: bounce (hard and soft), spam_complaint, unsubscribe. Hard bounce — immediately mark the email as invalid in your database, stop sending. Soft bounce 3 times in a row — same. Metrics: open rate, click rate, bounce rate, unsubscribe rate — review at least once a week. Our certified engineers configure alerts in Grafana/Prometheus.

DKIM configuration steps:

1. Generate a key pair (e.g., openssl genrsa -out private.key 2048).
2. Publish the public key in DNS as a TXT record for the selector (e.g., mail._domainkey.tx.example.com).
3. Provide the selector to the provider (SendGrid, Mailgun, Unisender).
4. Verify with dig TXT mail._domainkey.tx.example.com.

SPF, DKIM, DMARC must be configured separately for each stream. We use subdomains with different DNS records.

Why Is It Important to Separate Streams?

If you send a marketing campaign from the same domain as transactional emails and receive spam complaints, you risk getting the domain blocked — and users will stop receiving even order confirmations. SPF, DKIM, DMARC (Sender Policy Framework, DomainKeys Identified Mail, Domain‑based Message Authentication, Reporting and Conformance) must be configured separately for each stream. In one project, a marketing blast with 12% spam complaints blocked the transactional domain for 48 hours — we had to re‑authenticate with Google and Yandex.

What Does the Integration Scope Include?

• Audit of current communication streams and domain reputation (SPF, DKIM, DMARC)
• Provider and schema selection: transactional vs marketing traffic
• Configuration of SPF, DKIM, DMARC DNS records
• Development of email templates (HTML + dynamic content)
• Backend integration via queues and API
• Webhook setup for deliverability and complaints
• Operations documentation and team training
• Deliverability guarantee and post‑launch support

We deliver production‑ready documentation, access to monitoring dashboards, and a handover session with your engineers. Our certified engineers provide a 30‑day post‑launch health check guarantee.

Timelines and Cost

Cost is calculated individually after audit. We provide turnkey service: from analysis to production monitoring. Contact us for a free engineer consultation — we’ll evaluate your project and give accurate timelines. Over 7 years of experience in email service integration, 50+ projects implemented. Order a free audit of your current integration and receive a report with recommendations and estimated savings.