Your products: from the catalog to your emails automatically! – Send Pagebuilder Release v.1.9.0

We haven’t stopped our activity during the Summer and a new Pagebuilder feature is now available for boosting your emails. Contactlab’s email editor is enhanced to help you produce sophisticated and engaging communication, elevating it to higher levels thanks to the support of our creatives!

What can you do with this release?

You can choose to populate the fields of your email with data about your products – name, short description, price, etc.. – in a fully automatic way.


How it works

In the list of modules visible on the left of the workspace and present in the template that you gradually enrich and update with information to build your email, you will find a space dedicated to products. Step 1


Clicking on the module, it opens a window in which you can select the product code of your interest. You also have the possibility, in addition to the product, to choose the language in which you want the text to appear. Stepp 2


Confirming it, all the data related to that product, automatically appear in your email exactly in the position you have chosen in advance with the contribution of our experts. Step 3

What does it means?

From now on you can create emails with a higher level of content customization and fully automatically. Reduce time and optimize operations.

Choose texts, images, CTAs, layouts and allow your products to move from the catalog to the emails in a snap of a finger!

Call us now. The new feature is already available but it must be activated by our team of experts on the specific email template you wish to work on.



changelog Guide Resources Support



Read more

Send test for each email step in your journey – Flow release API v.2.23.0-923 and UI v.2.32.0

From August 19th, 2020, a new Flow version is available.
The release is planned between noon and 01:00 pm CEST.

What can you do with this release?

Send test emails to the addresses you want and each time you modify a template in your journey so that you can see the result immediately and make the appropriate changes before the actual delivery.

Thanks to this release you can customize text items of your communications and see how it looks like immediately by sending test emails to whoever you want. And you can do it for every single email step in your automation.

The goal is to streamline the test phase in particular in the management of variables in order to reduce the time required for the entire operation. Doing everything in the area dedicated to Marketing Automation means you no longer need to configure the event – i.e. the variable – in the Hub section because you will have everything immediately available during the creation of the journey.

You will test the graphics and effectiveness of your emailings instantly and within the same platform functionality!

How it works

CTAWhen you create a new step characterized by the send email action, and only after you have inserted the content of the template, the Create new test button will be enabled in blue.

At that point you can click it and choose who to send the test to.



What does this mean?

A huge support especially in case of complex journeys. You no longer have to wait for the creation of the entire flow but you can test the individual emails in the journey, whenever you need it and directly in the marketing automation tool.



changelog Guide Resources Support




Read more

One automation, many flows – Flow UI Release v.2.27 and API v.2.20.0-837

From May 5th, 2020, a new Flow version is available.
The release is planned between noon and 12:30 pm CEST.

What does this release enable you to do?

It becomes possible to express conditions based on relative dates on the attributes of the profile date and events date within the source or in the checks of your journey

Let’s try to see it better with an example.

Two traveler friends have both entered your automation after subscribing to the new newsletter that you have designed to support your contacts in the post lockdown. An appointment that newsletter after newsletter helps them to understand the good practices to implement and the warnings to follow, in order to leave safely and compliant.

Flow: relative datesOne of them, however, is an old contact, a customer for years who already follows you on many communication channels. You know that he is a skilled climber, he often stays in mountain villages and travels a lot on his own during the weekend. The other one is a new entry and you know that he is a friend of the first one because the subscription to the newsletter was suggested by him through “share” CTA. In filling out the subscription form he was accurate and left you a lot of information: he loves long distance trips, his favorite destinations are the tropical seas and above all he always travels with his family composed of two adults and two children under 6 years old.

You are therefore faced with two people who have subscribed to the same service – the post-lockdown newsletter – and therefore left for them the same journey but:

  • They’ve been among your contacts for a different time, from different dates.
  • They have different interests.

You can therefore prepare the same automation for them but once they have started, you can plan different actions and/or communications, in different times and ways, all depending on the fact that they have entered your db at different dates.

The same logic could be applied to many other scenarios basing the condition for example on the moment of the first purchase or the date of a future departure or other data that could be relevant for your goal.

How it works

Let’s take our example. Suppose we choose, as we said, the date of the subscription in the db for creating the condition and deciding in which branch of the automation each contact enters.

In the profile the DATA_INSCRIPTION attribute collects the information you need and then in the source or in the flow checks you can enter a condition of this type:

“DATA_SUBSCRIPTION” “greater than” “(today) -6 months”.

which means that, in order to be verified, the condition requires that at the time of its evaluation – i.e. today – the customer has been subscribed for less than 6 months.

Flow: source Flow: conditions


As the first friend, the climber, has been in your db since February 2015, he does not respect the above condition. He will continue in your automation in the B branch, will receive important information for the post lockdown dedicated to all but also specific content reserved only for the most obsolete contacts such as a survey to qualify and update all his data perhaps in exchange for coupons on his next trip.

The sea lover, on the other hand, only entered your db in March 2020. He responds perfectly to the condition set. His journey will continue in branch A, he will receive the same information as his friend on the post lockdown but among the proposed content he will find a box dedicated to the stories of customers who have already experienced the thrill of traveling with you in exotic destinations and a welcome coupon to be used within 6 months after the end of the lockdown.

What does this mean?

Further increase the quality of your flows by refining the conditions that allow you to better manage time and content. You can also customize the travel of each contact according to when an action has been taken or an event has occurred.


changelog Guide Resources Support





Read more

Are you updating an event? Automatically enter the customer in a predefined journey – Flow UI Release v.2.25 and API v.2.20.779

From March 19th, 2020, a new Flow version is available. The release is planned between 11.00 am and 11:30 am CET.

What does this release enable you to do?

You can decide to insert a contact in an automation also setting the event update as the trigger.

Why also?
Because now the only possible trigger is the creation of a new event.

For all joiurneys that are using a Real Time source, there is therefore the possibility to decide the trigger for the automation:

  • The new customer events only.
  • The new customer events and the event updates.

In both cases it remains possible to add further conditions on the event and profile properties to define more precisely when a customer must, or must not, be inserted in the flow.

Flow: trigger update eventThe activation is very simple: with a simple checkbox located below the event selection area that triggers the insertion in the flow. If the checkbox is selected, event updates are also considered.



What does this mean?

Think about two simple but effective examples.

Let’s start with brands with different status for completedOrder events: confirmed, paid, shipped, etc. They could trigger the insertion of the contact in the automation, when a specific status is reached and create more detailed journeys and marketing activities.

Or again in the loyalty area: when a certain level of points is reached in the grantedCoupon event, or vice versa, when you are stuck at a credit threshold for too long, it could be useful to automatically trigger activities towards customers, inserting them in predefined automations.



changelog Guide Resources Support




Read more