Overview:

Description	Allow users to pace delivery of leads to stager lead sending across the duration of a campaign.
Mockup	https://www.figma.com/proto/pyTjqrjDG6UNTQefhagIbh/Campaign---Publisher---Pacing-Delivery?node-id=2-3&scaling=min-zoom&page-id=0%3A1&starting-point-node-id=2%3A3
Assets	https://drive.google.com/open?id=1IH0MGAYzF8TIcU8I8tisBfpWu0G_YwHk&authuser=amish%40convertr.io&usp=drive_fs

Quantitative Data:

Data driven justification for ux/ui changes, especially necessary for organic changes that do not originate from client requests or roadmap features.

Link	Date Range	Item	Metric & Value	Assumption

Link

Date Range

Item

Metric & Value

Assumption

00/00/2021
to
00/00/2021
(0 Days)

Metric name

Metric Value

HYPOTHESES

Lorum ipsum

REASONING

Lorum ipsum

Competitor Research:

Function	Findings	Image	Takeaways

Function

Findings

Image

Takeaways

Embrace

Reject

TO DISCUSS

Proposal Feedback:

Stakeholder	Date	Changes

Stakeholder	Date	Changes
Product	04/04/23	Done Create a ‘minimum requirement’ flow (campaign > publisher > pacing) Existing flow caters for the more complex scenario where pacing can be setup on a publisher and band level with each month being fully customisable. Create a new flow that caters for a simpler scenario where pacing is setill setup on a publisher and band level, but each months requirement is the same. Add a ‘totals’ row On each ‘cap requirement' table (campaign > publisher > pacing), add a ‘totals’ row to help the user see how much of their allocation as been assigned to each month On each ‘fulfilment breakdown’ table (publisher > view > pacing), add a ‘totals’ row to help the user see how much of their allocation as been fulfilled each month Rejected need more info TO DISCUSS Add an ‘autofill/autobalance’ button (campaign > publisher > pacing) Need to scope this to determine how it could work Autofill based on calculation of total leads required split evenly between all months per band depending on number of days remaining Autofill based on a manually input number from user, therefore cutting out most of the potentially repetative number inputting E.g. if campaign duration is 12 months, 10 of those months will have cap of 100, therefore if cap of 100 is autofilled on all inputs, only 2 have to be changed to the unique cap Weekly cadence Require mocks for this yet or waiting on more customer feedback? Dedicated page If we have full customisation on months and publishers and bands, maybe a dedicated page would work better? Could live under campaign > admin? TO DO
Product	14/04/23	Done Rethink previously created mocks by creating a mvp mock with autocalculation and autobalancing Overall idea is for customers to have the least amount of input as possible (the more input, maybe the less likely they are to use the product) Therefore, have a dialog which has a single toggle to turn the feature on and off, no other inputs required Table to display breakdown for each publisher on a weekly basis If campaign settings change (campaign dates, volumes, publisher allocations, adding new publisher), auto balancing occurs without any user input Present this to customers and gauge if this would work for their scenarios, e.g. customers might say: I need to be able to pace monthly I need to be able to manually input because it changes from week to week or month to month, so even distribution doesn’t work Then take this feedback and build on the current mocks if required based on customer feedback Rejected need more info TO DISCUSS TO DO
Product & CS	14/06/23	Done Setup On the pacing dialog in the blue help bar, explain that publisher who are using bands will be delivered on a first come first serve basis On the pacing dialog, have indicator of how much of the requirements have been input (e.g. X / 120 leads required) Breakdown On the pacing dialog, show amount of leads delivered for past weeks Rejected need more info TO DISCUSS TO DO
Product & Dev	21/06/23	Done Setup New column/indicator to show how many leads have been deemed ‘billable’ for each delivery period As the weeks progress, previous delivery periods become uneditable and the allocation indicator will be updated if previous delivery requirements are not met Rejected need more info TO DISCUSS TO DO
Product & Dev	29/06/23	Done Setup Move to dedicated page under campaign > ‘admin’ dropdown rather than dialog Breakdown Remove ‘weekly pacing’ column as the button breakdown is enough for mvp Rejected need more info TO DISCUSS TO DO
Product & DSG	29/06/23	Done Setup Added a screen to show validation when a user inputs a value that is over the total allocation requirement Added a confirmation dialog to ask the user if they’re sure they want to save the configuration even if the configuration will not meet the total allocation requirement for X publisher. Rejected need more info TO DISCUSS TO DO

Retrospective:

To be completed after this features release. The retrospective should allow a basis for further improvements to this feature.

User Feedback

Stakeholder	Date	Description

Stakeholder	Date	Description

Quantitative Data

Link	Date Range	Item	Metric & Value	Assumption