Conversion Tracking Problems Businesses Forget to Check
Conversion Tracking Problems Businesses Forget to Check
Installed is not the same as working
Your developer set up the tracking. You saw a few numbers in GA4. Everyone moved on.
Months later, you are making decisions on those numbers. Which ads to keep. Which channel to cut. Where to spend next month.
Here is the problem. Conversion tracking problems rarely show up on the day of installation. They creep in afterwards, quietly, when something else on your website changes. Nothing looks broken. The numbers just stop being true.
These are seven things small businesses almost never check after installation. If you set up your tracking recently, read the six setup mistakes we see most often first. This post is about what goes wrong later.
1. A speed or cache plugin delays your tracking
Speed plugins make websites faster by delaying scripts until a visitor scrolls or clicks. Great for speed. Bad for tracking. If your tracking script is one of the delayed ones, visitors who land and leave quickly are never counted.
What to check. Look for settings like “delay JavaScript” or “load JS deferred” in your cache or speed plugin. If they are on, add Google Tag Manager to the exclusion list. Then test again.
2. Your WhatsApp button changed
Your tracking was built to catch clicks on a wa.me link. Then someone installed a new floating WhatsApp button. That button uses a different link format, like api.whatsapp.com, or opens the chat a different way. Your trigger is still waiting for wa.me.
What to check. Click your WhatsApp button in Google Tag Manager’s Preview mode and see if your tag fires. If you build the trigger on links that contain “whatsapp” instead of only “wa.me”, most button changes will not break it.
3. Your form was changed or replaced
The form tracking worked because the old form opened a thank-you page. The new form shows a small “Thanks!” message on the same page instead. Or it moved into a popup. The form still works for customers. The tracking does not.
What to check. After any change to your form, submit a test enquiry and confirm the event appears in GA4 Realtime. If your form no longer loads a new page, your trigger needs to change too.
4. Your payment gateway is stealing the credit
This one is very common for Indian businesses. A customer clicks your Instagram ad, adds to cart, and pays through Razorpay, PayU or Instamojo. Then they return to your thank-you page. GA4 sees that return visit as a new visit from the payment site.
So the sale is credited to the payment gateway, not your ad. Your Instagram campaign looks like it sold nothing.
What to check. In GA4, look at your traffic sources. If you see razorpay.com or a similar payment site sending you “traffic”, that is the leak. Fix it in GA4 under Admin, Data streams, your website, Configure tag settings, then List unwanted referrals. Add your payment gateway’s domain there.
5. Your links have no labels
You share your website link in your Instagram bio, WhatsApp status, email signature and LinkedIn posts. GA4 often cannot tell where those visits came from, so many of them land in “Direct”. It looks like people typed your address from memory. They did not.
What to check. Add UTM tags to every link you share. These are short labels at the end of a link, like ?utm_source=instagram&utm_medium=bio. Google’s free Campaign URL Builder makes them in a few seconds. Then your reports show exactly which place sent the visit.
6. GA4 is quietly deleting your history
Out of the box, GA4 keeps detailed data for just two months. After that, you cannot dig into it in custom reports. Most businesses only find out when they try to compare this festive season with the last one.
What to check. In GA4, go to Admin, Data collection and modification, then Data retention. Change it from 2 months to 14 months. It takes a minute and only works from the day you change it, so do it today.
7. You do not own your own tracking
Your developer or agency created the GA4 property, the Tag Manager container and the Meta Pixel using their own login. Everything works until they move on. Then nobody can fix anything.
What to check. Make sure your own business email has admin access to GA4, Google Tag Manager and Meta Business Manager. Add your developer as a user. Do not be a user on your own accounts.
When to check your tracking again
You do not need to check every day. You need to check after changes. Run a quick test whenever you:
- Update or add plugins, especially speed, cache or security plugins
- Change your WhatsApp button, form or contact page
- Add a new payment option or checkout step
- Add a cookie consent banner, which can stop tags from firing until a visitor accepts
- Redesign or rename any page
- Change developers or agencies
And once a month, spend ten minutes comparing GA4 with real life. If GA4 says five enquiries and your WhatsApp says twenty-five, something is leaking.
The numbers should match your business
Tracking is not something you install once. It is something you keep honest.
The good news is that most of these fixes take minutes. The hard part is remembering to look.
Not sure if your tracking still matches what is really happening in your business? Message us on WhatsApp and we will tell you honestly what we find. Got questions first? Read our FAQ.
