Mailjet

The Lyftron Provider for Mailjet offers the most natural way to access Mailjet data from Lyftron with ease and also enables to connect with BI, MDM & ML tools, Data warehouses, Databases and other SAAS based applications with zero code and zero infrastructure requirements. The provider wraps the complexity of accessing Mailjet data into easy-to-integrate relational fully managed ANSI Sql format. Make faster and better business decisions with Lyftron’s Mailjet data provider and automatically build your data migration pipelines in minutes, not months

The provider hides the complexity of accessing data and provides additional powerful security features, smart caching, batching, socket management, and more.

Key Features

• Comprehensive Delta load mechanism.
• Real-time access to Mailjet.
• Comprehensive full support of ANSI Sql to query data with ease.
• Collaborative query processing.

Prerequisites

The user must have credentials for Mailjet, Lyftron and your destination data warehouse, lake or database to perform the data pipeline operation with Lyftron

Step1: Setup Drip account

1.1 Create account in Mailjet and login

1.2. After Login go to -> Account and click on -> New API Key to generate Api key

Establishing a Connection with Lyftron's Quickstart Steps

Create your Mailjet connection with Lyftron by following the 5 easy steps show below:

Step2 : Login to Lyftron

Start creating your connection 

Step2.1Add your connection

Click on Connect section on the left panel →  Click on Add Connection button In the connector selection panel, search and click Mailjet for your connection 

Step2.2 Enter your connection details

In the Connection String section enter the values of the below parameters. The following connection string is required to establish Mailjet connection with Lyftron.

Profile=Mailjet.apip;ProfileSettings='User=[your_api_key];Password=[your_APISecret];'

 

Give connection name as Mailjet -> Replace “your_api_key” with Mailjet Api-key, click on test connection -> click save. If connection is not successful so, check the error

 

Key	Value	Field
Connection Name	Enter your connection details	Required
Profile	C:\profiles\Mailjet.apip	Required
User	your Mailjet < API Key >	Required
Password	your Mailjet < API Secret >	Required
Logfile**	Use the logfile option to debug your job and provide your connection name to generate the log file.  [ConnectionConfigurationPath]\Connection_name_log.tx	Optional
Verbosity**	Choose verbosity 1-5 based on the severity of debugging	Optional

** For more information, check the Lyftron logging and debugging section.

If you want more detailed information about how to establish a connection with Lyftron, click on Lyftron Connection Quick Start guide.

Test your connection

Once you are done entering your connection details, simply click on the Test Connection button to test the connectivity. In case your connection fails, add Logfile and Verbosity parameters and check the Lyftron logging and debugging section, to debug the error. 

Save your connection

Hurray! Now you have successfully connected with the Lyftron Mailjet connector and can utilize the connector to Extract, Warehouse, Analyze, Visualize and Share your data.

 

Step3 : Normalize 

Create data source

After establishing connection, datasource metadata import is needed and for that Lyftron automatically normalize your API & different SQL dialects data into ANSI SQL format and also gives you API sources into simple, code less out of the box data model.

3.1 Click on Normalize section from the left panel -> Click on Add Data Source button, Enter data source name -> Choose  Mailjet from the existing connection list  -> Click next

3.2 Choose the table you want to import and  -> Click Create

 

Data Model 

The provider models the data in APIs into a list of tables that can be queried using standard SQL statements.

Generally, querying APIs tables is the same as querying a table in a relational database. Sometimes there are special cases, for example, including a certain column in the WHERE clause might be required to get data for certain columns in the table. This is typically needed for situations where a separate request must be made for each row to get certain columns.