Why conversion rate dropped: check what changed

A rate is a ratio, so it can move with no change to the page at all. A new campaign can bring visitors who came for a free sample. A seasonal promotion can bring bargain hunters who never meant to pay full price. A new referral partner can send people who land on a page without the product in it. The same page then looks worse in the rate. A real break looks different: one step stops converting for the traffic that used to buy, often starting on a date you can point to.

• The drop date: what went live on the site, in its apps, or in the payment setup that week?
• Traffic source: did one channel grow fast, and does it convert far below the rest?
• Device and browser: is the drop on phones, in one browser, or on every device?
• Last working step: on which page do the visitors who still buy stop being able to continue?
• Outside services: the status pages of your payment provider and shipping calculator for that date.

Take the same weeks on both sides of the drop and cut them four ways: by date, by traffic source, by device and by new versus returning visitors. Owners often start by rewriting the homepage, because it is the page they know best. That is the wrong order. If the drop sits in one source, the site did not change and the traffic did. If it sits on one device, the cause is a rendering or script problem on that device. Only when the drop appears in every cut is the site the suspect, and then the date tells you which change to look at first.

Ask for the change log for the drop date, including the ones made by someone else. A theme update, a new review app, a changed discount rule or a tag manager script can each alter a step without touching the copy you reread. An expired security certificate is a clean example: browsers show a full-page warning and many visitors leave at once. Check the certificate date, the payment settings and the shipping rules as well. A change you did not make can still break the step, so list everything that touched the store in the days before the drop, not only your own edits.

Some drops affect a slice of traffic. Old links from emails and bookmarks can point to pages that were moved, and a redirect that loops sends the visitor back to the start. A discount code that used to apply may now be rejected at the last step. Those visitors feel like the store stopped working for them, and they are right. The fix is narrow: restore the redirect, or correct the rule. Give the test the old address as its starting point, so it follows the same redirect a visitor from that email would hit.

Releases, theme updates and new scripts can break a step that already works. Run the same path after each release, and after each change to payment or shipping settings, so a break shows up on the day it ships. Paid runs can sign a visitor in with a test account you give, so checkout pages behind a login can be included in the same run.