Drip supports 'Events' which are time or trigger-based actions you can use for advanced automation and segmentation in your email marketing. Drip also has a concept of 'Custom-Fields' which are updated in a similar way but are primarily used to store helpful information about your subscriber.
In this article, we give you a full breakdown of the Events and Custom Fields GrazeCart sends to Drip.
Key Events Created by Drip Based on GrazeCart Actions
| GrazeCart Action | Drip Occurrence |
|
Someone creates an account on GC Site |
“Created an account” event sent to Drip Suggested use case: Use this event to trigger an onboarding workflow to help convert them and nurture with behavior-based evergreen content and pitches |
| Someone places their 1st order ever (the previous order_total was = 0) |
“Confirmed first order” event sent to Drip, and tag of “Buyer” sent to Drip Suggested use case: Use this event to trigger a new buyer workflow nurturing workflow to automate asking for google review, monitor future buying progress, and automate a win-back campaign for those who don’t keep buying |
| Someone places 2nd or more order ever (the previous order_total was 1 or >) | “Confirmed order” event sent to Drip Suggested use case: Use to trigger a goal in a workflow that should pull the subscriber from being pitched with more emails |
| Product is part of a processed sale | “Purchased product” event and Tag sent to Drip for each product in final cart Suggested use case: Use to trigger a goal in a workflow that should pull the subscriber from being pitched with more emails or use in workflow decision before pitching a product |
| Credit is added to someone’s GC account | “Credit issued” event sent to Drip |
| Order is confirmed on Admin side and CONFIRMATION EMAIL IS NOT SENT | KEY EVENTS ABOVE are NOT sent to Drip |
| Order is confirmed on Admin side and CONFIRMATION EMAIL IS SENT | ALL KEY EVENTS ABOVE are sent to Drip |
| Order is marked “Completed” on the GC side |
“First order received” event is sent to Drip Suggested use case: Move a user forward in a new buyer workflow as this indicates the order has likely been delivered |
| Customer hits the Checkout page | “Initiated checkout” event is sent to Drip |
| Customer adds an item to their online cart |
“Started cart” event is sent to Drip Suggested use case: Trigger a Cart Abandonment workflow |
| Customer places Subscribe & Save order | “New Subscription” event is sent to Drip Subscription_status updated to active |
| Customer cancels Subscribe and Save order |
“Canceled subscription” event sent to Drip Subscription_status updated to canceled |
Custom Fields Created in Drip Based on GrazeCart Actions
| schedule_id |
The number associated with a particular GrazeCart Schedule Suggested use case: Segment your newsletter or send specific deadline reminders per schedule |
| fulfillment_id |
The number associated with a particular GrazeCart Pickup or Delivery Location Suggested use case: Segment your newsletter or send specific deadline reminders per deliver/pickup type |
| newsletter_recipient | Adds basic segmentation to people you can send a newsletter to Suggested use case: Identify subscribers with the newsletter_recipient field set to “Yes” and send them newsletters. Allow them to click a trigger link that sets the field to “No” to stop receiving newsletters without totally unsubscribing |
| order_count |
Indication of # of orders a subscriber has placed Suggested use case: When that field reaches a certain number, send an email to them acknowledging their loyalty |