Back to blog
Seasons2 min read

Reading the first week of Ramadan

Two channels with near-identical totals after three weeks. One is down a third, the other has more than doubled. The total says split evenly, the trend says move the whole budget.
Two channels with near-identical totals after three weeks. One is down a third, the other has more than doubled. The total says split evenly, the trend says move the whole budget.

Week three of Ramadan just closed, and in front of you is the budget split for the final ten nights, the heaviest spending stretch of your year. What's on the dashboard is totals, and totals are the weakest evidence available for this particular decision.

Two channels, same total, opposite directions

Week 1Week 2Week 3Total
Channel A907458222
Channel B4065105210

Read the totals and the two look interchangeable, 222 against 210. Any quick review says split the final-ten budget evenly between them.

Read the direction and the story inverts. A is falling by about a third, B has grown 2.6 times. And the decision isn't about the three weeks that happened, it's about the ten days ahead.

This matters more in a season than at any other time, because demand is elevated for everyone. The level is inflated across the board so it separates channels poorly, and the direction is what still carries information. A channel at 3.0 falling from 6.0 isn't the same channel as one at 3.0 climbing from 1.5, and the two are identical in the table.

Why week one is the week you should trust least

Buying patterns reset when Ramadan starts. Categories that sold through Sha'ban can stop and others begin. Buying moves to late evening. Ad auction costs shift because everyone launches at the same time.

So week one is a transition, not a baseline. Three errors follow from treating it as one:

  • Cutting a channel on week-one data. Prospecting campaigns are still learning, and a channel that opens journeys won't have closed any yet.
  • Scaling a channel on week-one data. Early spikes are usually your existing audience buying sooner, not new demand.
  • Setting the month's pace from week one. Ramadan volume isn't linear, so pacing from the first week will mislead you in one direction or the other.

What week one can actually tell you

Not performance. Three things it reports reliably:

  1. Whether tracking survived the start of the month. The most useful thing to confirm and the cheapest. A destination that went quiet looks exactly like a channel that stopped working, so check delivery before you cut anything. See tracking health.
  2. Whether the shift to late evening happened as expected. If your traffic hasn't moved later, your scheduling or your creative is pointed at the wrong hours.
  3. Direction, from about day five. Not the level, the slope.

Attribution flow and trends are live in Flowfy, so direction per channel is readable across the season alongside revenue by source. Pulling ad spend from your ad accounts is on the roadmap and hasn't shipped, so the return figure behind a trend currently needs your spend from the ad accounts next to your revenue from Flowfy. The year-over-year Ramadan comparison is built by hand, and there's more on that in why the dates lie.

What to do this week

Rank your channels by slope rather than total, and move the final-ten budget on that basis. Rebalance weekly through the first two weeks and daily through the final ten, when one day is worth several ordinary ones.

Tracking

How to catch broken tracking before a month goes by

Tracking rarely fails in a way you can see. A theme update or a lapsed permission, and the numbers drift down and read as a slow week. Here's what to compare, how often, and how to tell when a gap is worth acting on.

3 min read