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/advertisers

API Endpoints

Retrieving advertisers

GET-https://{enterprise}.cvtr.io/api/v4/advertisers

Retrieving Value Transforms

GET- https://{enterprise}.cvtr.io/api/v4/advertiser-value-transforms

Retrieving Suppression Lists

GET- https://{enterprise}.cvtr.io/api/v4/suppression-lists

Epic

DAS-14 - Getting issue details... STATUS

Document status

DRAFT

Document owner

Anu Kalangi

Designer

@ designer

Tech lead

@ lead

Technical writers

@ writers

QA

Related Content

/wiki/spaces/PROD/pages/2678095965

🏠 Feature Overview

Setting up an Advertiser

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

  • View account details

  • Add Value Transformation

  • View Default Value Settings

  • Add Validation Lists.

Create Campaign

Account

Account tab displays the account details entered when the advertiser was created.

Value Transformation

Value Transform lets the user take the data that already exists in platform, and create new data based off of them that can be used to report, integrate and categorise your leads.

There are two types of Value Transforms: Transforms and Manipulation

  • Transforms: This allows the user to take known data values which are expecting to receive, and transform them into a new value in a new field.

  • Manipulation : This allows the user to reformat unknown data values - combines different fields together (concatenation), or change a telephone number's format (Regex Find and Replace).

User can create value transform by importing or creating the new.

Importing Value Transforms

Click import and download the csv file

Once downloaded, fill in each row with the value transform you want to add - values with the same original field name, new fieldname and group name will be grouped together.

Add Value Transforms

Click Add on the Field Names tab.

When adding a entry to the value transform, user enter the following fields and clicks Save

Name

Required

Notes

Label

(tick)

Enter a label name

Original Field Name

(tick)

Select from the dropdown

New Field Name

(tick)

Enter new field name

Type

(tick)

Specify the type of value transform

Original Value

(tick)

New Value

(tick)

Transform

Manipulate

Value Transform Groups

User can create groups into which user can add previously-created Value Transform Fieldnames.

Validation Lists

Validation lists allows users to check the leads against the list of values to target or supress and pass/reject a lead based on the condition selected.

Validation Lists can be set up in two areas:

  1. System Level

    a. Lists applied at this level will be accessible across all campaigns in your enterprise

2. Advertiser Level

    a. Lists applied at this level will only be available to campaigns set up under this advertiser.

Setting Up Validation Lists At An Advertiser Level

Click Add

When adding a entry to the validation list, user enter the following fields and clicks Save

Name

Required

Notes

Name

(tick)

Enter the validation list name

Private

(tick)

Private toggle affects the view of the list for any Agency type users on your platform. If set to Private, Agency users will not be able to see the values that are added to the list, or make any changes to it.

Clicking Save will open a Add Validation List modal where the user can add values or Import values.

🎯 Objective

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.

\uD83E\uDD14 Assumptions

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

\uD83D\uDDD2 Requirements

User Permissions

The users should have access to the advertisers to be able to view the advertisers

Advertiser user.

As an advertiser user, I should be able to view the campaign(s) the advertiser is associated, Account and Value Transform.

Agency user

As an agency user, I should be able to add advertiser, create campaigns and view campaigns.

Advertiser Report user

As an advertiser report user, I should be able to view the campaign(s) the advertiser is associated, Account and Value Transform.

Requirement

User Story

Importance

Jira Issue

Notes

HIGH

 

 

 

 

 

\uD83C\uDFA8 User interaction and design

Advertiser-Create Campaign -https://www.figma.com/proto/XSFJYyCCNM0Z41Lh961pMm/ADVERTISERS---Create-Campaign-V3?scaling=min-zoom&page-id=0%3A1&starting-point-node-id=9%3A2&node-id=9%3A2

Advertiser- Import-https://www.figma.com/proto/AsU5TdoA31PwSqZsuTRKY4/ADVERTISER---Import?node-id=2%3A7&scaling=min-zoom&page-id=0%3A1&starting-point-node-id=2%3A7

Advertiser- Validation Lists-https://invis.io/WQ10SOR1P56B

Advertiser-Value Transform-https://invis.io/MEUGRPETYWK

https://invis.io/59UA4R5H3QR

(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