Platform Reporting - Customer

Document status	DRAFT
Document owners	@Barnaby Murtagh (Unlicensed) @Adam Carter @Danny Hannah
Tech lead	@Danny Hannah
Stakeholders (Convertr)	@Adam Carter @Hilton Young (Unlicensed)

Objective

To carry out customer feedback sessions in order to pinpoint the specific pain points customers are facing in relation to reporting within the platform.

Assumptions

Platform Reporting - Customer will only focus on the Data reporting for clients within the platform. Internal Convertr data reporting is not to be covered in this documentation and will be addressed as a separate document here.
Different customers dependent on role/seniority level within the customer business will require a range of granularity in the report information they are trying to collate.

Requirements

We will collate the requirements for delivering Platform Reporting - Customer based on the feedback sessions we hold with customers in the coming weeks.

	Requirement	User Case / User Story	Importance	Jira Issue	Notes

	Requirement	User Case / User Story	Importance	Jira Issue	Notes
1	Lead Reporting		HIGH
2	Publisher Reporting
3	Pacing/Delivery Reporting
4	Financial Reporting
5	Campaign Reporting
6	Usage Reporting

Open Questions

Question	Answer	Date Answered

Question	Answer	Date Answered
What reports are customers looking to create?
Which business areas within the customer business are looking for reporting capabilities?
What are customers expectations on how they will be able to view the data within the platform.
What data fields do you most use to report on?
How does the report need to be formatted?
Are users expecting data visualisation?
Does the reporting need to be automated?
Does the data need to be integrated into another system?

Out of Scope

All data reporting related to internal platform reporting

Success metrics

Once we understand the problem we are looking to resolve for the customer base we will address the metrics for success.

Goal - TBC	Metric - TBC

Goal - TBC	Metric - TBC

Knowledge Base