| Page Properties | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Target release
|
...
🏠 Feature Overview
The lead view is here to enable the user to understand the lead data to be able to perform an action on a lead. The user has the choice to perform a multitude of actions and can debug any technical issues that the lead may have.
🎯 Objective
Success metrics
Goal | Metric |
|---|---|
Streamline process | Improved user engagement |
...
| Info |
|---|
Provide details of what the feature is trying to resolve. |
\uD83E\uDD14 Assumptions
| Info |
|---|
Provide any assumptions/pre requisites that are needed for the feature to work. |
\uD83D\uDDD2 Requirements
Requirement | User Story | Importance | Jira Issue | Notes | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Reprocess a Lead | As an Admin or agency user on the live lead or campaign leads page when selecting the lead(s), they then have the option to reprocess them and to re-run all of the ‘Processr Jobs’ and Value transforms for that specific lead(s) |
| ||||||||
| 2 | Flag a Lead as Valid, Invalid or Test | As an Admin or agency user on the live lead or campaign leads page when selecting the lead(s), they have the option to flag a lead as Valid with the option to select why it has been accepted if one of the options does not apply the user can as well specify their own reason. Once flagging a lead as valid the user additionally has the option to then decide which integration they would like to run. As an Admin or agency user on the live lead or campaign leads page when selecting the lead(s), they have the option to flag a lead as invalid with the option to select why it has been rejected, if one of the options does not apply the user can as well specify their own reason. As an Admin or agency user on the live lead or campaign leads page when selecting the lead(s), they have the option to flag a lead as a test with the option to select why it has been marked as a test lead, if one of the options does not apply the user can as well specify their own reason. |
|
|
| ||||||
| 3 | Mark a lead as Delivered and Undelivered | As an Admin or agency user on the live lead or campaign leads page when selecting the lead(s), If the lead is valid and undelivered, they have the option to mark a lead as delivered which in hand marks the lead as billable to the advertiser. The user will need to sign and confirm before performing the action. As an Admin or agency user on the live lead or campaign leads page when selecting the lead(s), If the lead is valid and delivered, they have the option to mark a lead as undelivered which in hand marks the lead as not billable to the advertiser. The user will need to sign and confirm before performing the action. |
| ||||||||
| 4 | Bulk Edit | As an admin or agency user they will need to have the ability to perform all of the above action 1-6 within a bulk action. The user will be able to input a list of lead id(s) (separated by a semicolon) then select the action they wish to perform in bulk. |
| ||||||||
| 5 | Add Lead Data | As an admin or unmasked agency user, they have the ability to add lead data to an existing lead. When the user interacts with the lead they can click add and then input the additional data to the lead record |
| ||||||||
| 6 | Edit Lead Data | As an admin or unmasked agency user, they have the ability to edit lead data to an existing lead. When the user interacts with the lead they can click edit and then change the data on the lead record |
| ||||||||
| 7 | Custom Tables | As an Admin, Agency or Creative Manager user, they will have to option to customise the table with selected options to choose from | |||||||||
| 8 | Column Filter(s) | As an Admin, Agency or Publisher user, they will have to option to filter certain table columns with selected options to filter on. |
User interaction and design
Lead View (live global and campaign)
Open Questions
Question | Answer | Date Answered |
|---|---|---|