Illustrative example. This walkthrough is hypothetical and is provided to demonstrate how yas.sh features could be applied to an e-commerce team. It does not describe a real customer, and all figures, metrics, and quotes are illustrative only and do not represent actual customer results.
The hypothetical scenario
ShopFlex Commerce is a fictitious multi-brand online store with over 10,000 active SKUs across three regions. Marketing operates from a central team with country pods, and everything — email, social, influencer, print, packaging — carries links back to product pages.
The problem
Three chronic issues were costing the team real money:
1. UTM chaos. Every pod built links by hand. The analytics account contained Newsletter, newsletter, NL, email-news, and newsletter-july as separate sources for the same channel. GA4 reports were unreadable; channel comparison was guesswork.
2. Broken print QR. Packaging carried QR codes generated at 256px from a free tool. On textured boxes, a meaningful share failed to scan — support tickets mentioned "broken codes" weekly, and a reprint of one campaign cost €4,800.
3. No attribution for print. Even when scans worked, there was no data: no scan counts, no device mix, no way to compare print against email or social.
The requirements
The team wrote down what a fix had to satisfy:
- One taxonomy enforced by tooling, not by a document.
- Batch creation — thousands of links per product feed, automated.
- Print-grade QR with formats suitable for packaging and large-format POS.
- One analytics surface for digital and print, bot-filtered, exportable.
- No per-seat costs that would break the free-trial of the tool inside the team.
The solution
ShopFlex adopted yas.sh in two weeks, in three phases.
Phase 1 — taxonomy + builder (week 1). The marketing ops lead defined the UTM standard (source = platform lowercase, medium = fixed list, campaign = {year}{quarter}-{initiative}) and made the campaign manager the only sanctioned way to build campaign links. Enforcement was instant: the builder can't produce a mixed-case source or a missing parameter.
Phase 2 — API batch creation (week 2). The engineering pod wrote a nightly job that reads the product feed, builds UTM-tagged destinations per region, and calls the links API in batches:
# nightly job — one call per SKU, 60/min rate limit respected
for sku in $(cat feed.txt); do
curl -X POST https://yas.sh/api/v1/links \
-H "Authorization: Bearer yas_live_..." -H "Content-Type: application/json" \
-d "{\"originalUrl\":\"https://shopflex.example/p/$sku?utm_source=$REGION&utm_medium=email&utm_campaign=$CAMPAIGN\",\"customAlias\":\"$sku\"}"
sleep 1
done
The job writes each returned short link back into the PIM, so every downstream system (emails, ads, support templates) picks it up automatically.
Phase 3 — print QR at scale (week 3). Packaging artwork generation switched to 1024px PNGs for small formats and SVG for large-format POS:
curl "https://yas.sh/api/v1/qr?url=https://go.shopflex.com/$sku&size=1024&format=png" -o print/$sku.png
Each printed code points at a dynamic short link, so campaign retargeting never requires a reprint.
Results after 90 days
| Metric | Before | After |
|---|---|---|
| Properly tagged campaign links | ~15% | 99.8% |
| GA4 source rows for email channel | 5+ | 1 |
| Print QR scan-failure tickets | weekly | 0 in 90 days |
| Print attribution data | none | full series + devices |
| Link creation for new SKU | ~4 min manual | 0.6s automated |
| Reporting cycle | 3 days of cleanup | 15 minutes |
The channel comparison that used to be impossible became the opening slide of the monthly review: email at X clicks, social at Y, print at Z — one axis, bot-filtered, no arguments.
What the team says
"The taxonomy fight just disappeared. The builder enforces it, the API scales it, and the analytics settle it. We spent three years trying to fix UTM hygiene with a document; it took one week with a tool that does it by construction."
— Head of Marketing Operations, ShopFlex Commerce
Lessons for other teams
- Enforce taxonomy with tooling, not documents — a builder that can't produce bad links beats a guideline nobody reads.
- Print QR is an engineering problem — size, resolution, quiet zone, and dynamic targets are all decisions, not defaults.
- Batch APIs change workflow math — 10,000 links is a job for a script, and the rate-limited API makes the script safe.
- One analytics surface wins — when print and digital report to the same pipeline, channel budget debates end.
Start where ShopFlex started
The same building blocks are free: the campaign manager for taxonomy enforcement, the links API for batch creation, and the QR endpoint for print assets. The UTM taxonomy guide is the standard ShopFlex uses — copy it.
What standardizing UTM means in practice
This is an illustrative walkthrough of a realistic problem — not a claim about a specific client. The principle it demonstrates is UTM standardization: every link an e-commerce team publishes carries a consistent, pre-agreed set of UTM parameters (source, medium, campaign, content) so that all the clicks from a campaign merge cleanly into one analyzable set. Without standardization, marketing tools and a few individuals produce utm_source=facebook, utm_source=FB, and utm_source=Social as three separate rows, and the report fragments into noise. The walkthrough shows how a naming convention fixes that.
Why clean attribution matters for e-commerce
For e-commerce, attribution is revenue: knowing which source and campaign actually produced sales decides where the next budget goes. Clean UTM parameters make that attribution trustworthy. When every link is tagged with the same scheme, the analytics tool can group by source, medium, and campaign and report true performance; when the scheme is inconsistent, the numbers fragment and the decisions built on them are guesses. The UTM naming convention guide is the systematic version of this same idea, and the referral vs campaign vs UTM traffic material explains why clean traffic attribution is the difference between real and misleading ROI.
The practical discipline
Standardization does not happen by itself; it requires the same small disciplines shown throughout these guides. Agree on the tag set and casing in advance, make links easy to create with the scheme pre-filled, and review the analytics periodically to catch drift (a new tool or person introducing a variation). Consistency here is a maintenance habit, not a one-time setup. The bulk creation workflow shows how to apply a consistent scheme across many links at once, and the link management material covers keeping it consistent across a team.
Why this transfers beyond the example
As with any illustrative scenario, the value is in the transferable principle rather than the specifics: decide your taxonomy, apply it consistently, and measure the result. Whether the team is e-commerce, an agency, or any multi-channel marketer, clean attribution is what turns click data into trustworthy ROI. That is the lesson the walkthrough is designed to convey.