User Manual

Custom Dynamic Content

Custom Dynamic Content allows you to enable deep personalization in your customer communications. It can support use cases such as:

  • Providing the weather for a given zip code (e.g. Sunny and 55 degrees)
  • Providing cross-sell recommendations for a given product purchased (e.g. “Customers Also Bought”)
  • Dynamic pricing engines
  • Pulling content from your CMS

We configure Custom Dynamic Content on a case-by-case basis. It requires Drip’s engineering team to set up and we can not configure it for purely sandbox/playground use cases.

To work with Custom Dynamic Content, you'll need to you to answer the following questions.

    1. If you have more than one Drip Account, which Drip Account ID are you requesting Custom Dynamic Content for?
    2. What fields do you need passed to your Custom Dynamic Content endpoint? In the Weather example in our API docs, we pass a person's Custom Field of zipcode, but we can pass any Custom Field or Property from the Person. Or you could request that specific event properties of a certain type of Drip Event (e.g. “Checkout created” with an event property of zipcode = 55401) be passed. 

    3. What is the URL endpoint Drip should hit to retrieve your Custom Dynamic Content? For example,

    4. What Liquid shortcode would you like to use in your Drip emails to access your Custom Dynamic Content? This must follow the syntax my.<insert name here>. In the Weather example, {{ }} will pull in the “summary” value from this endpoint payload:

  "apparentTemperature": 51.57,
  "cloudCover": 0.48,
  "dewPoint": 43.6,
  "humidity": 0.74,
  "icon": "partly-cloudy-night",
  "ozone": 295.5,
  "pressure": 1020.55,
  "summary": "Partly Cloudy",
  "temperature": 51.57,
  "time": 1541697515,
  "visibility": 8.52,
  "windBearing": 67,
  "windGust": 3.78,
  "windSpeed": 3.58


The format in which we pass parameters to your endpoint; they are described in the Parameters section of our API Docs.