Global Leads > Flag/Manage
- Arunima Kurup Prasad
Platform URL | https://[enterprise].cvtr.io/v2/leads |
|---|---|
API Endpoints | Check lead delivery status
Update lead flag status
Mark leads as delivered
Mark leads as undelivered
Mark lead as replacement
Reprocess leads
Delete leads
|
Epic | |
Document status | REVIEWED |
Document owner | @Danny Hannah @Adam Carter |
Technical writers | @Arunima Kurup Prasad |
Related Content | Global Leads Global Leads > Actions > View Global Leads > Export |
Feature Overview
The Global Leads page has a Flag/manage option that allows admin users and agency users to flag leads as Valid/Invalid/Test and to manage (mark as delivered, reprocess, delete etc.) leads. This Flag/Manage functionality enables the user to manually update the lead status.
Flagging leads involves 3 steps:
Leads selection
Type selection
Processing
Step 1: Leads
This step involves selecting the leads for actioning. The user can select leads in multiple ways:
i. User can use the checkboxes available against each lead to select the lead, as shown below
ii. User can type in the lead ids in the text area provided under ‘LEAD ID(S)’
iii. User can import leads via CSV file using the Import icon, shown below
Step 2: Type
Here, the user can select the type of flagging or management for the selected leads. The below options are available:
Mark as Valid: This is used to flag a Lead as Valid. If a processr job has marked a lead as invalid/caution, the user can use this option to flag the lead as valid.
If the user selects this Type and proceeds to Processing step, they will be asked to select a mandatory reason and provide an arbitrary comment. The following reasons are available for the user to choose from.
There is also an ‘Integrations’ section that lists the integration jobs configured in the campaign. If the user wants the lead to be sent to the integrations, they can do so by selecting the appropriate checkboxes against the integration jobs.
Once processing is completed, the lead’s ‘Current Status’ will be ‘Valid’. Any comment added by the user at the time of flagging will be shown in the ‘Status history’ tooltip as shown below.
Mark as Invalid: This is used to flag a Lead as Invalid. If a processr job has marked a lead as valid/caution, the user can use this option to flag the lead as invalid.
If the user selects this Type and proceeds to Processing step, they will be asked to select a mandatory reason and provide an arbitrary comment. The following reasons are available for the user to choose from.
Once processing is completed, the lead’s ‘Current Status’ will be ‘Invalid’. Any comment added by the user at the time of flagging will be shown in the ‘Status history’ tooltip as shown below.
Mark as Test: This is used to flag a Lead as Test. If the user does not want to deliver leads to any integration and want to mark some leads as test data, they can do so by flagging the leads as Test.
If the user selects this Type and proceeds to Processing step, they will be asked to select a mandatory reason and provide an arbitrary comment. The following reasons are available for the user to choose from.
Once processing is completed, the lead’s ‘Current Status’ will be ‘Test’. Any comment added by the user at the time of flagging will be shown in the ‘Status history’ tooltip as shown below.
Mark as Undelivered: It is not possible to change the processr status of delivered leads. Delivered leads will be ignored during flag/manage.
In order to flag delivered leads, they will first have to be marked as undelivered. For this reason, we have the option ‘Mark as Undelivered’. Only the delivery status will change, lead will not be revoked from integration system.
If the user selects this Type and proceeds to Processing step, they will be asked to agree to the condition that marking the lead as undelivered would affect the payout amounts of advertisers and publishers.
Once processing is completed, the lead’s ‘Delivery’ status will be ‘Not Delivered’, billable status will be updated to ‘No’.
Mark as Delivered: This is used to mark a Lead as Delivered. If the user does not want to deliver leads to any integration and want to mark some leads as test data, they can do so by flagging the leads as Test.
If the user selects this Type and proceeds to Processing step, they will be asked to agree to the condition that marking the lead as delivered may affect the billable status.
Once processing is completed, the lead’s ‘Delivery’ status will be ‘Delivered’ but will not be sent to any integrations.
Mark as Other: This is used to flag a Lead as Replacement. If the user wants to flag leads as replacement to invalid/returned leads, they can do so by flagging the leads as ‘Other’ and selecting the reason as Replacement.
If the user wants to change the reason of a lead that is flagged as ‘Replacement’, they can select the option ‘None’.
The user may also provide a reason for flagging a lead as Replacement/None.
Flagging as Replacement
The lead status will not be affected, metadata will be appended to the lead. Replacement leads can be exported using Lead Export, as shown below.
The field ‘Other Reason Type’ shows the reason as ‘Replacement' and the field 'Other Reason Comment’ shows the comment entered at the time of flagging the lead as replacement.
Flagging as None
The lead status will not be affected, metadata will be appended to the lead. Replacement leads can be exported using Lead Export, as shown below.
The field ‘Other Reason Type’ is reset to empty and the field 'Other Reason Comment’ shows the comment entered at the time of flagging the lead as replacement.
Reprocess Leads: When selecting the lead(s), user has the option to reprocess them and to re-run all of the ‘Processr Jobs’ and Value transforms for that specific lead(s). Reprocessing will initiate when user confirms the action by ticking the checkbox and clicking on ‘Save’.
All QA jobs will be re executed for the selected leads and the statuses will be updated accordingly.
Delete Leads:
If the user wants to delete leads from the campaign, they can use the ‘Delete Leads’ option available. They will need to confirm the action by ticking the checkbox and clicking on ‘Save’. The leads will be removed from the campaign and will not appear on any reports for the campaign/advertiser/publisher. The count of deleted leads will be ignored when considering the number of leads on the campaign.
Summary
Summarise the functionalities in a table
Functionality | User Story | |
|---|---|---|
| 1 | Flag lead(s) as Valid | Allows user to change the current status of a lead to Valid |
| 2 | Flag lead(s) as Invalid | Allows user to change the current status of a lead to Invalid |
| 3 | Flag lead(s) as Test | Allows user to change the current status of a lead to Test |
| 4 | Flag lead(s) as Delivered | Allows user to change the delivery status of a lead to Delivered. This marks the lead as billable to advertiser. This will require the user to sign and confirm before performing the action |
| 5 | Flag lead(s) as Undelivered | Allows user to change the delivery status of a lead to Not Delivered. This marks the lead as not billable to advertiser. This will require the user to sign and confirm before performing the action |
| 6 | Flag lead(s) as Other | Allows user to mark a lead as Replacement and undo the same |
| 7 | Reprocess lead(s) | Allows user to rerun QA jobs and Value Transforms on selected leads |
| 8 | Delete lead(s) | Allows user to delete leads from the campaign |
User Permissions
Only Admin and agency users have access to Flag/Manage functionality in Global Leads.