Source Canvas Grid

Client notes

What people said after a source was named, or after one refused to be named.

These are notes from engagements on this site — mapping, pre-launch checks, paid-versus-organic reviews, first-window readouts, and window advice. They mention the awkward parts on purpose.

Launch attribution mapping

The map named our campus booths and the Malay listing as sources, which our paid report had been swallowing. We cut a campaign that only looked strong because it spoke last. The booth still bothers me — we had no unique link for it, so some of those installs remain guessed — but at least we stopped pretending the ads had done that work.

Nadia Rahman, Growth lead, education app · Johor Bahru

Pre-launch measurement setup

They made us write the family WhatsApp ask as its own line. I thought that was fussy until opening day, when those opens would have sat inside paid search. The punch list was blunt and short. We actually finished it.

Wei Jie Tan, Founder · Skudai

Paid versus organic source review

I came in convinced our TikTok burst had carried the first week. The review showed store search rising on days we had gone quiet. That was uncomfortable in the room. It was also the first time I had numbers I could take back to the founder without hedging.

Priya Menon, In-house marketer · Iskandar Puteri

Attribution window advisory

I had left a thirty-day click window on a four-day launch burst because that was the account default. The advisory letter was two pages and named the exact days the burst would keep stealing later store visits. Changing the setting took longer than the letter, which says more about our account access than about the advice.

Amira Salleh, Media planner · Johor Bahru

Two colleagues in conversation during a working session

A longer note

Fourteen days after a quiet store release

We released on a Wednesday because the listing cleared later than planned. By Friday the paid dashboard looked healthy and the team was ready to raise budgets. Source Canvas Grid froze days one to fourteen and read them against a list we had not written down: a weekend mention by a Kluang food page, staff installs from the operations group, and store search for the Malay name. The paid burst was not empty. It was also not the doorway we had been celebrating. We kept the burst, shortened the claim window, and put the food-page mention on the next map as a named referral. The second fortnight’s spend was smaller and less theatrical. Retention from store search held. That was the useful part.

Hafiz Osman, Product owner, local services app · Kluang · First-window source readout

The ninety-minute session was tighter than I wanted — I would have liked another pass on creator posts that landed after day fourteen — but the fourteen-day picture was clear enough to hold the next spend. Staff installs were finally separated instead of looking like early traction.

If your first-week report already looks complete, that is a reason to write, not a reason to wait.

Request a reading