GSK Pro Login/Registration metrics

Hi @tonyhutnyk,

That's a link to a report- no-one will be able to see that unless they have access to your Analytics account, so you'll need to add a screenshot ideally. 

Regards the question, it's almost impossible to say- if Login & Registration metrics are simple events, & not set by a segment, then if the data isn't there then it suggests the events broke, possibly because of on-site changes, or TMS changes, or a lot of other possible reasons.

If it's a segment such as 'visits to page X' count as a registration or login, then it's possible the page has changed & they no longer hit those pages after a login or registration. Again, there's quite a lot of reasons why that could have broken too. 
If you can let us know:

Are these simple events or segment-based metrics?

If event based, do you have segments applied to your report? If you remove these, does the data show?

If segment based, what are the definitions?  

Does the data still fire but intermittently/at low volumes, or is it 0 since December ’24?

Hi @tonyhutnyk 

if the Login/Registration metrics stop at December 2024 even after selecting “This Year,” it likely means no relevant data has been collected since then. I would check the following -

1. Are these metrics based on direct events (e.g., eventX = Login) or built using segments (e.g., visits to a specific URL or success page)?
   or, If they're event-based, it’s worth checking whether those events are still firing , a recent site or TMS update might have broken the tracking.
   or, If they're segment-based, verify whether the criteria (e.g., page names, URLs, or form submissions) are still valid. Page changes often silently break segments.
   
   

2. Try removing any applied segments or filters in the Workspace and check if the raw event volume appears for Jan 2025 onward.
   
   

3. Use the Debugger or Network tab to confirm whether the login/registration events are still being triggered on the site.

If you’re seeing a hard stop in data at a specific date, it usually points to either -

• A tracking issue (tags not firing, changed element IDs/classes, etc.)

• A change in logic or structure used in the report (e.g., outdated segment rules)

• Or a delay or misconfiguration in data ingestion (less likely, but worth checking with your admin)

Hope that helps!

Hi @tonyhutnyk ,

• Check the Report Suite

  • Make sure the correct report suite is selected (top-right of the workspace).

  • Sometimes, older or QA suites don't have 2025 data populated.

• Check Data Availability

  • Go to Admin > Report Suites > Data Feeds (or check with an Admin)

  • Confirm if data collection is active for 2025 for the report suite.

  • Ensure no data processing issues happened around Jan 1, 2025 (sometimes caused by processing rule misconfigurations or classification breakdowns).

• Manually Select 2025 Date Range

  • Instead of "This Year", try a custom range:

    • Click the date picker

    • Select Custom Date Range

    • Manually choose Jan 1, 2025 – Today

  • Check if this returns any data.

• Check Workspace Panels and Filters

  • Look for any panel-level filters or segment filters that might limit data to 2024.

  • For example, a panel might be hard-coded to Dec 31, 2024.

• Segment or Metric Configuration

  • Some metrics (like "Login Events" or "Registration Success") may rely on segments or classifications that were deprecated or renamed in 2025.

  • Check if those segments still apply to 2025 events (ask a solution architect if unsure).

• Validation in Reports

  • Go to Reports > Real-Time Reports or Reports > Reports & Analytics > Traffic Reports

  • Check if daily visits or events are being logged in 2025

  • This can confirm whether data is coming in at all.

As others have said, it sounds like something broke / changed in your site's tracking in Dec... either resulting in the data not being capture (in which case there is no getting this data back for the last 7 months), or the segment / calculated metric used to identify registrations no longer works due to changes in the tracking.

If it's a segment / calculated metric issue, you or someone more familiar with the report / how the site is tagged, can make an update to the definition and fix the report.

If the issue is data stopped tracking, while that info will be gone, you can sometimes use a segment / calculated metric as a proxy to get data for the time frame where the tracking was broken, and you will need to get your developers / implementation specialists to fix the tracking problem so that it starts collecting again.

Unfortunately, we can only offer surface advice and condolences, since none of us have access to you site or your reports to see the issue.