How can we help?

Getting started

Home
Quick Start
Tutorials
Templates
Recent Updates

Building

Creating a popup
The Popup Editor

Connecting

Embedding your popup
Subscribing to popup submissions
Integrations

Observing

Popup Analytics
Popup Submissions

Company

Terms and conditions
Privacy policy

The goal action editor

The actions editor is a small piece towards benefiting a stage in one of your goals. They are used to intelligentily interact and engage your visitors.

With the action editor you will define a user journey and determine when something will happen. For example, you can easily show a popup to a visitor after they have visited a certain page.

The main objective of your action should be to focus on encouraging a visitor to convert to the next stage in your action journey. The condition of the next stage is shown at the bottom of the page.

Page overview

On the left side we have the main area where you will define the user journey. This can be as complex as you like, but ideally should focus on converting your visitors to the next stage.

On the right side we have the block sidebar, this displays all the available blocks that you can apply to your visitor journey. The blocks are broken down into different categories depending on their purpose.

These blocks are either conditions or events.

Conditions

Conditions are used to ensure a visitor meets a requirement, such as if you have a device condition, it will check the device of the visitor. If the device is not matched, the visitor will not continue down that path.

You can easily introduce alternative paths a visitor can take depending on this condition.

Events

Events are when something happens, so in the journey it may be showing a popup when the visitor passes the block. The journey also provides a conditional path depending on if the visitor submitted the popup or dismissed the popup.

The block sidebar

The block sidebar is where you can find all the blocks you can apply to your visitor journey. They are broken down into the following groups:

  • General
  • Effect
  • Triggers
  • Conditions
  • Traffic

The general group contains the show popup and end block.

The end block doesnt do anything, it just states that the path has ended in your journey.

The show popup block is used to trigger a popup to display to your user.

Show popup

When you click on a "show popup" block in your vistor journey, the sidebar on the right will change into a form to allow you to configure your popup. Depending on the appear type of your popup, you will have access to certain options.

In this case, the popup appear type is to show a modal, do here you can determine if the backdrop is shown and if the backdrop can hide your popup.

In this form you can also very easily change to another popup using the "Popup to show" dropdown, here the unique identifier of the popup is shown, but in the visitor journey you get a preview of that popup and in the dropdown we use the assigned name.

The effect group

Another important part of the block sidebar to mention is the effect group.

These blocks are very special but can make your visitor journey very powerful. In the current version, from (5th of April 2021), there are the following blocks:

  • Repeat
  • Wait
  • Webhook trigger
  • Integration trigger

The repeat block will allow you to push the visitor to another block in your journey, please use this wisely and dont introduce painful loops that will impact the experience of your visitor in a negative way. Ideally our visitor journeys should enhance the experience.

The wait block can pause the journey for your visitor, with the wait block you can have the block wait multiple days, a few hours and a few minutes.

The webhook trigger and the integration trigger will send some event to another service you use, for example if a visitor passes a certain block, maybe you want a Google spreadsheet to add a new row. This is possible with the integration trigger.

We use Zapier.com for integrations, with Zapier you can connect Embedery to over 1,500 different services and applications.

The trigger group

The trigger group contains blocks to wait for a visitor interaction. For example when a visitor scrolls to a certain point in a page, then show a popup. With triggers this is easily possible

The conditions group

With the blocks in the condition group, you can filter and target specific visitors depending on their device, if they are a returning visitor or even if they have passed a path before.

We will add more conditions overtime depending on your needs.

The Traffic group

Finally we have the traffic group, this group is used to conditionally continue depending on the traffic source or the query string of the webpage. You may want to target certain visitors depending on the query string, this would work if you want to target visitors from a paid advertisement.

Changing the name

To help you know which action is which, we have added an easy way for you to quickly change the name of your action.

In the input field next to the breadcrumb, just change the name and press save. And that's it.

Analytics

The last feature of this page is the traffic share percentage. This is still in beta at the time of writing this, so its not perfect. but it will break down where your traffic is going and reveal bottlenecks in your visitor journey.

This will allow you to quickly understand where the journey is not working and make optimisations to make your journey more effective.

My issue is still not resolved.

We are sorry to hear that you have not found the appropiate documentation to help solve your problem.

Please reach out to us and we will do our best to help.

© 2022 Embedery