### [Guide to Build Custom Triggers for Shopify](https://www.pushengage.com/documentation/guide-to-build-custom-triggers-for-shopify/) **Published:** July 23, 2026 **Author:** Ayushi Dubey **Content:** Trigger Campaigns are automated push notifications that fire based on what a shopper does, such as abandoning a cart, browsing a product, a price dropping, or an item coming back in stock. A trigger listens for a specific event and sends the notification only when that event happens for a subscriber. This guide shows you how to create, configure, and activate a triggered campaign in the PushEngage Shopify app. ### Before You Start - Install and connect PushEngage on your Shopify store before you create a trigger. - Confirm your plan includes Triggered Campaigns. If it does not, you see an upgrade prompt when you open the builder. - Know which trigger type you need. Cart Abandonment and Browse Abandonment work automatically once active, because their start and stop events are built in. Custom, Price Drop, and Back in Stock triggers need your store to send PushEngage an event, which you set up in the last section. ### How Triggers Work A trigger has a start event and an optional stop event. When the start event fires for a subscriber, the first notification goes out. If you add more notifications, each later one follows its own delay until the stop event fires and cancels the rest. You choose a trigger type first, and each type comes pre-configured for its use case. TypeWhat it doesStart / stop eventCart AbandonmentReminds shoppers about items left in their cart.Starts on add-to-cart, stops on checkout (built in).Browse AbandonmentRe-engages visitors who viewed products but did not add to cart.Starts on browse, stops on add-to-cart (built in).Price Drop AlertAlerts subscribers when a viewed product drops in price by your threshold.You send a price-drop alert event.Back in Stock AlertNotifies subscribers when an out-of-stock item is restocked.You send an inventory alert event.Custom Trigger CampaignSends a notification when any custom event fires from your site, such as `user.signed_up`.You define the start and optional stop event names.### Create a Triggered Campaign 1. Go to **Web Push ยป Campaigns** and select **Trigger Campaigns** from the campaign-type strip. 2. Click **Create** and choose a trigger type. 3. Enter a campaign name at the top of the builder. PushEngage checks the name against your existing campaigns when you click away from the field and warns you if it is already taken. 4. Build your notifications on the **Content** step. 5. Set your rules and limits on the **Settings** step. 6. Click **Save draft** to finish later, or **Activate** to make the trigger live. ![](https://www.pushengage.com/wp-content/uploads/2026/07/image-4-1400x475.png) #### Write the notification sequence On the **Content** step, the first notification fires when the trigger event occurs. If you add more steps, each later step follows its own delay until the stop event fires. New notifications come pre-filled with placeholder copy for the type you chose, so you edit rather than start from scratch. FieldNotesLimitNotification titleRequired. Supports variables like `{{productname}}` and `{{price}}`.85 charactersNotification messageRequired.135 charactersNotification URLRequired. Must be a valid http or https URL. Use `{{notificationurl}}` or `{{link}}` for alerts.1600 charactersNotification imageOptional small icon image.Large imageOptional. Required if you enable it.Action buttonsOptional. Up to two buttons, each with a label and URL.Label 12, URL 256Any `{{variable}}` you add to a notification becomes a field PushEngage expects in the event data you send from your store. ![](https://www.pushengage.com/wp-content/uploads/2026/07/image-5-1400x861.png) #### Configure rules and limits On the **Settings** step, the controls change with the trigger type. For Custom, Cart, and Browse triggers, set the trigger rules. Use **START this campaign IF** for the event name that begins the sequence, and **STOP this campaign IF** for the event that cancels remaining steps. Cart and Browse events are fixed and cannot be edited. For a Custom trigger, enter your own event name. For Price Drop and Back in Stock triggers, set **Campaign expiry (days)** between 1 and 365 to control how long PushEngage monitors the product for each subscriber. For Price Drop, also pick a **Threshold type** of percentage or absolute amount, then enter the **Drop by** value. The alert fires when the price drops by at least that amount. Use **Frequency capping** to stop a subscriber from re-entering the trigger too often. Set a **Daily notification limit** (1 to 200) or a **Weekly notification limit** (1 to 2000), or leave both blank for no cap. Enable **UTM parameters** to append tracking tags to the notification URL, and enable **Goal tracking** to attribute conversions with a goal name of 1 to 64 characters using letters, numbers, hyphens, and underscores. ![](https://www.pushengage.com/wp-content/uploads/2026/07/image-6-1400x711.png) ### Send the Trigger Event From Your Store Cart and Browse abandonment triggers work as soon as they are active. Custom, Price Drop, and Back in Stock triggers need your store to tell PushEngage when the event happens. In the builder footer, click **Integration code** to open the code modal, which generates a copy-paste snippet in Promise or Callback form. ![](https://www.pushengage.com/wp-content/uploads/2026/07/image-7-1343x1024.png) ### Frequently Asked Questions #### Why is my custom trigger not firing? Check that the `event_name` in your integration code exactly matches the START this campaign IF value in the builder, and that the campaign is Active rather than a draft. A mismatch or a draft campaign is the most common reason a custom trigger stays silent. #### Why is my notification missing product details? Every `{{variable}}` in your notification content needs a matching key in the event data or alert payload you send. When a key is missing, PushEngage renders that spot blank, so confirm your payload includes every variable you used. #### How do I stop sending too many notifications to the same shopper? Set a daily or weekly frequency cap on the Settings step. The cap prevents the same subscriber from re-entering the trigger within the window you choose. #### Why will the builder not let me save? The builder highlights the first field that fails validation. Common causes are a blank title, message, or URL, a URL that is not http or https, or a delay of zero on a later step. If you run into any issues, please feel free to [contact us](https://www.pushengage.com/contact-us/?utm_source=website&utm_medium=helpdocs&utm_campaign=contact-us) by clicking here. Our support team will be able to help you. **Doc Categories:** Shopify, Web Push ---