Drip Integration

Migrating GrazeCart Data into Drip

If you are using the Drip + GrazeCart integration, the point at which a customer creates
an account on your GrazeCart website opens many doors to more personalized,
segmented, effective marketing.

Listed below are the steps you’ll need to take to connect Grazecart and Drip so that all
data is exchanged seamlessly as new accounts are created, new purchases are made and
website visits happen.

In addition, I’ll show you how to export your existing customers and their data out of
GrazeCart and import it into Drip.

Step 1 - Connecting Drip + GrazeCart

  • Log in to your Drip account. If you do not yet have a Drip account you can start
    with a free trial.
  • Once logged in, navigate to your 'Settings' in the bottom left corner of your Drip dashboard
    and click User Settings.
  • Scroll down to find your API token and copy the entire contents of that field to
    your clipboard.
  • Log in to your GrazeCart admin panel and click on the Apps menu > Install Drip 
  • Once Drip is installed, you can then enter your API token under the authentication tab.

Now all customer data will be freely exchanged between the two platforms. But to complete
the full connection let’s go through the process of installing the Drip javascript snippet
on your GrazeCart site.

Step 2 - Adding the Drip JavaScript Snippet

  • Navigate back to your Drip account, click on 'Settings' in the bottom left corner of
    your dashboard, and select Account.
  • Scroll Down and Expand 'Site Setup'.
  • Click on the field that contains all of the javascript code and highlight and copy it to your clipboard by hitting Command-C or Control-C.

Markup_2022-02-18_at_09.47.17.png

  • Navigate back to your GrazeCart site and click on the Settings menu.
  • Click on the Tags & Scripts option and paste the javascript code from Drip into
    the ‘Footer Scripts’ area.
  • Click Save.

Your Drip Javascript snippet is now installed on every page of your GrazeCart website,
which allows you to identify site visitors, use trigger links, and more as outlined in this
Drip help article.

Step 3 - Import Existing Customer Data into Drip

The integration between Drip and GrazeCart only adds new activity into Drip. It does
not look back and pull previous orders or the entire customer database. But, here are
the steps you can take to import it:

  • Navigate to the admin side of your GrazeCart website and click on the Settings
    menu, then select the Customers icon.
  • Scroll to the bottom of that page to the ‘Export Format’ section, select Drip from
    the drop-down menu, and hit Save.
  • Next, click on the People menu on your GrazeCart site and then click on the
    ‘Filter Customer’ option is located on the top left of the customer list.
  • Make no adjustments to the Filter option, like the (screenshot below):

Markup_on_2022-02-18_at_10_08_55.png

  • Click the Download icon to the immediate left of the Filter button. This will
    generate a .CSV file to your Downloads folder that contains all the customers in
    your GrazeCart database.
  •  Open the .CSV file
  • The column headers (across the top) on the .CSV file are exported with a name
    format that matches how these fields are added to subscriber records as part of
    the integration. Under no circumstance should any of these header fields be
    changed (i.e., first_name, schedule_id, fulfillment_name, postal_code). DO
    NOT remain or change the case on these fields at all.
  • Save this file off to your computer, naming with the date you exported it. (i.e.
    gc-export-12-1-20.csv.).
  • Log into your Drip account and click on the 'People' menu at the top left then Bulk Operations (See below).

Markup on 2023-08-14 at 08:38:34.png

  • Then, Click on the Bulk Operation Button, and then Select Upload a List of
    People and hit “Begin.”
  • On the next screen, select the file you just saved to your computer for upload.
  • Then you’ll see this Import preview screen:

Markup_on_2022-02-18_at_09_59_45.png

  • Leave the “Treat the first row in your file as headers” radio button toggled to On.
    Do not change it, but notice above the names that headers are correct. These
    headers will become custom fields for each person’s subscriber record in Drip.
    Lastly, Click Next.
  • On the next page, you have the opportunity to start automation in Drip or apply some segmentation. The only thing I recommend that you do is select Apply a Tag from the drop-down menu and type in a tag name like GrazeCart Import-Date of Import. That way you’ll always be able to identify this list of people. This is a habit I recommend you repeat with any future imports. Here’s an example:

Markup_on_2022-02-18_at_10_01_39.png

  • Hit Next and proceed to the final screen where you will complete the import by
    immediately importing or scheduling at a later time. Just choose Immediately.

After a few minutes, all of your customers from GrazeCart, and their data, will be in
Drip. You’ll be able to use that information to send specific Deadline reminders based
on schedule_id, pickup name, fulfillment_id, etc. in your newsletter among other
things.

Additional Considerations:

Finally, here are a few final notes on common questions & mistakes we encounter with email marketing integrations.

  • You can also migrate subscribers from old email service providers (ESPs) like
    MailChimp, ConstantContact, etc., and you should, and then close them down.
  • Using two Email Service Providers is strongly discouraged.
  • ***Critically Important*** Just keep in mind that if you import a different .CSV
    file with the same headers fields that you’ve already imported for a subscriber,
    you will OVERWRITE AND DELETE information in the custom field assigned
    to that header. So, if you uploaded your GrazeCart file which has first_name
    filled with a name (i.e., Stephanie) and you import a new file that also has a
    first_name header it will overwrite whatever is already in Drip with what is on
    the new file even if that field is empty in the new file.
  • We would recommend simply uploading the email address column from your old
    ESP. So, you would be uploading a CSV file with only 1 total column with a
    header field at the top that you must title email. (NOTHING different...not
    Email, not email address, not email_address). Lastly, at the point, you can add 
    automation along with your import similar to when we added “GrazeCart Import
    - Date” above. You will want to select “Set a Custom field value’ from the drop-down menu and then choose to set the newsletter_recipient field to Yes. This will add a person to your newsletter and matches the field that comes across withGrazeCart.
  • Drip support is a great service with online chat to answer specific questions about
    migrating from other ESPs

Events and Custom Fields

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

 

 

 

Was this article helpful?
8 out of 8 found this helpful