Marketing.ThoughtLeadership

Purpose The purpose of these queries is to streamline the integration and transformation of marketing and campaign data from multiple sources into a unified format. These Power Query scripts address various types of campaign-related data—ranging from email campaigns, social media posts, and advertising, to events, page performance, and form submissions. Process

Marketing.Meltwater

Purpose The purpose of these queries is to streamline the integration and transformation of marketing and campaign data from multiple sources into a unified format. These Power Query scripts address various types of campaign-related data—ranging from email campaigns, social media posts, and advertising, to events, page performance, and form submissions. Process

Marketing.LandingPages

Purpose The purpose of these queries is to streamline the integration and transformation of marketing and campaign data from multiple sources into a unified format. These Power Query scripts address various types of campaign-related data—ranging from email campaigns, social media posts, and advertising, to events, page performance, and form submissions. Process Source Selection: The query … Read more

Marketing.DataMapping

Purpose To provide a SharePoint list designed to map the source field names (attributes) with the corresponding target report column names. Data Fields Field Name Description Attribute Name The exact name of the field as it appears in the data source. Platform The name of the data source route (e.g., CRM, Website Analytics, etc.). Label … Read more

Project.ActivityDetails

Purpose [FACT_PROJ_ACTIVITY_INFO_OL] unique based on ACTIVITY_SEQ, CONTROL_CATEGORY_KEY This table plans to be unique for ACTIVITY_SEQ only Use Case Owner: Martyn ColeTypical Use Case: Provide details for ACTIVITY_SEQ and Sub Project IDStyle: Dimension, Dimension i.e. Single row per ACTIVITY_SEQ Source Key Parameters CompanyProjectCustomerActivitySeq Sample Exec Response SEQ Dates Measures Codes SQL

Customer.Details

Purpose The Customer Details view serves as a unified source for basic business customer information, accessible across departments for consistent reporting and analysis. It excludes transactional data (like dates or measures) and provides a limited set of dimensional attributes, designed for integration with fact tables in reporting scenarios. Use Case Owner: Data EngineeringTypical Use Case: … Read more

Project.CustomerInvoice

Purpose The Project Customer Invoice (value) Fact TableDesigned to display quantitative data related to invoices generated for projects. This table integrates with dimension tables, such as client_details and project_details, to provide detailed insights into the financial aspects of projects, including invoicing, revenue, and billing trends. The primary purpose is to support forecasting, budgeting, and proactive project … Read more

Project.CustomerOrderLine

Purpose The Project Customer Orderline (value) Fact TableDesigned to display quantitative data related to orders generated for projects. This table integrates with dimension tables, such as client_details and project_details, to provide detailed insights into the financial aspects of projects, including invoicing, revenue, and billing trends. The primary purpose is to support forecasting, budgeting, and proactive project … Read more

Customer.Market_Campaign

Purpose To construct and deliver a global marketing report capturing performance across channels and platforms, aligning results against campaign or core (BAU) KPIs and assumed customer behaviour. Use Case Owner: Emma O’NeillTypical Use Case: capturing performance across channels and platformsStyle: Fact Source Key Parameters CompanyDetails Sample Exec Response SEQ Dates Measures Codes SQL

Customer.Invoice

Purpose Customer Invoice, provides high-level invoice details primarily focused on essential customer and financial information. It is structured to include invoice metadata, billing details, amounts, and various identifiers. The view originates from multiple snapshots and iterations, with each change tracked meticulously to support functionality and flexibility for different reporting and integration requirements. Use Case Owner: Soon … Read more