A Thai food brand runs a three-hour live from 8 to 11pm, the window most of its buyers are actually on the app. The session closes at a number the team can live with, everyone posts the screenshot, and the next session is planned the same way. Nobody opens the TikTok live commerce analytics behind that number, so the harder question never gets asked: the three hours were not one session. They were three, and only one of them worked.
The total cannot show that. A session where hour one produced most of the GMV and hours two and three produced almost nothing looks identical, in the summary, to a session that sold steadily for three hours. Same total, opposite diagnosis, opposite fix. One needs the opening improved, the other needs the second hour rebuilt.
This is written for the brand or agency running live commerce in Thailand with a team of ten to fifty, where a session is planned weeks ahead and a dead hour is expensive. It is about splitting one live into its hours, reading peak viewers and GMV side by side, and knowing which of those two numbers is the one that failed.
Why a flat total hides the hour that died
TikTok live commerce analytics start with the session. GMV, orders, average order value, conversion rate, viewers, watch time — all of it summarised per broadcast. That summary answers “was this session worth running” and nothing else. It cannot answer “which part of it should we do differently”, which is the only question that changes next week.
In Thailand the shape of a session is fairly predictable. Viewers climb through the first twenty minutes, hold, then drop after 10pm as the audience moves off the app. A session with a strong opening and a collapsing middle hits the same total as one that grows steadily, and the second is the healthier business even though both look the same on a dashboard.
The fix is not more metrics. It is one metric at a finer interval: GMV per hour, read next to peak concurrent viewers for that same hour. Two numbers, one interval, and the session stops being a single verdict.
Three numbers per hour, and which one is lying
Every hour of a live produces three things worth looking at: how many people were watching at peak, how much of the product they clicked, and how much of that click became an order. The mistake is treating them as one signal. They fail independently, and each failure has a different repair.
| What the hour shows | Most likely cause | What to change next session |
|---|---|---|
| Peak viewers low, click rate normal | Nobody was brought in — the feed had no reason to stay | Move the paid traffic push into this hour, or move the session earlier |
| Peak viewers fine, click rate low | The product was not shown, or was shown without a reason to tap | Put the product on screen in the first minute of the hour, not the last |
| Views and clicks fine, orders low | Price, stock, or checkout friction — the intent was there and died at the end | Check variant availability and any COD restriction before blaming the host |
The third row is the one Thai food sellers miss most, because food has a specific failure that does not look like a failure. A viewer taps the product, sees the variant is out of stock in their province, and leaves without complaining. The session reports a good click rate and poor conversion, which reads as “the host did not close” when the actual cause was inventory.
So the rule is: never read hourly GMV alone. Read it beside peak viewers and click rate for the same hour, and only accept “the host lost them” after the other two are ruled out.
Reading a dead hour without guessing
Open the live detail for the session, sort by GMV, then look at the hourly split rather than the session total. The hour with the largest gap between its share of viewers and its share of GMV is the hour to work on. If it held twenty percent of the viewers and produced four percent of the GMV, that is not a slow hour, that is a broken one.
The second pass is to check whether the dead hour is the same hour every session. Two dead sessions in the same slot is a scheduling problem. The same session dead in different hours, with different products, points at the show itself — pacing, product order, or a host who runs out of things to say ninety minutes in.
DAMI’s live detail carries this split directly: session basics, transaction metrics including GMV and average order value, interaction and traffic metrics with peak concurrent viewers, and GMV per hour, with sessions sorted by live GMV so the outliers surface first. The point of pulling it is not to build a report. It is to answer one question per session — which hour, and why — and then change exactly one thing in the next one.
A brand running two sessions a week on the same product can use this to test product order instead of guessing. Put the strongest item in the second hour instead of the first, run the session again, and compare hour two against itself across the two sessions. That is a clean comparison; comparing whole sessions never is, because the audience differs each night. DAMI’s live overview keeps that hourly trend across sessions, so the comparison is against last week’s hour two rather than against a number somebody remembers.
Where hourly data stops being useful
Two limits worth stating before this becomes a habit.
The first is sample size. Under roughly two hundred viewers at peak, an hour’s conversion rate is noise — one buyer deciding differently moves the number more than any change you made. At that size, watch the trend across a month, not the hour.
The second is that hourly data explains a session, not a catalogue. If the product is wrong for the market, every hour will look mediocre and the split will tell you nothing useful. Food sellers in Thailand hit this when they bring a flavour that tests well in Bangkok but not in the provinces; the session data will show a flat, slightly disappointing night and no hour that stands out.
DAMI can also show which creator or video drove the session’s traffic, which is the next question after “which hour” and usually the more expensive one. The live commerce benchmark data is the place to check whether a session’s numbers are normal for the category before treating an hour as broken.
FAQ
Should I run shorter sessions if one hour always underperforms?
Usually yes, and sooner than teams expect. A two-hour session that holds attention beats a three-hour one with a dead final hour, because the algorithm reads the drop as declining interest and stops pushing the room.
Is GMV per hour the same as hourly revenue?
Not exactly. It is GMV attributed to that hour, before cancellations and refunds, which in Thailand with cash on delivery can take several days to settle. Treat the hourly figure as a shape, not as money.
What if peak viewers and GMV peak in different hours?
That is the most useful signal in the whole session. Traffic arriving after the buying hour means the promotion is pulling people in too late, and moving the push thirty minutes earlier is usually the cheapest fix available.
Start with one session. Pull the hourly split, find the hour where the viewer share and the GMV share disagree most, and change one thing about that hour — the product on screen, the timing, the offer — before the next broadcast. The live selling playbook covers what to put in the hour once you know which one is broken; doing both at once, without the data, is how teams end up rebuilding a session that was never the problem.
If the roster behind the session is the fuzzy part — you have creators booked but no clear read on which of them actually converts — the DAMI workspace starts from the creator list rather than the broadcast, so the next session is planned around people who have sold before instead of whoever was available.
