On This Page
Mailshake is a sales engagement platform that helps you to automate the process of sending personalized emails at scale, allowing you to accelerate and optimize every interaction throughout the sales process. You can easily manage and track your leads by monitoring the action on every mail that you send.
Mailshake uses an API key to identify Hevo and authorize the request for accessing account data.
An active Mailshake account from which data is to be ingested.
You are assigned the Team Administrator, Team Collaborator, or Pipeline Administrator role in Hevo to create the Pipeline.
An API key is available to authenticate Hevo on your Mailshake account.
Obtaining the API Key
You must create an API key to authenticate Hevo on your Mailshake account. The API key do not expire and can be reused for all your Pipelines.
To create the API key:
Log in to your Mailshake account.
In the left navigation pane, click Integrations, and select API from the drop-down.
In the API page, scroll down to Your Team Access.
Copy the API key and account ID and save it securely like any other password.
You have successfully obtained your API key. Use this API key for creating Hevo Pipelines.
Configuring Mailshake as a Source
Perform the following steps to configure Mailshake as the Source in your Pipeline:
Click PIPELINES in the Navigation Bar.
Click + CREATE in the Pipelines List View.
In the Select Source Type page, select Mailshake.
In the Configure your Mailshake Source page, specify the following:
Pipeline Name: A unique name for the Pipeline, not exceeding 255 characters.
API Key: The API key that you copied from your Mailshake account.
Click TEST & CONTINUE.
Proceed to configuring the data ingestion and setting up the Destination.
|Default Pipeline Frequency||Minimum Pipeline Frequency||Maximum Pipeline Frequency||Custom Frequency Range (Hrs)|
|1 Hr||1 Hr||24 Hrs||1-24|
Note: You must set the custom frequency in hours as an integer value. For example, 1, 2, 3 but not 1.5 or 1.75.
Historical Data: In the first run of the Pipeline, Hevo ingests all historical data for the Campaigns, Leads, Members, Recipients, Replies, Senders, and Sent Messages objects and loads it to the Destination.
Incremental Data: Once the historical load is complete, all new and updated records for the Clicks and Opens objects are synchronized with your Destination according to the ingestion frequency.
Schema and Primary Keys
Hevo uses the following schema to upload the records in the Destination database:
The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:
|Campaigns||Full||Contains the details of all the marketing emails sent to multiple recipients to increase sales of a product or service.|
|Clicks||Incremental||Contains the details of the recent links clicked in your campaign emails.|
|Leads||Full||Contains the details of all prospective customers.|
|Members||Full||Contains the details of all the users who have access to your Mailshake account.|
|Opens||Incremental||Contains the details of most recent emails which are opened by the recipients.|
|Recipients||Full||Contains the details of all the users who have received the campaign emails.|
|Replies||Full||Contains the details of the responses received for the emails.|
|Senders||Full||Contains the details of all the email IDs from which the campaign email has been sent.|
|Sent Messages||Full||Contains the list of the most recent emails sent to recipients during a campaign.|
Pagination: Each API response for each Mailshake object fetches one page with up to 100 records per page.
Rate Limit: Mailshake imposes a limit of a maximum of 1000 API calls per minute per account to ensure that their system remains stable for usage by all users.
Hevo currently does not support deletes. Therefore, any data deleted in the Source may continue to exist in the Destination.
Hevo does not provide you with the option to select the historical sync duration for loading historical data. All the historical data in your Mailshake account is loaded.
Refer to the following table for the list of key updates made to this page:
|Date||Release||Description of Change|