SiteAud!tLint Support

Opportunity Tracking & Analytics

No custom events tracked

Severity
Opportunity
Impact
Medium
Effort to fix
Medium
Issue code
track_no_custom_events

Why it matters

Only page views are measured. Without events for leads, sign-ups or purchases, GA4 cannot show which pages or channels bring results.

How to fix it

Add GA4 events for the actions that matter (form submit, sign-up, add to cart, purchase) and mark them as key events.

What this means

The site has GA4 or Google Tag Manager, but SiteAud!tLint found only page views: no custom events in the page code, in the GTM containers, or in the requests sent while rendering.

Why it matters

Page views show where people go, not what they do. Without events, you cannot measure the actions that matter: form submissions, sign-ups, purchases, downloads, calls, add-to-carts or clicks on key buttons. GA4 can then report traffic but not results, and Google Ads cannot optimise towards conversions.

GA4's enhanced measurement sends some automatic events, such as scrolls, outbound clicks and file downloads, which are configured in GA4 itself and may not show up in the page or GTM. Check your GA4 settings before concluding nothing is tracked.

How to fix it

  1. List the three to five actions that mean success on the site.
  2. Create events for them, ideally in GTM: triggers on form submissions, clicks or dataLayer pushes from the site, sent to GA4 with clear names such as generate_lead or purchase.
  3. Use GA4's recommended event names where they fit, so standard reports work.
  4. Mark the most important ones as key events in GA4.
  5. Test them in GTM Preview and GA4 DebugView.

Verify the fix

Recrawl. With Render JavaScript on in Crawl settings, events that fire on page load also appear. Improve > Tracking & Pixels lists the events found. See Tracking and pixels audit.

How it affects your score

Tracking issues have their own Tracking score and never lower the SEO site health score. They still appear in the Action Plan, the issues CSV, Slack messages and Linear tickets. A smaller improvement with a modest effect on its own.

Find the affected URLs

Open Crawl > Issues and pick No custom events tracked. Each affected URL is listed with its evidence, and Copy URLs or Export URLs hands the list to a developer. The issue also appears in the Action Plan, ranked by impact (medium) and effort (medium), and in the issues CSV under the code track_no_custom_events. After fixing, run a new audit and use Compare to confirm the URLs moved to fixed.