Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 9 Next »

Platform URL

https://[enterprise].cvtr.io/v2/leads

Epic

DAS-56 - Getting issue details... STATUS

API Endpoints

GET https://{enterprise}.cvtr/api/v4/leads

Add all associated endpoint details

Document status

DRAFT

Document owner

Adam Carter

Technical writers

Related Content

https://convertr.atlassian.net/wiki/spaces/PF/pages/edit-v2/3063447553

šŸ  Feature Overview

A logged in user should navigate to Dashboard->Leads to view global leads listing table.

Here they can perform a multitude of different actions on the lead data ranging from filtering the leads or performing bulk actions such as flagging leads as valid or invalid etc also depending on the user they can debug any technical issues.

User can view, flag/manage and export leads for reporting.

The main objective is to allow the user to manage their lead data all in one place. This is done by allowing the user to understand the lead data and to be able to perform an action on a lead.

The following actions can be done on leads by the user:

  • Flag/Manage

    • Reprocess a Lead: 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)

    • Flag a Lead as Valid, Invalid or Test: 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.

      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.

      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.

    • Mark a lead as Delivered and Undelivered: 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.

      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.

  • Add/Edit Lead Data: 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. 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

  • Custom Tables and Column Filters: Current Status - Filter on lead status valid invalid test or caution

    Campaign - filter by campaigns

    Date. - filter between dates

    Lead Generator - filter by publisher

    Processor Status - Filter by the different statuses

  • Widgets

\uD83D\uDDD2 Summary

Functionality

User Story

1

Table Filtering

\uD83D\uDDD2Ā User Permissions

https://docs.google.com/spreadsheets/d/1i4qTTKkC3rF3EyEOh2585ktDDGge0L0IMVDNCwriFR0/edit#gid=1329587291

  • No labels