PERFORMANCE CHANGE

Before and after

Sub-line Prior-period cost per conversion to be added once historical data is verified.

BEFORE Account-level reporting only

AFTER $10 per conversion, tracked per product

Once you pull the historical figures, the stronger version of this block is a straight cost-per-conversion pair, matching how the JaskAuto grid card reads.

---

Brief about the Problem

JaskAuto sells replacement parts across a wide automotive catalogue, and was already spending around $50,000 a month on Google Ads. The budget was not the issue. The account was organised the way the catalogue is filed rather than the way people buy, so broad category campaigns pulled volume at thin margin while high-intent part number searches competed for the same budget inside the same campaigns. Nobody could say with confidence which products were carrying the account.

---

Case Study Unveiled

At this level of spend, that kind of vagueness is expensive. A few points of return either way is real money every month, and the team had no product-level view to make the call on. Conversion values were in place but had never been checked against what the business actually books, which meant any decision to scale would have been made against numbers nobody had verified.

---

What Did We Do

We started with measurement rather than structure. Conversion values were checked against real bookings before a single campaign was touched, because scaling spend against unverified numbers is the most common way a large account quietly loses money.

From there we split high-intent searches, part numbers and specific components, away from broad category traffic so each could be bid on its own terms. Someone typing a part number is close to buying. Someone typing a category name is not, and the two should never share a budget.

Campaigns were then rebuilt around demand that repays the spend, which meant capping some well-trafficked categories and giving room to smaller product groups that returned better. Search term reviews and negative lists now run every week, because on a catalogue this wide waste accumulates fast.

---

The Results

The account now delivers over 4,800 conversions a month at roughly $10 each, on approximately $50,485 in monthly spend. Impressions grew by 46,659 over the prior period while cost per conversion held, so the additional reach came without paying more for each result.

Reporting runs at campaign and product level rather than account level, which means budget decisions are made on margin instead of click volume. The weekly search term routine is what holds the position in place month after month.

---

Before this page goes live

Confirm the 6X ROAS figure. Your earlier note put JaskAuto at roughly 6X return on ad spend, but the account view you sent has no conversion value column, so that number must come from your own reporting rather than from the screenshot. Either confirm it and add it to The Results, or leave it off this page.

Use the USD account view, not the rupee one. The rupee view spans more than one client, shows every headline metric declining, and includes a campaign paused with all ads disapproved.

Mask the campaign column on any screenshot. The visible campaign names are JaskAuto product lines, and one earlier view named a different client outright.

Replace the stock imagery. The Khatabook page uses generic laptop and globe images that say nothing about the work. For JaskAuto, a masked account screenshot in that slot would carry far more weight than stock photography.