Revenue processed
Across 230 verified purchases in a 28-day window
E-commerce / Case study
A dormant ad account rebuilt, and the tracking that was never recording
Direct-to-consumer motorcycle parts brand (name withheld). Google Ads & Meta Ads · 28-day reporting window.
Google Ads & Meta AdsBIGSHARK / CASE RECORD
₹25.8LRevenue processed
Across 230 verified purchases in a 28-day window
Direct-to-consumer motorcycle parts brand (name withheld)
The challenge.
The Google Ads account was effectively dormant, and its conversion tag pointed at an account that had been cancelled, so no purchase had ever been recorded against it. On Meta, a spend cap was quietly throttling the entire channel, and performance was read at account level, which hid the fact that one placement was carrying the results while another was losing money on every rupee.
What we did.
Rebuilt the account structure from the ground up, shipped a Merchant Center product feed, ran Performance Max alongside a dedicated brand search campaign, and added negatives to stop the spend that was never going to convert. Repaired conversion tracking end to end, added server-side tracking on Meta so the data survives the browser, and started reading Meta at placement level instead of account level. All reporting is reconciled against the store's own order table rather than against the ad dashboards.
Brand campaign ROAS
Return on ad spend on the brand search campaign
Best product ROAS
On a single product inside the same account
What changed.
| Measure | Before | After |
|---|---|---|
| Purchases recorded by the conversion tag | 0 | 230 |
| Facebook Feed ROAS | Not read separately | 11.98× |
| Instagram Feed ROAS | Not read separately | 0.17× |
The details
that mattered.
- Conversion tag repointed from a cancelled account to the live one
- Merchant Center feed built and maintained
- Performance Max run alongside a separate brand search campaign
- Negative keyword control to cut wasted spend
- Server-side conversion tracking on Meta
- Placement-level reporting instead of account averages
- Spend cap identified and lifted
Source: BigShark’s existing case record. Scope and reporting window are stated where recorded. Results describe this engagement and do not predict future performance.