# Marketing ## Overview The Loyalty Engine doesn’t send emails, SMS, or push notifications directly. Instead, it’s designed to emit real-time event triggers (e.g., `VOUCHER_REDEEMED`, `ORDER_PLACED`) that can be consumed by your connected marketing platform (such as Klaviyo, Mailchimp or Twilio). Those platforms then handle the delivery of the communication. This approach ensures that marketing, compliance, and deliverability remain centralized in your own systems, while the Loyalty Engine focuses on capturing user actions and powering loyalty logic. ### Why this approach? * **Compliance & consent –** Marketing platforms specialize in managing opt-in/opt-out preferences and regional regulations. * **Better deliverability & analytics –** Tools like Klaviyo or Mailchimp provide advanced controls, templates, and reporting. * **Protecting sender reputation –** Keeping all emails under your own marketing infrastructure avoids deliverability risks tied to third-party senders. * **Centralized visibility –** A single system for all customer communications simplifies support and reporting. * **Industry standard design –** Decoupling data triggers from message delivery is a best practice in SaaS and e-commerce. ### How it works 1. A user takes an action (e.g., redeems a voucher). 2. The Loyalty Engine emits a real-time event. 3. Your marketing platform receives that event. 4. The marketing platform sends the corresponding email, SMS, or push notification. The articles in this section cover each marketing channel in more detail. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://kbase.whitelabel-loyalty.com/product/modules/marketing.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.