Users
There are two types of users in automation:
- Incremental Users
- Repetitive Users (All Users)
Incremental Users
Zero (0) denotes the incremental users. This includes all of the current subscribers during the first execution, then only the new subscribers in a month/day/week during the following executions.
| 0 = Incremental User |
Repetitive Users (All Users)
One (1) denotes the repetitive users. If the expiry date is “≥” current date, then the user gets the count – otherwise, the team reverts back.
| 1 = Repetitive User |
| NOTE We are updating the parameter current state to 1, last execution time to the current time. Here, the column name is required for understanding purposes. |
Key Points
- When we get the output “recursive status > 0”, we call the start_date. The same update is what we are doing, if “recursive status < 0”.
- Additionally, what we do is for the automation_source_details table, we get source_type (whether it is from Data List or Segmentation). If it is a Data List, then we get the datalist_id or if it is a segment, then we get the segment_id.
- Now, we call a method called active_nq. It is a messenger and is recursive – executes in the backend. From there on, we retrieve back to the frontend. The user will get a message that the automation has started.
- If the automation is ≤ 1 (not greater than), we send message to active_nq.
Columns Structure Info
| Column Name | Description |
| Id | Identity column |
| product | Product id of the product |
| Name | Name of the product |
| createddate | This is nothing but creation of the product |
| enddate | This is nothing but expiry date of the product |
| Expired | “≥” means not expired, ≤” means expired product |
| Database Table automation_master |
Adding the User
To know the source where we have created the datalist, we have decoded the numbers:
| Source Type | Description |
| 2 | If the source type is 2, then it is Form Type |
| 4 | If the source type is 4, then it is Excluded Emails |
| 5 | If the source type is 5, then it is Invalid Domain |
| 6 | If the source type is 6, then it is Threshold |
| 11 | If the source type is 11, then it is Segment |
| 1 | If the source type is 1, then it is Data List |
| 8 | If the source type is 8, then it is Unsubscribe Data |
| 7 | If the source type is 7, then it is Invalid Email |
| 9 | If the source type is 9, then it is Segment Exclusion |
| 10 | If the source type is 10, then it is Duplicate Users |
Process
The process involves:
- Campaign Details: You can set what kind of campaign automation you want. For example, you may want the campaign to run weekly for three (3) months. You can also set the status and display process logs for the campaign.
- Campaign Element: You can set how to process your responses using workflow templates as it is the campaign element which contains the actual activity such as sending out an e-mail.
You can either carry out a follow-up step immediately after a response is received by setting the indicator Start for each Responder or you can collect your responses over a certain period of time and then carry out follow- up steps. This is the case if the indicator is not set. You set conditions, which determine when the follow-up steps are triggered. You can also determine the channels through which campaign execution should be carried out, for setting the status, for displaying process logs for the campaign element and for assigning segments such as target groups to the campaign.
- Decision Node: Here, you specify the rules that should be used for determining follow-up steps. You can either specify that only the first rule where conditions are met should be taken into account or you can specify that all rules should be checked and then executed if conditions are met.
- Optimization Element: The optimization element enables you to optimize your campaign by carrying out simulations and testing different scenarios until you find the ultimate mediums that are best suited for your campaign.