eCommerce case studies told with context and verifiable data
A single result does not explain the work behind it. To understand a project you need the starting situation, the period analysed, the activities, the constraints and the sources used.
Zeno Web publishes case studies only when the story can be told with verifiable data and the client's consent. We do not use invented projects, percentages with no basis or examples built to support a sales promise.
Our first case studies are in preparation: here is the standard they will meet
There are no published cases on this page yet. We would rather leave it empty than fill it with generic examples. The cases we publish will be projects we followed directly, with the explicit consent of the company involved.
Every published case will state, explicitly:
- The source of the data: GA4, Search Console, the platform back office, the advertising platform or the ERP, listed item by item.
- The reference period: comparable time windows, flagging seasonality, promotions or events that may affect the reading.
- The measurement method: how the metric was calculated, what it includes and what it excludes.
- The scope of our work: what we did and what depended on the client or on third parties.
- The limits: what the case does not prove and why it cannot be transferred automatically to other projects.
Until these elements can be verified, the case is not published.
What a case study must contain
The context
Industry, business model, platform, catalogue and any situation needed to understand the project, without disclosing confidential information.
The initial problem
The issue is described through evidence: data, errors, processes, limits or agreed goals.
The scope of the work
The case study separates what Zeno Web delivered from what depended on the client, other suppliers or external conditions.
The activities
Development, SEO, campaigns, automations, CRO or integrations are described without turning the story into a list of services.
The period
Every comparison states consistent time windows and flags seasonality, promotions or other relevant factors.
The sources
Analytics, the eCommerce platform, advertising, Search Console, CRM or ERP are named as the origin of the data, when used.
The results
Metrics are tied to the goal and come with the limits of interpretation.
A case study shows what happened in a specific context. It is not a guarantee of results for other projects.
How we select the projects to publish
A project can become a case study when:
- the client authorises publication;
- the scope can be reconstructed;
- the sources are available;
- the period is long enough;
- the metrics are consistent;
- confidential information can be protected;
- the story offers something useful to learn.
Not every project has to become a public case. The quality of the documentation matters more than the quantity of content.
Want an opinion on your specific case?
Thirty minutes of conversation, no sales pitch: tell us your situation and we will tell you how we read it.
No commitment: if now is not the right time, we will tell you.
Technical, marketing and organisational results
A project can produce different kinds of results.
Commercial results
Revenue, margin, average order value, acquisition or repeat purchase, when measurable and authorised.
Marketing results
Visibility, traffic quality, conversions, costs and the performance of automated flows.
Technical results
Speed, stability, errors, upgradeability and the quality of release processes.
Operational results
Less manual work, fewer synchronisation errors or shorter handling times, when there is a reliable measurement.
A case study avoids attributing to a single activity results produced by several factors.
From a real case to your project
A case study can show the method and suggest questions, but it should not be used to propose the same solution automatically.
To understand our overall approach you can explore the eCommerce agency. To analyse a specific situation you can request an eCommerce audit. To turn data and goals into a roadmap you can consider strategic eCommerce consulting.
Frequently asked questions about case studies
Only when we have permission. In some cases a project can be described anonymously, as long as data and context stay real and do not make confidential information identifiable.
We use the sources available for the project and document the period, the metric and the comparison criterion.
Not every project has enough data, consent or a suitable period. We prefer a few well-documented cases to a collection of examples that are hard to verify.
There is no guarantee. Catalogue, market, margins, team, platform and investment make every project different.
You can use the filters when real content exists. Without a specific case, the conversation starts directly from your model and your data.
Want to start from your eCommerce data?
With Shop Analyzer you can analyse your online store on your own and see what comes up, before you even talk to us.
No commitment: if now is not the right time, we will tell you.
