Processr Job Groups
- Adam Carter
What does it do?
A user can group together multiple processor Jobs, and depending on the value within the lead field the user can run different processor jobs.
Action | Description | Acceptance Criteria | |
|---|---|---|---|
| 1 | Manage Groups | A user can create select the option to Create New Group and add the processer job(s) to the group. The user will be able to name the group and set the overall data score of the job passing. A user can select the option to Move to Group which allows the user to move the processor job to a previously created job group. | A user can group together multiple processr jobs into a group. |
| 2 | Edit Group Name | A user can edit the name of the group | A user can successfully rename the group name |
| 3 | Job Conditions - Value | A user can set the conditions of the job group to determine which job needs to run depending on the scenario | A user can add a single value or multiple values. To add multiple values this can be done using a semicolon-separated list. |
| 4 | Job Condition Catch-All | A user can set a catch-all option to fulfil any conditions of the job group scenario that has not been met. | A user has the option to set the condition to catch all. |
| 5 | Job Condition - Field | A user can set which filed the condition needs to run on | A user can select from a dropdown of available fields on the campaign. |
| 6 | Job Condition - Condition | A user can specify the condition that needs to be met | A user can specify the condition that needs to be met with these available options: |
What Uses cases does this apply to?
CONTENT SYNDICATION
Why would they use this feature?
Normally for a lead to be deemed valid it will need to pass all jobs on the campaign. However, users can implement Job Groups which allows the user to pick and choose the processr jobs they want to apply to the lead.
From a customers perspective, this would normally be a manual process where they would need to check the leads against ABM or suppression lists by country.
What the solution does is automate this at scale.
Key Talking Points
- Users have the ability to run different scenarios on lead data typical
- an example would be running a different ABM validation list per country.
- This can also be used for all processr jobs QA, Enrichment and integrations.
An example of how it would be implemented?
ABM by Country
In the example below, there are 4 jobs that have been group together.
Each job is configured with a certain value:
Step 1 (Job Conditions):
Simple Conditional Validation processor job (ID 1649) is configured to only run if for leads that have a country field value of UK or FR.
Step 2:
Once the lead has been routed correctly, it will then run the Simple Conditional Validation processor job for the criteria set.
As you can see in the example the simple conditional validation job will check to see if the lead with a country value of either UK or FR has a field called company_name which equals any of these values:
- Oceanworks
- Nero Sports
- Cryptic Entertainment
- Deserprises
- Whiteoutwares
- Titaniumotors
- Phantasmedia
- Chiefmedia
- Globerover
- Purpleex
Example:
Full example below
In the below example you can see that lead ID 73345 was Accepted because it passed both criteria. The country value equalled with the UK or FR and the company name Oceanworks match one of the values on the simple conditional processr job.
The rest of these leads did not pass these criteria and they all failed on Country.
Note: see lead 73348 has a country value of SA and this would have ran the catch-all processr job as it didn't meet the criteria of the other 3 simple conditional validation jobs.
