|
| 1 | +--- |
| 2 | +title: Mailmodo Destination |
| 3 | +rewrite: true |
| 4 | +id: 623a07123d307e60f268a1c2 |
| 5 | +--- |
| 6 | + |
| 7 | +[Mailmodo](https://www.mailmodo.com/) is a powerful email marketing tool focused on bringing the interactive experience via AMP framework to emails. It allows businesses to create emails with web page-like interactivity right inside the user inbox, thereby increasing engagement and conversions multi-fold. |
| 8 | + |
| 9 | + |
| 10 | +This destination is maintained by Mailmodo. For any issues with the destination, [contact the Mailmodo Support team ](mailto:[email protected]). |
| 11 | + |
| 12 | + |
| 13 | +## Getting Started |
| 14 | + |
| 15 | +{% include content/connection-modes.md %} |
| 16 | + |
| 17 | +1. From the Destinations catalog page in the Segment App, click **Add Destination**. |
| 18 | +2. Search for "Mailmodo" in the Destinations Catalog, and select the "Mailmodo" destination. |
| 19 | +3. Choose which Source should send data to the "Mailmodo" destination. |
| 20 | +4. Go to the [Mailmodo Dashboard](https://manage.mailmodo.com/app/dashboard), navigate to **Settings > API Keys**, then create a new API Key and copy the same. |
| 21 | +5. Enter the "API Key" in the "Mailmodo" destination settings in Segment. |
| 22 | + |
| 23 | + |
| 24 | +## Supported methods |
| 25 | + |
| 26 | +Mailmodo supports the following methods, as specified in the [Segment Spec](/docs/connections/spec). |
| 27 | + |
| 28 | +### Identify |
| 29 | + |
| 30 | +If you aren’t familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify) to learn about what it does. |
| 31 | + |
| 32 | +```js |
| 33 | +analytics.identify('userId12345', { |
| 34 | + firstName: 'Bob', |
| 35 | + lastName: 'Dole', |
| 36 | + |
| 37 | + company: 'Initech', |
| 38 | + employees: 234 |
| 39 | +}); |
| 40 | +``` |
| 41 | + |
| 42 | +Every time you call identify with an email address included, we will: |
| 43 | +1. First ask Mailmodo if the email exists. |
| 44 | +2. If the email doesn’t exist, then we will add the user as a Contact to the Mailmodo database and match user properties with the Segment `traits` sent in identify call payload. |
| 45 | +3. If the email exists, then we will update the user properties for the Contact against the Segment `traits` sent in identify call payload. |
| 46 | + |
| 47 | +All the [special traits](https://segment.com/docs/connections/spec/identify#traits) recognized by Segment will be translated and matched with the Mailmodo user properties for a Contact. These fields will be automatically created or mapped for a Contact in Mailmodo and will be available for personalization and advance segmentation. |
| 48 | + |
| 49 | +==Please note== |
| 50 | +==1. The email field is required. Identify calls without an email is dropped.== |
| 51 | +==2. If different email addresses are sent against same user id in identify call, then they are treated as two different contacts in Mailmodo.== |
| 52 | + |
| 53 | +### Track |
| 54 | +If you aren’t familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track) to learn about what it does. An example call would look like: |
| 55 | + |
| 56 | +```js |
| 57 | +analytics.track('Product Viewed', { |
| 58 | + product_id: '507f1f77bcf86cd799439011', |
| 59 | + name: 'Monopoly: 3rd Edition', |
| 60 | + price: 18.99, |
| 61 | + url: 'https://www.example.com/product/path', |
| 62 | + image_url: 'https://www.example.com/product/path.jpg' |
| 63 | +}); |
| 64 | +``` |
| 65 | +Segment sends `Track` calls to Mailmodo as a Custom Event. When you call track, we’ll send the event to Mailmodo with the event name and all properties that you specified. |
| 66 | + |
| 67 | +==Be sure you send an Identify call for any user who will trigger Track calls. If Mailmodo receives a Track call for an unknown userId, the call is dropped.== |
| 68 | + |
| 69 | +--- |
0 commit comments