We are an affiliate: if you order from Growth Guys using this code we earn a commission, at no extra cost to you. We are not Growth Guys and have no ownership of or role in the company.
A code issued to acquire a specific customer -- a first-order welcome, a one-time recovery offer -- is built to be short and often single-use.
A code issued to acquire a specific customer -- a first-order welcome, a one-time recovery offer -- is built to be short and often single-use. A code published as a standing arrangement is maintained because it is doing continuous work. Lifespan follows purpose, and purpose is usually visible from where the code was published.
It is undated. Those are different things. An undated code can stop working at any time without anything on any page changing, which is the entire reason a dated reading has value: it narrows when the code was last known to work.
A code appearing in a seller's own checkout flow is doing acquisition work. One circulated through third parties is doing reach work and is usually maintained longer, because withdrawing it leaves stale references everywhere.
Sellers adjust how offers combine far more frequently than they withdraw a code. A code that still applies but no longer combines with something has changed materially while appearing unchanged. A test recording only whether the code was accepted will miss this; one recording the resulting total will not.
A code that still applies but at a different percentage has changed in the way that matters while remaining active by any test that only checks acceptance. This is the single most common way a published figure goes wrong.
The total, not the percentage. A percentage can be recomputed from a cart total; a total cannot be recovered from a percentage, and it is the total that was actually observed.
That a code worked at a stated time, on a stated cart, at a stated total. Everything beyond that is an expectation about the future, and should be written as one.
Codes end when a seller decides they end, and no published duration is binding unless stated as a term. A code described as permanent is describing an intention.
Whether a code works today is answerable only by a test today. Any claim about current validity that is not attached to a recent date is an inference from the past.
The claims on this page about why some codes persist for years and others die in a week can be checked against sources outside this site: