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 5 Next »

Platform URL

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

Epic

Type /Jira to add Jira epics and issues

Document status

DRAFT

Document owner

Anu Kalangi

Designer

@ designer

Tech lead

@ lead

Technical writers

@ writers

QA

🏠 Feature Overview

Setting up an Advertiser

The advertiser is the client accepting the leads. The advertiser will be able to set up multiple campaigns per advertiser and assign publishers to campaigns to provide leads to these campaigns.

From this interface you can Add, Import, Delete, Create New Campaign and View Advertiser

Add Advertiser

When adding a entry to the advertiser, you will be able to enter the following fields:

Name

Required

Notes

Advertiser Name

(tick)

Advertiser Name has to be unique

Account Manager

(error)

This is the clients' contact

Campaign Manager

(error)

Internal Team managing the campaign

First Name

(tick)

Last Name

(tick)

Email

(tick)

Telephone

(tick)

Postcode

(tick)

Address

(tick)

City/Town

(tick)

Country

(error)

IO Management

(error)

Toggle Default is set as disabled.

Contracts

(error)

Toggle Default is set as disabled. This determines if the contracts are auto-signed

Default Publisher Terms

(error)

If specific campaign terms need to be made default, they can be placed here.

Notes

(error)

Notes will apply to all publishers.

Import Advertiser

Import Advertiser will let the user import a CSV file.

View Advertiser

View Advertiser will let the user create a campaign, view the campaigns associated to the advertiser, account details, value transformation, default value settings and validation lists.

🎯 Objective

Provide details of what the feature is trying to resolve.

\uD83E\uDD14 Assumptions

Provide any assumptions/pre requisites that are needed for the feature to work.

\uD83D\uDDD2 Requirements

Requirement

User Story

Importance

Jira Issue

Notes

HIGH

 

 

 

 

 

\uD83C\uDFA8 User interaction and design

Provide any mocks or wireframes if applicable

(question) Open Questions

Question

Answer

Date Answered

(warning) Out of Scope

Provide any details of additional feature requirements that haven't been scoped.

  • No labels