Metrics Media Help Center

How can we help you today?

Search 20 guides or browse categories below to find answers instantly.

Back to Knowledge Base

Best Practices for Reporting Website Bugs & Technical Glitches

Verified Guide • • 2 min read

Help Our Engineers Solve Bugs in Record Time

When our engineering team can replicate a bug instantly, they can usually fix it within minutes. Providing specific, structured details eliminates endless back-and-forth emails and ensures your website stays bug-free.

Report a Bug

The 4 Details Developers Need in Every Bug Report

1. Exact Page Link (URL)

Paste the exact URL where the issue happens (e.g. https://yourdomain.co.nz/products/item-a) instead of saying "on the shop page".

2. Step-by-Step Instructions

Explain what you clicked: "1. Clicked Add to Cart → 2. Clicked Checkout → 3. Received a blank white screen."

3. Browser & Device Info

Let us know what device you used: e.g. iPhone 15 on Safari, or Windows 11 on Google Chrome.

4. Screenshot or Screen Video

A screenshot highlighting the error, or a quick 30-second screen recording (using Loom or your phone) is worth 1,000 words!

Expected vs Actual Behavior

In your ticket description, clearly state what should have happened versus what actually occurred. This clarifies design intent instantly!

Did you find this article useful?

Your feedback helps our New Zealand team continuously improve our documentation.

Still have questions or need assistance?
Our technical support team is online Monday – Friday, 9:00 AM – 5:00 PM (NZST).

Related Articles