Goals that do not close themselves when you hit the number
Reaching the target marks a goal as reached and leaves it open. Closing is a separate decision with three possible endings, because a number passed through in week two is not a result.
A goal in Market4 does not close itself when you hit the number. The reading tells you it is reached, the progress figure goes past one, and the goal stays active until somebody ends it. Hitting a target in week two and falling back below it in week three is ordinary behaviour for every metric a marketing goal can be set on, and a system that declared victory the first time a number was passed would be recording a moment of noise as a result.
Reaching a target sets a derived flag and nothing else. Reading the goal list returns three computed fields alongside the stored ones: progress, expressed as a fraction of the distance from the baseline to the target, reached, and the number of days left before the due date. None of them writes anything to the goal. The status stays ACTIVE, the goal keeps being measured, and the agent working toward it keeps working toward it.
Closing is a separate call with a separate argument, and it names which ending happened: ACHIEVED, MISSED or ABANDONED. Those three are kept apart on purpose. Collapsing them into a single closed state would delete the one thing a closed goal is worth reading for, which is which of the three it was. A goal can be closed once.
Progress is measured from where the metric stood when the goal was set, not from zero. A site sitting at 800 organic clicks a month that sets a target of 1,000 has moved a fifth of the way when it reaches 840, not four fifths. Measuring against the target instead would show a customer 90 per cent progress on their first day and would make the bar meaningless for any metric that starts well above zero, which is most of them.
When the baseline could not be measured at the time the goal was set, progress reports itself as unknown rather than assuming zero. Progress is also not clamped at the bottom: a site whose clicks fell after the goal was set is shown a negative number, because rounding that to zero would hide the only fact in the report that needs acting on.
| Goal metric | Where the number comes from | Direction of improvement |
|---|---|---|
| Organic clicks | Search Console | Up |
| Organic impressions | Search Console | Up |
| Average position | Search Console | Down |
| Sessions | GA4 | Up |
| Key events | GA4, as the customer defined them | Up |
| Published posts | Posts published in the window | Up |
| Keywords won | Tracked keywords whose target page is the page Google ranks | Up |
A progress bar that cannot go below zero hides the one thing you needed to know. Here is what measuring from a baseline gives you, and what it costs.
Search Console's Performance report is a rolling sixteen-month window. At month fifteen the first month your site ever had is still inside it, and two months from now it will not be.
Market4 turns one release note into a changelog page, a blog post, a mail-out and a week of social posts — and then tells you which of them brought anyone back.
The list is closed, and every member is a number the product can already read without asking anyone to install anything new. Revenue and sign-ups are missing deliberately: both are the customer's own business numbers, both live in systems this product does not read, and a goal that could only ever report "unknown" would make the whole screen untrustworthy. A goal whose progress cannot be measured is a wish, and a wish rendered as a progress bar is a lie.
Average position is the one metric in that list where down is good, and the direction is derived from the metric rather than stored on the goal. A stored direction is a field somebody eventually sets the wrong way round, and a goal that reported success while a site's rankings collapsed would be the worst outcome this record could produce.
Nothing stops a site holding two active goals on the same metric at the same time. A quarter target and a year target on organic clicks are two different commitments with two different due dates, and a uniqueness rule on the metric would refuse the second one with a database error nobody could act on. The goal list sorts live goals first and the soonest deadline first, so the near one is what you read and the far one is what you are steering toward.
No. Reaching the target sets a derived reached flag and the progress figure passes one, but the goal's status stays ACTIVE and it keeps being measured. Closing is a deliberate call that also names the ending: ACHIEVED, MISSED or ABANDONED. The reason is that metrics cross a threshold and fall back all the time, and a goal closed on that crossing records noise as an outcome.
Because progress is the fraction of the distance travelled from the baseline toward the target, and a metric that fell below its baseline has travelled a negative distance. The figure is not clamped at zero. A customer whose organic clicks dropped after setting a goal needs to see that first, and a progress bar pinned at zero would hide the one number in the report worth acting on.
Both are the customer's own business numbers and live in systems this product does not read, so a goal set on either could only ever report progress as unknown. The goal metrics list is closed and every member is a number already readable from Search Console, GA4, the publishing record or the tracked-keyword record. A goal whose progress cannot be measured is a wish.
MISSED means the goal was still the goal on its due date and the number did not get there. ABANDONED means the goal stopped being the point before the date arrived, usually because the strategy or the product moved. They are two different lessons for whoever writes the next goal, which is why they are stored as two endings rather than one closed state.
A consent banner changes what GA4 can measure, and the reports carry no marker saying so. What the seven consent types cover, what basic and advanced consent mode each do when someone declines, and how to read numbers collected under either.