What Is Clicked At?
Clicked At is the timestamp assigned to a product click recorded on WheelInterchange.com. The field indicates when a user selected or clicked a product link, listing, or other tracked product element.
The alias click timestamp describes the same concept. Unlike bolt pattern, center bore, wheel width, or offset, Clicked At does not describe a physical wheel or vehicle dimension. It is an analytics event attribute stored as a datetime value.
How Clicked At Is Used
A Clicked At value helps organize and analyze product-click events over time. For example, an analytics record might contain:
- The product or listing that was clicked
- The page where the click occurred
- The target vehicle or fitment context, if recorded
- The Clicked At datetime
- Other event information, such as a session or anonymous user identifier
A reporting system can use this timestamp to answer questions such as:
- When did a product click occur?
- How many product clicks happened during a particular day or period?
- Which fitment pages generated clicks during a campaign or traffic period?
- Did clicks occur before or after a page, listing, or interface change?
The timestamp records the event time; it does not by itself confirm that the clicked product fits the target vehicle.
How It Is Measured or Expressed
Clicked At uses a datetime format, combining a calendar date and a time. A value may be displayed in a form such as:
2025-03-08 14:32:10
The exact display can vary. Systems may use an ISO 8601 format, such as 2025-03-08T14:32:10Z, where Z indicates UTC, or may show a local time with a timezone offset.
The timezone is important when comparing events from different systems or creating daily reports. A click recorded late at night in one timezone may appear on a different calendar date after conversion to another timezone. Analytics implementations should document whether Clicked At is stored in UTC, local time, or another standardized timezone.
Clicked At vs. Fitment Data
Clicked At should not be confused with information used to determine wheel compatibility. It cannot establish whether a wheel is a Direct Fit, needs hub rings or a spacer, requires an adapter, or is Not Directly Compatible.
A fitment decision still requires the relevant technical data, which may include:
- Bolt pattern / PCD
- Center bore
- Wheel diameter and width
- Offset
- Brake and suspension clearance
- Lug hardware and wheel geometry
- Tire fitment and vehicle configuration
For example, a Clicked At value may show when someone selected a product described for a particular fitment search. It does not prove that the product matches the target vehicle's bolt pattern or center bore. Those specifications must be checked separately.
Common Analytics Mistakes
- Treating the timestamp as a fitment confirmation: A click shows an interaction, not a successful installation or compatibility result.
- Ignoring timezone handling: Comparing raw timestamps without knowing their timezone can place events on the wrong reporting day.
- Confusing clicks with purchases or outbound visits: A recorded click may not mean the user completed a purchase, reached the destination page, or contacted a seller.
- Assuming one click equals one person: A user may click more than once, and analytics systems may record repeated events.
- Using an incomplete timestamp: A date without a time, or a time without timezone context, may be insufficient for accurate event ordering.
Clicked At is therefore best understood as the recorded datetime for a product-click event. It provides timing context for analytics while remaining separate from the dimensional and hardware data required for wheel fitment.