# page.props.urlParams are timestamped with gateway time when written from client

**URL:** <https://forum.inductiveautomation.com/t/page-props-urlparams-are-timestamped-with-gateway-time-when-written-from-client/103986>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [March 20, 2025, 11:00pm UTC](https://forum.inductiveautomation.com/t/page-props-urlparams-are-timestamped-with-gateway-time-when-written-from-client/103986 "2025-03-20T23:00:29Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![hunterdg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/hunterdg/32/67774_2.png) [@hunterdg](https://forum.inductiveautomation.com/u/hunterdg)\
**Post date:** [March 20, 2025, 11:00pm UTC](https://forum.inductiveautomation.com/t/page-props-urlparams-are-timestamped-with-gateway-time-when-written-from-client/103986/1 "2025-03-20T23:00:29Z")

</div>

I’m sure there’s an explanation for this, but on it’s face, it’s a bit confusing.

if i write to a _page_ prop (urlParams in this case) from a client (browser/designer/presumably workspace), the associated timestamp is derived from the gateway

if i write to a session/view/component prop, the associated timestamp is derived from the client

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [March 21, 2025, 12:08am UTC](https://forum.inductiveautomation.com/t/page-props-urlparams-are-timestamped-with-gateway-time-when-written-from-client/103986/2 "2025-03-21T00:08:33Z")

</div>

I don't see why that is surprising. URL parameters are "bare" where they are received, at the gateway, so naturally will get the gateway's UTC timestamp on their qualified values. Whereas, for any operation involving the browser or designer, those can construct and send qualified values themselves, so would have the UTC timestamp where they were constructed.

(Unless you have non-timezone skew from real time, the difference should be effectively zero. Timestamps in QVs are UTC.)

---

<div class="post-metadata">

**Author:** ![hunterdg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/hunterdg/32/67774_2.png) [@hunterdg](https://forum.inductiveautomation.com/u/hunterdg)\
**Post date:** [March 21, 2025, 12:55am UTC](https://forum.inductiveautomation.com/t/page-props-urlparams-are-timestamped-with-gateway-time-when-written-from-client/103986/3 "2025-03-21T00:55:37Z")

</div>

Not necessarily surprising, given the “read only” use-case assumption, just confusing since they _can_ be written to from designer/browser. In that case, I’d assume the “normal” behavior would apply.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [March 21, 2025, 12:58am UTC](https://forum.inductiveautomation.com/t/page-props-urlparams-are-timestamped-with-gateway-time-when-written-from-client/103986/4 "2025-03-21T00:58:37Z")

</div>

Does your designer's time differ from the gateway (after converting both to UTC)?

---

<div class="post-metadata">

**Author:** ![hunterdg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/hunterdg/32/67774_2.png) [@hunterdg](https://forum.inductiveautomation.com/u/hunterdg)\
**Post date:** [March 21, 2025, 1:00am UTC](https://forum.inductiveautomation.com/t/page-props-urlparams-are-timestamped-with-gateway-time-when-written-from-client/103986/5 "2025-03-21T01:00:23Z")

</div>

lol, that’s precisely how I discovered it.