Klaviyo signup form best practices: 5 checks

A new visitor lands on a product page, reads one line, and a box appears over the product. If the box shows before the shopper has looked at anything, they have no reason to give an address, so they close it, sometimes with a tap that misses the small close control. Timing rules built for a laptop, such as showing a form when the cursor leaves the window, do not fire on a phone, where there is no cursor. The form then covers the button the shopper came to press. The store owner has seen the form many times and does not notice the screen is blocked.

• Timing: does the form wait until a shopper has scrolled or viewed a product?
• Close control: can a thumb reach it on a phone without touching a field?
• Covered button: does the form sit over add to cart or the checkout button?
• Offer: does the discount in the form match a code the store accepts?
• Phone field: does the consent line match the messages you will actually send?

Wrong: the form opens the moment the page loads, before the shopper has read the product name. Right: the form opens after the shopper has scrolled past the first image or spent a short time on the page, and it never opens over the product they are reading. On a phone, use triggers that do not need a cursor. The test is simple. Open the store on a phone in a fresh session, scroll once, and see whether the form waits for you or arrives on top of the first product photo. If it arrives before the photo has loaded, move it.

A form can promise a welcome discount that the cart then rejects. One cause is that the owner tests with a code that works for them, such as one with no usage limit, while the form's code carries a minimum order or an expiry date that the shopper has not read. Enter the code from the form in a fresh cart on a phone, and check that the discount applies to a product that is in stock. A simulated visitor can add an item and type the code, and the report shows the step where the code fails. It cannot tell you whether the discount is a good offer for your margins.

A form that asks for a phone number has to say what the number will be used for, and the messages you send should match that wording. A visitor cannot receive a text message, so a simulated run can show the phone field and its wording, but not the message itself. If the form needs a code sent by text, the run stops at that step. Read the consent line aloud, then confirm that any welcome email the form sends arrives in an inbox you control and names the same offer.

Store themes, announcement bars and chat widgets change after launch, and a new banner can push the add to cart button under a fixed form. Rerun the first-visit path on a phone after each theme or form change, and test the offer's code again whenever the discount changes.