Available Autoresponder Triggers
Filipe Sá
Last Update a day ago
Autoresponders - List of Available Autoresponder Triggers
| Event | Description |
|---|---|
| Campaign - Open | This autoresponder is fired when a subscriber opens a campaign. Please note that if the user blocks remote images, the open won’t be accounted for and the autoresponder won’t be triggered. The autoresponder won’t be triggered if you choose not to track campaign stats |
| Campaign - Clicked Any Campaign Link | This autoresponder is fired when a subscriber opens a link from the email. Please note that the autoresponder won’t be triggered if you choose not to track campaign stats |
| Campaign - Clicked Specific Campaign Link | If your campaign has a wide variety of products, with this autoresponder, you can specify the link that should trigger the autoresponder. You might have sent a newsletter with cameras and smartphones, but you might want to send a follow up for cameras Please note that the autoresponder won’t be triggered if you choose not to track campaign stats |
| Search - New | Imagine a customer searches for Xbox one. You might want to send him a campaign after a day or two if he did not make any order. When creating the autoresponder, select the “New order” event in the Cancellation Events. This way the autoresponder message won’t be sent if the user searched for Xbox and then made a purchase. |
| Review - New | The autoresponder is fired when a new review is created. No matter the approval state. If you required review approval, you could use this autoresponder to send the subscriber a note pointing that out and give him extra information, like how long it might take to approve the review. |
| Review - Status Changes to Approved | This autoresponder is fired when the review status changes to approved. You might want to use it to notify the subscriber the review was approved. Please note that if you don’t require reviews approval, this autoresponder will be fired when a new review is done since the status will be ‘approved.’ |
| Review - On a Bought Product | When the subscriber makes a review on a product he has purchased |
| Product - Expected Lifespan Reached (X days before) | When the product consumption lifespan is approaching, this event will be fired X days before that happens (X is defined in the autoresponder details) More info Here => |
| Shopping Cart - New Abandoned Cart Appears | This is used to send abandoned cart email reminders. You can define the amount of time, in minutes, a shopping cart should be flagged as ‘abandoned’ since it was last updated by the customer. In this type o autoresponder, you should take advantage of the “Email & SMS Marketing – product List” widget to send the subscriber the contents of its cart. Additionally, you can also use our other widget “Email & SMS Marketing – Coupons List” to send to the subscriber a specific coupon that can only be used by him and has an expiration date |
| Customer - Signup | When a new account is created |
| Customer - Login | When the user logins to your store |
| Customer - Last Activity | This autoresponder is triggered when is not registered any activity from that user in the store. Please note that this event is based on information collected by Magento® for registered customers only. If you clear your visitor’s logs, this information will also be lost |
| Customer - Birthday | This autoresponder is fired X days before the customer birthday. The number of days is specified when the autoresponder is created. Please note that if you add a “wait” action in your autoresponder, the waiting period starts after the autoresponder is triggered (X days before the customer birthday) and not after the birthday. For example: If a customer’s birthday is 20 days from now and you want to send the first notification 15 days before, you should place in the “Number of Days” field 15, because is the day you want the first event to be fired. If you want to send the second message five days after the first email, add a new “Wait” action and specify five days. Meaning, five days after the first event, send another message. The extension will not fire more than one time per subscriber per year. Meaning this, if the subscriber has a birthday on April 2, and then changes the date to September 12, the extension will not send the campaign again on September 12, if an autoresponder of the same type was sent in April. |
| Customer - Group Changes | When the customer is moved to a new customer group |
| Customer - Attribute Value Changes | When the customer attribute changes |
| Shipment - Tracking Added To Shipment / New Ship. W/ Tracking) | This autoresponder is fired when a new shipment is created with tracking information or when new tracking information is added to the shipment. To clarify, if you create a shipment with no tracking code, the autoresponder won’t be fired up, but if you later add the track information, the autoresponder will be fired. This is useful to send the customer a message with tracking information, whether is SMS or email. Just as a reminder, you can use these tags in your message (email or SMS) and they will be converted to tracking information {{track_title}} {{track_code}} {{order_id}} |
| Shipment - New Shipment (NO tracking number) | This autoresponder is only fired if there is no tracking information attached to it |
| Order - New Order | When a new order is made |
| Order - Bought Specific Product | When the customer buys a specific product |
| Forms - New Entry | When a new entry is added to a form |
| UTM Campaigns | This autoresponder is fired when specific params are detected in the URL originating in marketing campaigns. Available params are: • Campaign (utm_campaign) • Source (utm_source) • Medium (utm_medium) • Term (utm_term) • Content (utm_content) Available conditions for each parameter: • Is • Starts With • Ends With • Contains • Does Not Contain • Wildcard • Exists You might want to add autoresponders for events like, a payment is marked as fraud. The order was put on hold/released from hold status, etc. |
| Magento® - Internal Event | This autoresponder is triggered by Magento® internal events. Example of Magento® internal codes include: customer_login, sales_order_place_after, customer_save, etc. Your dev team should help you out with this one for identification of the event you need |