SepetLine lifted ROAS 3.4x in 90 days
Fast-fashion D2C brand SepetLine could not read true ROAS with spend split across agencies. Tecrube unified server-side measurement, catalogue health and SKU-level budget — 3.4x ROAS and a 36% CPA cut in 90 days.
Key metrics
3.4x
ROAS lift
36%
CPA reduction
90 days
measurement window
Story highlights
- Double-counted conversions and feed gaps cleaned up
- Low-stock SKUs paused automatically
- 3.4x ROAS and 36% CPA cut
- Optimisation fell from hours to minutes
- Sales and performance shared one ROAS score
SepetLine is an Istanbul-based fast-fashion D2C brand that grew on rapid catalogue refreshes since 2023. Inventory turns were high, gross margins thin, and weekly launches forced constant creative production. Google Shopping and Meta catalogue campaigns sat with separate agencies, so the same SKUs often competed against each other on bids.
Marketing director Elif Kaya relied on four weekly spreadsheets; pixel and GA4 purchase events disagreed. Post-return net ROAS vanished, out-of-stock items stayed live, and high-return styles were scaled by accident. Digital marketing spend rose while profitable order share stalled.
This case study shows how Tecrube repaired measurement, matched the product feed and enforced approved budget rules in one panel — making true ROAS visible and cutting weak SKUs without inflating net spend.
Below: the challenge, the solution and the 90-day outcome, with concrete steps ecommerce teams can reuse for ROAS, CPA and catalogue health.
Delivery journey
Four steps from discovery to proof
Every case study follows the same discipline: clarify measurement, set up, optimise, prove the outcome.
Measurement repair
Pixel, GA4 and server-side orders mapped to one score.
Catalogue setup
Shopping and Meta relaunched with approved budget rules.
Creative rotation
Fatigued creatives paused; winners funded by SKU cluster.
Scale
3.4x ROAS and 36% CPA cut confirmed in 90 days.
Challenge
Shopping and Meta catalogues ran in two teams; overlapping bids inflated CPC while attribution panels disagreed on order counts. Pixel and GA4 purchase events were out of sync — some orders fired twice, others never landed. Creative fatigue was spotted monthly, not weekly, so CTR-decay groups quietly burned budget. SKUs below stock thresholds stayed in the feed; high-return models scaled on a cheap-CPA illusion. Weekly reporting took four hours and nobody could answer the CFO’s net ROAS question from one screen. Unapproved budget bumps vanished in Slack and panic spend followed every dip.
What we did
Tecrube mapped the conversion API and product-feed matching into one order score, clearing double counts and missed events. Catalogues relaunched under approved budget rules; low-stock SKUs paused automatically and high-return models hit caps. Daily creative-health signals rotated fatigued assets; winners moved into SKU clusters. Google Ads and Meta Ads were watched in the same panel with justified, approved scale-ups. Sales and performance shared one ROAS/CPA score — the Excel merge disappeared. Unapproved spend stayed blocked and launch calendars followed panel scores.
Outcome
By week nine ROAS rose 3.4x and CPA fell 36%. Profitable order volume grew on the same net ad budget while high-return SKU share declined. Weekly optimisation dropped from four hours to about twenty minutes. Stock and margin meetings ran on panel scores, not guesswork. The next two launches needed less creative churn because winning formats were already known. The CFO finally signed off on net ROAS from a single screen.
For the first time we saw which products truly made money. Budget follows the panel now, not guesses.
Modules used
Key takeaways
- Do not scale ROAS before measurement and feed health are fixed.
- Stock and return signals must steer budget.
- Blocking unapproved spend raises both speed and trust.
- One shared score ends the sales-versus-performance fight.
Make the next story yours
Apply the same method to your channels
Start free — unify tracking, campaigns and sales follow-up in one panel. No card required.
Frequently asked questions
Short answers on timing, channels and how to get a similar outcome.
This story used a 90-day window. Tracking repair finishes in days; stable ROAS usually clarifies within a few weeks.
Google Ads Shopping and Meta Ads catalogues managed inside Tecrube.
Return and stock fed the score; weak SKUs were capped or paused.
Create a free Tecrube account, connect your feed and conversions, then run a measurement health check.
More case studies