Webhooks is for communicating in the reverse direction. When something happens in MarketingPlatform, like an Email Campaign being opened, a Contact unsubscribing and other actions you might find relevant, we can contact your system via a webhook. Where, when and how is totally up to you.

MarketingPlatform will send a HTTP POST request to the provided URL. The Webhook will then attempt to resend the request up to five times until it receives a successful response code (200 OK).

You can set up a webhook by following the guide below:

Setting up a Webhook

Each webhook must be given a name – this is for reference when working with a specific webhook in the platform.

You need to enter the URL which we will contact when the chosen action happens.

You can opt to write a token which we will merge in the HTTP request to access the URL or use Basic Auth to grant access to the URL.

• Token-based authentication works by ensuring that each request to a server is accompanied by a signed token which the server verifies for authenticity and only then responds to the request.
• Basic Authentication (Basic Auth) allows users to provide the username and password associated with your HTTP endpoint when setting up a webhook

Only one of either Verification Token or Basic Auth can be used at a time, but one must be included.

Before saving it is advised to test your Connection to see if contact between the systems has been established.

Headers are your way of sending additional information with every message to be read by the receiving end. A maximum of ten headers can be set up per webhook.

Your overview for existing Webhooks

Your overview of existing Webhooks allows you to deactivate and reactivate Webhooks, edit them and so forth.

If you click “Show Logs” you will be able to see the latest sent messages from the system.

This includes a timestamp, payload with information such as Contact and List id and a Response that can either be Sent or Failed.

The post Webhooks appeared first on MarketingPlatform - Dansk Email Marketing Software.

The post Playable Integration appeared first on MarketingPlatform - Dansk Email Marketing Software.

Before you begin setting up the integration with MarketingPlatform you should have created an API user in Smartweb. You will need to use this API username and password to set up the integration in MarketingPlatform. 

In Smartweb, go to the Control Panel ->Administrative users -> Click “Create admin user account”, which you will find in the upper right-hand side. Then you should follow the steps to create an admin user account – if you need help doing so you can contact Smartweb support directly. 

You need to use the following values when creating the Connector in MarketingPlatform:

The first step is to create a Connector. You find Connector under the “Integration” tab in the MarketingPlatform system. Next, you will need to do the following:

• Name your Connector.
• Select contact list.
• Choose Wannafind (and NOT SmartWeb) from the list of the systems on the right .
• Insert your Username and Password. An additional button called “+Add a second endpoint’’ will appear.
• Click on “+Add a second endpoint” button and the first field will be auto-filled with “Orders + Order items”.
• Next to this field, there are two additional fields. Just enter the words Username and Email here.

• Click “Test Connection” to see if the connection works.
• If this works as planned, click the “Save and Continue Mapping” button.
• Next, all fields must be merged together:
  • The first field is always “email” or “mobile”.
  • Then, if the field does not already exist in the contact list which you have previously selected, use “create field mapped with name and type from connected system”.

• For orders, unlike other fields, start on the left-hand side and select “Create OTM field from connected system”. As a result, the button “Map One to Many” appears on the left. Follow these steps:
  • Click on the “Map One-To-Many” button. Then you must build the One-to-Many/order structure.
  • Name it, for example, “Orders”
  • Then drag “Orders” from the right to the left.
  • It is important that you mark/click on ‘orders’ to activate it and to be able to build the rest of the structure.
  • From  “Orders” expand with the following fields: ID, CurrencyID, CustomerID, Status, Total, DateDelivered, TrackingCode, DateUpdated, DateSent, Origin, and orderLines. These fields should all be dragged from the right-hand side and into the order structure on the left.

• • “OrderLines” needs a relationship (parent). Go to the “Properties” tab in the top right and set “parent” to “Id”

• • A new structure needs to be built from “OrderLines”. Mark/click on “OrderLines” to activate it. From here, you need to drag over the following fields: OrderID, ProductID, VariantID, Amount, ProductTitle, VariantTitle, Discount, Price, StockStatus, TrackingCode

• • Click “OK” in the bottom right-hand corner.
  • You should now go to “Advanced Import Settings”.
  • Marked as ‘Confirmed’ must stay as “Confirmed”.
  • Subscribed Status must stay “Subscribed”.
  • In “Overwrite Existing Details” select “Add new contacts, and update existing”. The rest should not be selected.
  • In “Autoresponders” select “Yes, add contacts to autoresponders” if you have set up Autoresponders in the system.

• In “Filter content where” 
  • Select “Match any rule (OR condition)”
  • In the dropdown menu “The webservice items in this connector will be filtered by this rule” select “Newsletter”. Here, respectively, “Bool” and “True” need to be selected. This means that we will only retrieve the contacts where there is permission to do so.
  • Save and close.

You have now set up your SmartWeb Connector.

The post SmartWeb Integration appeared first on MarketingPlatform - Dansk Email Marketing Software.

The setup includes three stages:

1. You will first need to create a design for the product recommendation in Hello Retail platform.
2. Then you will create a campaign that sets the conditions for the content of the product recommendations.
3. Lastly, you will input a piece of code from Hello Retail into your newsletter in MarketingPlatform.

1: Create a design in Hello Retail

The first thing you need to do is to create a design for the product recommendations. Specifically, you will create a design for a single “tile” with a product recommendation containing a picture, title, and price. You’ll then insert an amount of these tiles into your newsletter depending on how many product recommendations you wish to include in the newsletter. Let’s get started with the design.

Log in to your Hello Retail account and go to Newsletter Content -> Designs and click Create a new design.

Then you’ll see a list of designs to start from. In this guide, we choose Simple which is a picture over the title, previous price, and current price.

On the next page, you can customize the design to make it fit the design of your shop and newsletter. First, you’ll give the design a name, and then you can change the size, font, font size, colors, and the text and color of the buy button.

If you know basic HTML, you can edit the design code directly, if you click “Edit source”. 

Since the MarketingPlatform newsletter by default is 600 pixels wide, we will create a 290×290 product recommendation to make them fit nicely side by side in the newsletter.

When you like the design, click Create.

After clicking Create you’ll see an example of the design with your products, and you can fine-tune the design to make it perfect. Remember to click Save if you made changes you want to keep.

2: Create a campaign

After creating the design, you need to create a campaign – this will define the conditions for how Hello Retail automates the product recommendations. There are three campaign modes, and you can read more about them here. The best solution in the integration between Hello Retail and MarketingPlatform is the Rolling campaign, where you only have to do the setup once and everything will run automatically from there. 

You create a new campaign in Hello Retail by going to Newsletter content -> Rolling campaigns and click Create new rolling campaign.

On the next page, you give the campaign a name for your own reference later. Then you pick the newly created design and choose the number of product recommendations you wish to include in your newsletter – here we have chosen 4. Lastly, you need to set the unlock frequency. This set the number of days where the product recommendations are locked so that your customer will see the same products when returning to the same newsletter a few days later – but will see new products in the next newsletter, without you having to change anything in the meantime. You need to choose the number of days that fit with the frequency of your newsletter, for example 7 days.

When done, click Create.

After you have created the campaign, you’ll be presented with more options for how you want to configure the campaign. Out of the box, the campaign will create personalized product recommendations ready to be sent out, but you can tune how Hello Retail pick out the products or add fixed products you wish everyone will see. You can read more about the detailed settings here.

If you are satisfied with the settings, click Code snippet.

This code represents the 4 product recommendations that you have configured using the design you created, and you will paste this into your MarketingPlatform newsletter. Select the full code snippet and copy it to your clipboard.

3: Input the code into your newsletter

The last thing to do is to insert the code snippet into your newsletter in MarketingPlatform. You might have an existing template already or you need to create a new one. You can read all about how to do that here. We continue under the assumption that you already have a template.

When editing your template you have to insert a grid element where you want the product recommendations to be placed. Drag it into position as shown below.

Then you drag an HTML element into the grid element.

Click “Insert your HTML” to see the editing options for the HTML element. Then you’ll see a box to the right where you can paste the code you copied from Hello Retail. Then click Update HTML.

After clicking Update HTML you’ll see the newsletter update with your product recommendations, as shown below.

Now you’re ready to send out the newsletter and every recipient will be presented with personalized product recommendations based on their behavior on your site.

Optimize the product recommendations

Hello Retail knows a customer’s behavior on your shop by the use of a unique cookie, but Hello Retail doesn’t necessarily know that customer’s email address – and the email address is the identifier in the newsletter. The first time the customer clicks a product recommendation, the customer’s email address will be coupled to the cookie, and from then on the product recommendations will be generated based on the behavior of the customer. So, the product recommendations will become more personalized as the customers interact with your newsletter.

You can ensure a faster identification by helping Hello Retail coupling the email address to the cookie no matter what they click in the newsletter. You do this by adding a small piece of code to other links in the newsletter – for example, a link to the frontpage in the head banner, as many have at the top of the newsletter. The code is   ?aw:userEmail=%%emailaddress%%

that you add to the end of existing links. So, a link will change from  

https://www.dinshop.com

to

https://www.dinshop.com?aw:userEmail=%%emailaddress%%

When the customer clicks that link and is directed to your frontpage, Hello Retail will instantly couple the cookie and email address. From here on you and the customer will benefit from personalized product recommendations in every following newsletter.

The post Integrate Hello Retail with MarketingPlatform appeared first on MarketingPlatform - Dansk Email Marketing Software.

With the App integration to Firebase, it is possible to output content as notifications on mobile devices. Do you want to target customers who have not shown activity on your Email Campaigns, send a happy birthday message or offer free shipping for those who have your app installed? 

You will find the Notification output under App Integrations in the left-side Menu. We integrate with Firebase to let you segment your Profiles in MarketingPlatform and target them with App Notifications through Firebase. We plan to continue to add more options for integrating MarketingPlatform with your app center.

Get an edge over your competition with Notifications

Firebase allows you to create a Notification Campaign and target your Profiles that you synchronize between MarketingPlatform and Firebase.

It requires you to use Firebase with your mobile application.

How the notification will look like will depend on the device and notification setting of your customer.

Utilizing Notifications as an output channel is a great way to

• Target inactive Profiles to win them back.

• Reward some of your best customers with targeted messages or if their favorite item is back in stock.

• Get an edge over your competitors on special occasions such as Black Friday by using multiple channels where your competitors might not be present.

All the segmentation can be done in MarketingPlatform based on behavior data we have collected from your website, purchase history with One-to-Many data, email, and SMS Campaigns.

Set up an integration to Firebase with a few clicks with the Connector

In order to send notifications through Firebase it is necessary to set up a Connector to synchronize Profiles between Firebase and MarketingPlatform. 

Firebase Connector

All you have to do is to select the Firebase standard Connector and upload your authentication downloaded from Firebase – and we can continue to the mapping of the Data Fields.

One-to-Many Firebase

Here we are mapping the fields in MarketingPlatform with the fields in Firebase. On the left side are the Data Fields you have created in MarketingPlatform. On the right side is the information available from Firebase.

Maybe there are fields with information in Firebase that you do not have in MarketingPlatform? Choose either an existing field in MarketingPlatform – that could be First Name or in case you have not created any Data Field in advance, let us create the field for you.

If you select ‘Create field mapped with name and type from connected system’ then we will take care of creating the Data Field in MarketingPlatform with the correct settings whether it is a text, boolean, date, checkbox field, etc.

Hit the blue ‘One-to-Many’ button in order to map deeper data from Firebase. We need to find the token, which will allow us to send the Notification to each Profile.

Map One-to-Many Firebase

Your screen can look slightly different from what you see above. You can drag’n’drop and adjust the data model in One-to-Many to match your own data model as it is in Firebase – or you can map a few selected fields only. You must however map the ‘token’ and tell us that this field is the token by checking the checkbox you see in the image above. In most cases your field will simply be called ‘token’, and if we detect it we might have checked the checkbox for you already.

Once you are sure the token is mapped. You are free to make any adjustments to the data model as you wish and save the creation of the One-to-Many field and save and exit the Connector setup.

View Notifications

View notifications

View Notifications will give you an overview of your existing Notifications. Here you can see your current Notifications, their internal name in the system, the title the receivers will see, when it was last sent and you have the Actions to send, copy or delete them.

Let us go ahead and create a new Notification

Create Notification

Create Notification

Just like when we create a List, Email Campaign, SMS Campaign, etc. we start off by giving our Notification an internal name. No one except you will see the name – it is solely for internal use.

The first thing the receiver of the notification will see is the Title. The title will typically be bolded and will in most cases be the primary text shown in the collapsed notification and is often limiting you to just a few characters to get your customers’ attention.

The text itself is often shown if there is no need to show a collapsed notification or if the notification is expanded.

It is optional to add an image, which will be shown if your customer’s device supports it and if your app has permission to show notifications with images. How each device will choose to show the notification is not something you can control – and it will heavily be influenced by the customers’ user settings as well as how they prefer to see and receive their notifications across their devices.

How does it look when choosing to send a Notification that we have just created? Let us take a look below …

Send Notifications

Send Notification

When you click Send, we can select our List on the left side, and choose another Notification on our right side.

The only Lists available for choosing will be the Lists where you have a Connector with Firebase – only then do we actually have a connection between your List in MarketingPlatform and your customers in Firebase which will take care of showing the actual notification to your customers’ devices.

Firebase Segmentation

Any information from Firebase can be used in our Segment area. In the above example, you see a simple segment finding all the Profiles with a token making it possible for sending Notifications to them.

You will soon find the ‘Send notification’ option in the FlowBuilder.

The post App Integrations and Notifications – Firebase appeared first on MarketingPlatform - Dansk Email Marketing Software.

In order to set up the integration, you will need to set up a connector in MarketingPlatform that will retrieve the required data uploaded to the FTP/sFTP server from an external system, such as a client’s CRM system, webshop, etc.

For more information on how to integrate using CSV or XML files, please refer to the following articles:

One-to-Many CSV integration via FTP

One-to-Many XML integration via FTP

JSON files

Files in JSON format are capable of storing deep data and as such, they are often used to store customer related deep data e.g. order data.

Below you will find an example of a JSON file containing customer order data (see image below). This type of data should be stored in an OTM type data field in the platform.

The file contains customer data coming from an external system, such as:

• email address
• first name
• ID
• order name
• order surname
• order date
• order ID, etc.

In order to retrieve the data to MarketingPlatform you will need to create a connector and map the OTM field/s against the JSON file and according to the data fields included in your list in MarketingPlatform. Mapping them correctly will ensure that each contact’s data in MarketingPlatform is being properly updated with the data from the JSON file i.e. data coming from an external system to the FTP server.

Connector Setup

Access Integration -> Connector in the side Menu on the left and click on Create a Connector.

Select the corresponding list and name your connector.

Next, select the type of connection (FTP or sFTP) and log in with your FTP/sFTP credentials:

• Domain
• Port
• Username
• Password
• Directory path

Click on Connect to FTP server and select the corresponding FTP file (endpoint). Below, you will also find an option to manually set up the synchronization frequency of the connector if needed.

Click on Test Connection to check if you are able to establish a connection with your file directory on the server – you should be able to see the email address/mobile data field fetched from the server.

Next, click on Continue Mapping to map the fields from your list with the data from your JSON file.

Set MarketingPlatform Key Field and Key Field from Connecting System to be either email address or mobile phone depending on how your contacts are being added to the list.

If you have previously created/mapped your OTM field and included it in your list, you can select it under Select Data Field. Otherwise, select Create OTM field from connected system and click on the button Map One-To-Many to map the customer data from your JSON file (see image below).

Note that you must select the appropriate unique key while mapping the OTMDataField, as well as for all other objects in your structure. In this example, the appropriate unique key for the OTMDataField will be the ID of the customer, as one ID will have one or more orders associated with it. That being said, it makes sense to use the ID as a unique key so that the connector can retrieve all data for each of the customers and keep it appropriately updated and organized.

Under Advanced Import Settings, you can set the confirmation/subscription status of the profiles (contacts) being retrieved via the connector and choose to insert new profiles and/or update existing, as well as other settings available (see image below), such as adding the profiles to an existing Autoresponder.

If needed, you can also apply filters to filter the data retrieved by the connector that is to be included in your list.

Once you are done setting up the connector, click on Save and it will be automatically activated and start its first run.

How contact data is saved

To view the data retrieved by the connector, go to your list and click on the View Profiles icon or access your profiles by clicking on Profiles > View Profiles and select your list.

Next, click on the orderdata tab to see the OTM order data that has been retrieved for the specific profile, as shown in the image below.

If you click on any of the data objects you will see the OTM data associated with it, e.g. by clicking on Orders, you will see the OrderName, OrderSurname, OrderData and OrderID corresponding to the example shown.

The post One-to-Many JSON Integration via FTP appeared first on MarketingPlatform - Dansk Email Marketing Software.

XML file format only allows flat data fields and cannot contain deep data (like JSON files). To integrate deep data using an XML file into MarketingPlatform, you may need to combine two files to store customer-related data in the system.

XML file example

XML file 1 contains following information:

• id
• email
• phone
• title
• description
• link etc.

In this example, we can see that the XML file allows only flat data fields. We are missing information on which product/description, each of the ids has ordered. To integrate that information when importing data using an FTP connector, we can combine it with another file that contains the order information (That can be XML file 2).

XML file 2 contains following information:

• id
• email
• customer id
• name
• description
• Price

Combining these two files, we can have an overview of which id has ordered which product, the price, etc. That is how deep data can be stored in the system.

In the example illustrated above, we can see that the email contact: denis.spasovski@ymail.com bought “Product 1” at the price of 1000.

How to setup connector

On the left side choose “Connector” and select “Create a Connector”.

Choose your list, then name the connector and select FTP or sFTP and log in with your credentials:

By ticking “Connect FTP server” select two files: “customer.xml” containing customer data and “customers_orders.xml” with order data.

If you have more than one file, specify which ‘tag’ name combines two sheets which in this case is “id” specified in the FTP file (endpoint 2) line.

Tick “Continue Mapping” and then map flat fields from the “customer.xml” file with the fields from the list.

Set the “MarketingPlatform key field” and “Key field from connecting system” (email address or mobile phone).

Tick the “One Too Many” options to map the customer data from your customer file.

You need to select the appropriate “Unique key,” which, in this case, is “customerid”.

Under “Advanced Import Settings”, you can set the confirmation or subscription status of the profiles; there is an option to choose whether to insert new profiles or update existing and other available options as in the photo below:

How contacts are saved

If the connector was set appropriately the data will be stored on the related list.

When opening a specific profile imported via FTP connector to see the OTM order data, you can tick the “orderdata” as specified in the photo below:

By clicking on any of the given data fields from the left part of the screen on the right side you can see the related information to those fields like customer id, name description, and price.

The post One-to- many XML Integration via FTP appeared first on MarketingPlatform - Dansk Email Marketing Software.

CSV files

Example 1:

In this example, you can see in the first file, that each contact has a customer_id. Each customer_id in the second file will have one or more orders. We simply find all orders associated with a given customer_id and link all orders to the email address associated with the customer_id.

Example 2:

It is important to point out that the nature of the CSV file only allows flat data fields, as seen in the example below. It cannot store JSON data or anything else in these cells.

As you can see in the image above, the contact erik+1@emailplatform.com has order_id 1 and order_id 3. But you can’t see the details of the order such as which products, what date, total amount, shipping status, etc. that each order has. This is the limitation of CSV files.

Therefore, there is often an extra sheet where information on the individual orders is detailed as below:

Here you can see all the details of the orders.

Notice that the order_id is what binds the 2 sheets together.

If we look at the first sheet again, we can see that erik+1@emailplatform.com is represented several times in the sheet. Normally we would consider this as a duplicate contact. But when we know that the sheet will be used to create One-to-Many data, it is quite natural that the contact is represented several times.

Setting up the Connector

Login first with your (s)FTP details.

Select your CSV or in this case multiple files. In this case there are 2 files: custom.csv file which contains customer data and ord.csv which contains order data.

If you have more than one file, you must specify which ‘tag’ name combines the two sheets. In the example mentioned, it was the order_id, which is specified in the FTP file (endpoint 2) line.

You can now map flat fields from the custom.csv file containing customer data.

And then map One-to-Many from the ord.csv file, which contains the word data.

How contacts are saved

If you follow the above example with the 2 files in the corresponding data, you will then see the 2 contacts in the list.

And erik+2 should have fields from the custom.csv file.

And order data from ord.csv.

The post One-to-Many CSV Integration via FTP appeared first on MarketingPlatform - Dansk Email Marketing Software.