campaign-goals

Campaign Goals – Mautic 3 plugin

Fast Reliable Well documented Mautic plugin

Would you like to handle the first few submitter or clicker on a different campaign branch? With this plugin you can set campaign goals and thus you can put the first few winners into a different segment.

version:3.0.0

Purpose

Running campaigns is a built-in tool in Mautic. Campaigns consist of successive steps of three types – actions, conditions, decisions.

In the campaign, the ‘Condition’ type step is used to branch the course of the campaign according to certain conditions. However, the ‘condition’ type step in the vanilla solution only offers conditions that apply to the member for whom we are running the campaign. 

The plugin allows you to create campaign Condition that branches based on global conditions, instead of the member’s status, data (fields, tags, segments, etc.), but. 

How does it work?

Using the plugin allows to create a Condition type step in the campaign journey builder, that can test one of the the following global criteria:

  1. How the membership count of a segment relates to a specified number.
  2. How the membership count  of a campaign relates to a specified number. 

A campaign condition always has a true and a false branch based on the condition defined in it – to which additional campaign steps can be attached. When a campaign is run on a member, the campaign proceeds on the true or false branch based on an evaluation of the condition specified in the condition.

* Some examples of conditions can be formulated:

  • Is the number of members of segment ‘A’ less than 5?
  • Is Campaign ‘B’’s membership greater than 10?

What can it be used for?

Rewarding first clicks

If we send a letter to a target audience and want to reward the first few clicks, all we have to do is check with a ‘campaign goal’ branch to see if our target segment is full. We need to collect the first clicks into a target segment on the true branch. If the segment is full, we can notify those that went to the false branch of the condition.

Rewarding First Form Fillers

If we fill out a form with our members and want to reward the first time we fill out, all we have to do is check with a ‘campaign goal’ branch to see if our target segment is full. We need to collect the first fillers into a target segment on the true branch. If the segment is full, we can notify those who are above the threshold.

Applying

If we offer our members a subscription to a limited-capacity event and we can only accept the first few candidates, all we have to do is check with a ‘campaign goal’ branch to see if our target segment is full. We need to gather the first applicants into a target segment on the true branch. If the segment is full, we can notify the fake branch of the laggards.

‘Screenout’ management

In the case of market research, the subset of our potential customers/users who do not correspond to the original target group due to some special feature related to them is excluded from the research during the process. The exclusion process is called the ‘screenout’ process.

* Eg.: We would expect 100-100 female and male responses during a software evaluation campaign. The 101st was placed on the ‘screenout’ of either male or female applicants with whom we need to communicate accordingly.

With the usage of ‘Campaign Goals’ plugin, if someone does not fit into a target segment, we can notify them.

Restricting Participation in a Campaign

If we only accept applications, fills, clicks, etc. from a certain number of first members, we have the option to limit how many people participate in a particular campaign.

Restricting the number of simultaneous participants in a campaign

If you want a certain campaign to have only a certain number of members at a time, you have the option of limiting the number of members in that campaign to another.

You must make sure to remove members from the campaign at the end of the campaign so that the other campaign monitoring the number can start a new member.

Dependencies

A bővítmény használatához szükség van a phpbolt nevű php kiterjesztés futtatási környezetbe való beépítésére.
  • Your cart is empty.

Verziótörténet

3.0.0

  • new function Show version number at the settings page.
  • new function Show version history link at the settings page.
  • optimization New version numbering logic aligned to the major Mautic versions.
  • bugfix

2.1.1

  • new function Add detailed documentation.

2.1.0

  • new function Add licensing.

2.0.0

  • new function Mautic 3.* compatibility.

1.0.0

  • new function First version.
  • Your cart is empty.

Version history

3.0.0

  • new function Show version number at the settings page.
  • new function Show version history link at the settings page.
  • optimization New version numbering logic aligned to the major Mautic versions.
  • bugfix

2.1.1

  • new function Add detailed documentation.

2.1.0

  • new function Add licensing.

2.0.0

  • new function Mautic 3.* compatibility.

1.0.0

  • new function First version.