
STA1000 - Data Analytics and Metrics
STA1000 - Data Analytics and Metrics…
You will learn …

Since 2019, I have been teaching Data Analytics and Statistics at DCU Business School.

Without data, an organisation could not successfully complete most business activities. However, organisations need to convert these data into meaningful information
Example: Sales Manager
Data → transformation process → Information
Marketing produces enormous quantities of data and comparatively little information. A dashboard with forty numbers on it is still data.
The science of using data to build models that lead to better decisions that in turn add value to individuals, companies and institutions
The analysis of data, typically large sets of data, by the use of mathematics, statistics, and computer software.
flowchart LR P["Business<br>performance"] --> A["What happened?<br><b>Descriptive</b>"] P --> B["Why did it happen?<br><b>Diagnostic</b>"] P --> C["What do we want to happen?<br><b>Predictive and prescriptive</b>"]
Historical information and reference data about customers or products, used for analysis and decision support:
Before we look at any tool, one question, which we will return to in every lecture:
What decision would change if this number were different?
If the answer is “none”, the number is decoration. Producing it is not analysis, it is reporting.
The term Big Data corresponds to a table containing observations (i.e. database or dataset) that is too long, too large or too complex to be handled by conventional tools
Have you ever tried to scroll down to the end of Excel? Because I did!
The first three are properties of the data.
The last two are properties of the decision you are trying to make.
Most big data investment optimises the first three and assumes the last two.
More rows do not fix a badly posed question.
More rows do not fix a biased sample. A million records from people who accepted cookies still tells you nothing about the people who declined.
More rows make spurious correlations more likely, not less. With enough variables, something always correlates with revenue.
Most marketing questions are answered with a few hundred rows. You will spend most of this module with datasets small enough to open in a spreadsheet.
Data collection is never free:
Collect what a decision needs. Not what a tool offers.
Stories are how we translate core, essential content
to different forms
for specific audiences.
Visual communication plays an important role in a visual analytics process. No matter how advanced and sophisticated the techniques are, if you fail to tell a compelling story with the visualisation you designed, all the hard work is wasted.

Data is gathered and filtered, then structured, then decoded by an audience with its own memories and expectations. Two of those three steps are yours.
Exploratory analysis
Explanatory analysis
You will do a lot of the first. You are assessed on the second.
Reporting
“Sessions were up 12% last month.”
Describes the past. Changes nothing on its own.
Analysis
“Sessions were up 12% because paid search spend rose 40%, and cost per conversion rose with it.”
Explains. May change a decision.
Decision support
“Paid search is now above our cost-per-acquisition ceiling. Cut spend by 30% or raise the ceiling.”
States the option and its cost.
Most marketing dashboards stop at the first column. This module is aimed at the third.
What the tool gave you
What a newsroom would publish
*Same data. Same finding. The difference is who it was made for.
“Looks nice” is not on the list.
When adding text or visualisations, ask yourself: “Does this element support the point I want to make about the data?”
Use annotations to guide someone through the figure. But only label the data that matters.
. . .
Six questions, thirty seconds. Most bad charts fail the first one.
A Dublin 8 womenswear label, founded 2024 by two design graduates.
Small-batch drops of five to nine pieces cut from deadstock and recycled fabric. Direct to consumer through its own store, no wholesale, no shop.
Five people, one of whom writes the posts and buys the ads. Prices €45 to €180, gross margin 52%.
Instagram is effectively the entire top of the funnel.
Go to loop page and download the file insta-data.csv
Create a 1 page PDF report of follower’s engagement in the last 18 months with actionable insights.
05:00
“In three words: deep learning worked.”
“In 15 words: deep learning worked, got predictably better with scale, and we dedicated increasing resources to it.”
“That’s really it; humanity discovered an algorithm that could really, truly learn any distribution of data (or really, the underlying “rules” that produce any distribution of data). To a shocking degree of precision, the more compute and data available, the better it gets at helping people solve hard problems. I find that no matter how much time I spend thinking about this, I can never really internalize how consequential it is.”
- Sam Altman, [The Intelligence Age, 23-09-2024]
Typically meant in the context of content-creation
This is not new: thispersondoesnotexist.com (2018)
But became significantly more powerfull, flexible, practical, and “mainstream” around ~2022
\[P(token_n|token_{n-1}, \cdots, token_1)\]
A token: a single character, a combination of characters, or a word
\[P(token_n|token_{n-1}, \cdots, token_1)\]
This is nothing new, your phone does something similair:


A language model on its own only produces text. You read it, you decide, you act.
An agent is the same model wrapped in a loop that lets it act: it can call tools, read what comes back, and decide what to do next, without you in between.
The difference in one line
Same model. The capability is in the loop, not in the language.
flowchart LR G["Goal<br>your prompt"] --> P["Plan<br><b>what next?</b>"] P --> A["Act<br><b>call a tool</b>"] A --> O["Observe<br><b>read the result</b>"] O --> P O --> D["Stop<br><b>report back</b>"]
The tools are ordinary software: a web browser, a file system, a SQL query, an API call to Google Analytics or to your Tableau server.
The model chooses which tool to call, and when to stop. That is the whole difference, and it is also the whole risk.
The useful measure is not “how clever” but how long a task an agent finishes unsupervised.
Read it as a trend, not a prophecy. The benchmark tasks are software tasks with clean pass or fail criteria. Almost no marketing question is like that.
What 50% means
An agent that finishes a five-hour job half the time still needs somebody who can tell which half they got.
Agentic browsing has moved from demo to traffic source. Adobe, across over a trillion visits to US retail sites:
Your analytics now contain a visitor that reads your site rather than looks at it. It ignores your hero image, your colour scheme and your carousel, and reads your structured data instead.
That is a new segment. It has to be identified, attributed and defended in a report, exactly like any other. We come back to it in the attribution and segmentation lectures.
They do not fail loudly. A wrong join, a mis-parsed date, a filter quietly dropping half the rows: the agent reports success either way.
They are not reproducible. Run the same prompt twice, get two different pipelines and two different numbers. Your marking, and later your employer’s audit, both need one.
They optimise the task you stated, not the decision behind it. “Increase conversion rate” is satisfied by narrowing the definition of a conversion.
Which brings back the test from Section 1:
What decision would change if this number were different?
An agent cannot answer that for you, because it does not carry the consequence. You do.
There is no version of this module where you do not use an AI assistant, and no version where pretending otherwise would help you.
The policy is simple:
“The AI produced it” is not a defence here, and it will not be one in a job.
If an assistant makes those decisions for you, you will not understand your own data later, and it will show.
Delegate the typing. Keep the deciding.

Thanks for your attention and don’t hesitate to ask if you have any questions!
@damien_dupre
@damien-dupre
https://damien-dupre.github.io
damien.dupre@dcu.ie