Download the PHP package artlounge/magento2-bento without Composer
On this page you can find all versions of the php package artlounge/magento2-bento. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package magento2-bento
Bento Integration for Magento 2
Connect your Magento 2 store with Bento email marketing using reliable, non-blocking async event queues.
What It Does
This package automatically sends customer activity from your Magento store to Bento for email marketing automation. Events are processed through RabbitMQ queues so they never slow down your store.
Server-Side Events
| Magento Event | Bento Event | Trigger |
|---|---|---|
| Order Placed | $purchase |
Customer completes checkout |
| Order Shipped | $OrderShipped |
Shipment created |
| Order Refunded | $OrderRefunded |
Credit memo created |
| Customer Registered | $Subscriber |
New account created |
| Newsletter Subscribe | $subscribe |
Email subscribed |
| Newsletter Unsubscribe | $unsubscribe |
Email unsubscribed |
| Abandoned Cart | $cart_abandoned |
Cart idle for configured time |
Client-Side Events
| Event | Bento Event | Trigger |
|---|---|---|
| Product View | $view |
Customer views product page |
| Add to Cart | $addToCart |
Customer adds item to cart |
| Checkout Started | $checkoutStarted |
Customer enters checkout |
| Purchase (fallback) | $purchase |
Success page (deduplicated with server-side) |
Requirements
- PHP 8.1+
- Magento 2.4.4+
- RabbitMQ 3.8+ (or Magento database queue fallback)
- Aligent Async Events ^3.0
- Bento account with Site UUID, Publishable Key, and Secret Key
Installation
Configuration
Navigate to Stores > Configuration > Art Lounge > Bento Integration in Magento Admin.
Required Settings
| Setting | Path | Description |
|---|---|---|
| Enable | General > Enable | Master on/off switch |
| Site UUID | General > Site UUID | Your Bento site identifier |
| Publishable Key | General > Publishable Key | Client-side API key |
| Secret Key | General > Secret Key | Server-side API key (stored encrypted) |
Optional Settings
- Orders — Toggle tracking for placed, shipped, cancelled, refunded orders. Configure tax inclusion and currency multiplier.
- Customers — Toggle tracking for customer creation/updates. Add default tags.
- Newsletter — Toggle subscribe/unsubscribe tracking.
- Abandoned Cart — Set delay (minutes), minimum cart value, and whether email is required.
Test Your Connection
After entering your API keys, click Test Connection in the admin config to verify your credentials.
Queue Consumers
Start the async event consumers (production environments should use Supervisor):
Check queue status:
CLI Commands
Reliability Features
- Outbox fallback — If RabbitMQ is unreachable, events are stored in a database outbox and retried automatically when the broker recovers.
- Dead-letter replay — Events that fail after max retries can be replayed via CLI or monitored by cron.
- Smart retry prevention — Permanent failures (400, 401, 403) are not retried; transient failures (429, 5xx, network errors) are retried with exponential backoff.
- Abandoned cart detection — Configurable delay, minimum value, and HMAC-signed recovery links.
- Event deduplication — All events include unique keys to prevent duplicate processing.
Varnish / Full Page Cache Compatibility
All client-side tracking is Varnish-safe. Templates render no user-specific data in HTML — all customer identification happens via Magento's private content AJAX system (customerData).
Architecture
See docs/architecture.md for a detailed walkthrough of how the three modules work together, the event flow, retry system, and design decisions.
Contributing
See CONTRIBUTING.md for development setup, running tests, and pull request guidelines.
License
MIT
All versions of magento2-bento with dependencies
magento/framework Version *
magento/module-store Version *
magento/module-config Version *
magento/module-backend Version *
magento/module-sales Version *
magento/module-customer Version *
magento/module-newsletter Version *
magento/module-quote Version *
magento/module-catalog Version *
magento/module-checkout Version *
aligent/async-events Version ^3.0
ramsey/uuid Version ^4.0