Outfit Emails

2 Minutes to read

Print
Share
Dark
Light

Article summary

Did you find this summary helpful?

Thank you for your feedback!

Include outfits based on a defined initial item, typically post-purchase.

Outfit Emails is a machine learning-powered recommendation product designed to help retailers increase customer engagement and drive revenue through personalized outfit recommendations.

This product is typically used by retailers to send an email to customers after they’ve made a purchase. The email suggests two different outfits to demonstrate the versatility of the purchased garment. Should the customer purchase multiple items, we’d encourage you to select the highest-valued item.

To set this up, you'll also work with our creative team to ensure the images match your design and add the following HTML template to your email tool. Your email tool will need to tell us which garment to base the outfit on.

Below is some example HTML to include in your email tool.

<a href="https://dressipi-emails.com/outfits/:namespace_id/:send_id/:sku/:customer_id/link/outfit/1/slot/1">
  <img src="https://dressipi-emails.com/outfits/:namespace_id/:send_id/:sku/:customer_id/image/outfit/1/slot/1">
</a>
<a href="https://dressipi-emails.com/outfits/:namespace_id/:send_id/:sku/:customer_id/link/outfit/1/slot/2">
  <img src="https://dressipi-emails.com/outfits/:namespace_id/:send_id/:sku/:customer_id/image/outfit/1/slot/2">
</a>

<a href="https://dressipi-emails.com/outfits/:namespace_id/:send_id/:sku/:customer_id/link/outfit/2/slot/1">
  <img src="https://dressipi-emails.com/outfits/:namespace_id/:send_id/:sku/:customer_id/image/outfit/2/slot/1">
</a>
<a href="https://dressipi-emails.com/outfits/:namespace_id/:send_id/:sku/:customer_id/link/outfit/2/slot/2">
  <img src="https://dressipi-emails.com/outfits/:namespace_id/:send_id/:sku/:customer_id/image/outfit/2/slot/2">
</a>

The SKU and Send ID must be consistent for all slots in an outfit. You should pass a different Send ID for each email sent. If you're sending this as a post-purchase email you may choose to use the order id.

Slot 1 is always the garment referenced with sku

If you are based in our australia region, your domain should be au.dressipi-emails.com

Parameter	Value	Purpose
:namespace_id	string	This is the Mapp Fashion-provided identifier for your namespace
:send_id	string	This is a unique identifier for this email. For post-purchase emails, this is typically the order id.
:sku	string	This is the SKU for which to build outfits. It must be consistent for all href/srcs in this email to ensure all the items form the outfit.
:customer_id	string	This is the user identifier we generate the recommendations for. This must match the customer_id provided in your customer journey tracking and/or transaction feed.
:outfit_id	integer. either `1` or `2`	We support up to two outfits per email; use this to identify which outfit to show.
:slot_id	integer. max `6`	This is shown as `1` and `2` in the example above. The example is for an email that has two recommendations. If you wish to show more recommendations in the email, you can add additional slots. We support up to 6 recommendations per email.

FAQ

How often are the recommendations refreshed from your end?

When a customer first opens the email, we generate fresh recommendations and persist them. Every subsequent open of that email will get the same recommendations as the first time the email was opened. We use the "send ID" as part of the lookup for recommendations so it's important that each new email that is sent out to a customer has a new send ID so that new recommendations are generated for each email that is sent to the customer. The send ID can be the same between customers (if required) as we use both the send ID and customer ID to look up recommendations.

Was this article helpful?

What's Next

Security

Table of contents