Custom ESP

Follow

You can configure any ESP that supports restful APIs to enable triggered emails. 

  1. Go to Settings › Integration and locate Non-listed Email Provider.
    custom_esp_settings.png
    If this is not displayed, contact your Customer Success Manager to enable the feature. 
  2. Click Enable. 
  3. Enter the settings required by your ESP:

    1. Select the Identifier Type
      • Email: Identify customers by plain text emails 
      • External: Use a string as an identifier that your ESP can map to an email address 
    2. Select the authentication type depending on your ESP requirements 
      1. No Authentication (No Auth) - No authentication type is used. Sending any header parameters, including API keys, is optional.
      2. Basic Authentication (Basic Auth) allows users to provide the username and password associated with their HTTP endpoint when setting up their ESP. When data is sent, the Basic Auth fields are included in the header of the HTTP request.
      3. OAuth 2.0 - OAuth 2.0 requires an authentication token, which is issued by an authorization server, in order to connect to your ESP. The authentication token is checked by the receiving endpoint when accepting the HTTP request. We use Client credentials type.
    3. If you selected Basic Auth, provide the username and password that your target URL uses. 
    4. If you selected OAuth2.0, provide the following information
      1. OAuth2.0 Client ID and OAuth2.0 Client Secret (which is akin to username and password) that Dynamic Yield will use to request the authentication token from your authorization server.
      2. OAuth2 Token URL i.e. the URL of the authorization server from which Dynamic Yield will request the token.
    5. HTTP POST URL / Endpoint: This is where Dynamic Yield will send the POST request. A variable ${dyCampaignName} can be used and will be replaced with each campaign name that triggers the end point.
    6. HTTP Header Parameters: Define the header parameters which are the HTTP header settings used when sending the actual POST request. Certain endpoints may require that you include headers in your request. Common use cases for request headers include a content type specification (JSON) and authorization headers that contain your credentials with your vendor or system. For example, content type specifications have the key “Content-Type” and common values are “application/json”
  4. Verify that the request is formatted properly by going to the Test tab and sending a test email and view the server response. image5.png
  5. Click Save Settings. 

You can now use the custom ESP you defined to create triggered emails.