# Trigger Rules ### Trigger Rules An event that starts an automation flow, based on customer events and cart activity The Trigger enables users to verify whether customer contacts that meet the trigger event criteria will enter automation. This tool ensures your automation is correctly configured by demonstrating whether the trigger and audience filters are operating as expected. ### Types of Trigger Conditions > Order total > > Language > > Currency > > User roles > > Category Name > > Category IDs > > Product name > > Product ID's > > Variant ID's > > Buyer Accepts Marketing > > Geolocation > > Placed order ### Use Case > #### 1. **Order Total** > > * **Use Case:** Trigger an automation for customers whose order total meets a certain threshold (e.g., > $100). This could be useful to send personalized thank-you emails, loyalty rewards, or special discounts to high-spending customers to encourage future purchases. > > #### 2. **Language** > > * **Use Case:** Tailor emails and content in the customer’s preferred language based on their browser or previous interactions. This ensures a personalized experience and can help boost engagement and conversion rates. > > #### 3. **Currency** > > * **Use Case:** Trigger region-specific pricing or promotions. For example, if a customer is browsing in GBP, show them offers that are most relevant to the UK or offer free shipping for orders in that region. > > #### 4. **User Roles** > > * **Use Case:** Segment emails based on user roles such as “New Customer,” “VIP,” or “Wholesale.” For instance, send VIP users exclusive offers or reward programs, while new customers could receive a welcome discount. > > #### 5. **Category Name** > > * **Use Case:** Trigger specific automations based on the product category a customer interacts with. For example, customers browsing "Electronics" could receive recommendations for complementary products like chargers or cases. > > #### 6. **Category IDs** > > * **Use Case:** Automate follow-up emails for customers who have purchased items from certain categories (by ID). If a customer purchases from a "Skincare" category, send skincare-related tips, product recommendations, or refill reminders. > > #### 7. **Product Name** > > * **Use Case:** Create targeted post-purchase follow-ups or pre purchase automations for specific products. For example, after purchasing a "Yoga Mat," the customer could be sent offers for yoga accessories or a wellness subscription plan. > #### 8. **Product ID** > > * **Use Case:** Create targeted post-purchase follow-ups or pre purchase automations for specific products. For example, after purchasing a "Bluetooth Speaker," the customer could be sent offers for related accessories like speaker stands or headphones. > > #### 9. Variant ID > > * **Use Case:** Tailor post-purchase emails based on the specific variant a customer purchased. For example, if a customer buys a "Red T-shirt" in a specific size, they could receive offers for similar shirts in different colors or matching accessories. > > #### 10. Buyer Accepts Marketing > > * **Use Case:** Send marketing emails or exclusive offers only to customers who have opted in for communications. For example, after a customer accepts marketing, you could send them personalized discounts, promotions, or updates about new products. > > #### 11. **Geolocation** > > * **Use Case:** Personalize marketing messages based on the customer's location. For instance, offer discounts on warm clothing to customers in colder regions or showcase products that are popular in their area. > > #### 12. **Placed Order** > > * **Use Case:** Trigger post-purchase workflows, such as thank-you emails, product review requests, or loyalty reward notifications. This can enhance customer satisfaction and foster repeat purchases. **Order total** Triggers emails based on the total amount of a customer's order.

#### Language Sends emails in the customer's preferred language

#### Currency Sends emails in the user's preferred currency into the automation

#### User Roles Administrators or staff members of the store, allowing them to test and manage automated workflows.

#### Category Name Sends specific emails based on the product category the customer interacted with.

#### Category IDs Sends specific emails based on the product category IDs the customer interacted with.

#### Product names Triggers emails for certain product names a customer views or buys.

#### Product IDs Triggers emails for certain product IDs a customer views or buys.

#### Variant ID Triggers emails based on the product variant the customer interacted with, such as selecting a particular size, color, or style.

#### Buyer Accept marketing Sends emails only if the customer has agreed to receive marketing emails.

#### Geolocation Uses the customer's location to send an email.

#### Placed order Triggers a follow-up email once a customer completes a purchase.

--- # 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://help.retainful.com/automations/automation-workflow-settings/trigger-rules.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.