Mailmodo 0ff833fb

Mailmodo Support

Stay updated on the status of all your company's support tickets.

Raise a Ticket here

Customer portal

 removes the need to build a connection to the Mailmodo API yourself. Anytime you Identify a person on your site, they’ll be added to a Mailmodo contact database or, if they’re already on it, their traits will be updated based on your Segment traits. Similarly, when a user performs any activity on your site, you can use Segment Track calls to push those activities to Mailmodo. You won’t need to do any additional development to configure any of these features.

Once the identify and track data is synced to Mailmodo, you can 

 and send them personalized campaigns at scale.

Search for “Mailmodo” in the Destinations Catalog, and select the 

 should send data to the Mailmodo destination.

, then create a new API and copy the same.

 in the Mailmodo destination settings in Segment.

Mailmodo supports the following methods, as specified in the 

If you aren’t familiar with the Segment Spec, take a look at the 

 to learn about what it does. An example call would look like:

Anushka Agnihotri

Every time you call identify with an email address included, we will:

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.  

If the email exists, then we will update the user properties for the Contact against the Segment traits sent in identify call payload.  

 recognized by Segment will be translated and matched with the Mailmodo accepted user properties for a Contact. These fields will be automatically created in Mailmodo and will be available for personalization and advanced segmentation. 

Please note the following things:
1. The email field is required. Identify calls without an email are dropped.
2. If different email addresses are sent against the same user id in identify call, then they are treated as two different contacts in Mailmodo. 

 to learn about what it does. An example call would look like this:

Segment sends Track calls to Mailmodo as a Custom Event. When you call  

, we’ll send the event to Mailmodo with the event name and all properties that you specified.

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.

Segment lets you change these destination settings from the Segment app without having to touch any code.

How will the traits of a user in Segment be integrated into Mailmodo?

Any new property receive will have the same name as Segment, and it's data type will be inferred from the value of the property

Q) How to sync historical data from Segment?

A) Mailmodo destination supports cloud-mode data which enables customers to sync historical data from Segment into Mailmodo. To import historical data, you need to perform the following:

 for syncing or replaying historical data to Mailmodo Destination. To learn more about replaying, 

 to delete existing data from Segment if required.  

If you face any problems, reach out to us at 

Integration with Segment CDP (as Destination)

 is a customer data platform that helps you collect, clean, and activate your customer data. Using Mailmodo Source allows you to export the campaign activity events generated after your contacts engage with the Mailmodo campaigns to Segment for further processing and analysis

Enhance your team's engagement and marketing strategies by consolidating all customer data in a single location.

Merge the data from Mailmodo with the existing event data integrated into Segment.

Utilize Mailmodo Source to seamlessly transmit these events to your desired destinations or data repositories.

Obtain a comprehensive report on your engagement and marketing endeavors, capturing the complete picture.

A step-by-step guide to setup Mailmodo Source for Segment

Search for “Mailmodo” in the Sources Catalog, select click Mailmodo, and click Add Source.

On the next screen, give the Source a nickname and configure any other settings.

The nickname is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The nickname can be anything, but we recommend using something that reflects the source itself and distinguishes it amongst your environments (e.g. Mailmodo_Campaigns).

Copy the Write key from the Segment UI. You will need to input this key on the Mailmodo integration page.

Look for the Segment Source option on the Mailmodo Integration page. Click on the "Click to configure" option

Enter your Write Key copied from Step 1 and select a Segment Region

Click on "Test and Save" to complete the setup. 

If the provided write key is valid, Mailmodo will now act as a Segment source. To confirm the same, you can check the source debugger within Segment to see if the event arrived. 

Now that your Source is set up, you can connect it with Destinations.

Log in to your downstream tools and make sure that the events are populating in your Debugger and that they contain all of the properties you expect. If something isn’t working as you expect, see the Destination docs for troubleshooting.

If there are problems with how the events arrive at Segment, 

The following table lists events that Mailmodo sends to Segment. These events show up as tables in your Warehouse and as regular events in your other Destinations.

Mailmodo will send campaign activity data only for those contacts for whom we have received identify calls previously from Segment.

This table lists event-specific properties Mailmodo sends to Segment:

The Mailmodo Source works only when you also connect Mailmodo as a Destination. With the Mailmodo Destination, you can use Segment to send identify and track calls to Mailmodo so you can target customers with interactive emails. 

Want to start sending data to Mailmodo? Learn how by reading the 

Segment.io (CDP)

Integration with Segment CDP (as Destination)

Integration with Segment CDP (as Source)