Automating Marketing for Crowdgames: Mindbox Integration
We built a complex, bidirectional Mindbox integration for Russia's largest board game store — enabling triggered email campaigns, abandoned cart recovery, a loyalty program, and personalized product recommendations.
Crowdgames, Russia's largest board game retailer, purchased Mindbox for email personalization, abandoned cart recovery, and product recommendations — but couldn't launch a single feature without a site integration. We designed and built it from scratch.
Connecting Mindbox to a Site With No Existing Blueprint
Project Snapshot
- Client Crowdgames
- Platform Custom Site + Mindbox
- Planned Timeline 28 days
- Actual Timeline 3 months
The Problem
Crowdgames paid for Mindbox specifically for its event-based segmentation, triggered email campaigns, loyalty program, and product recommendations — but none of these features worked without a deep integration on both the backend and frontend. No off-the-shelf module existed for their platform, and Mindbox's API was one of the most complex on the market. The client was paying for a service they couldn't use, and losing money in the process.
Diagnosis
We broke down Mindbox's requirements and found the integration needed to be bidirectional, spanning two layers:
- Frontend: a JS SDK was needed to track product and category views, cart additions, and cart changes — without slowing down page load.
- Backend: registration, login, profile edits, order creation, and order status/composition changes all had to sync with Mindbox via API in real time.
- Infrastructure: DNS/DKIM configuration was required for email deliverability, along with catalog feeds and historical data import for segmentation.
Our Approach
Since no reference architecture existed for this kind of setup — even on Mindbox's side — the technical specification had to be built from scratch, taking over a month before any code was written.
What We Built
- Frontend SDK: asynchronously loaded Mindbox JS SDK — no impact on site speed — tracking product views, cart changes, and cart clearing.
- Backend API Integration: registration, login, profile editing, order creation, and status changes — with separate logic for authenticated and guest users.
- Guest Checkout Handling: guest users are automatically registered in the database, with their discount and promo code saved to their profile.
- Reference Data Setup: 20+ order statuses, payment methods (YooKassa, Split by Yandex Pay), and a YML product feed refreshed every 2 hours.
- Historical Data Import: CSV import of past order data to enable segmentation from day one, avoiding a cold start.
- Triggered Emails: confirmation, shipping, and review-request emails tied to order status changes.
- Async Processing & Logging: most operations run asynchronously to avoid slowing the site, with logs retained for 14 days for debugging.
Challenges With Mindbox Support
The biggest obstacle wasn't technical complexity — it was support response times. A +5/+6 timezone gap meant replies came every 5–6 business hours. With no comparable prior project in their system, the technical spec alone took over a month to finalize. The project ultimately took 3 months against an initial estimate of 28 days.
The Results
A stable, fully functional integration with real-time bidirectional data sync.
The Mindbox Manager plugin is installed on-site, and every platform feature is now fully available. The complete customer journey — from product view to order status — is visible to managers in a single profile, powering the personalized campaigns, loyalty program, and recommendations the client originally paid for.