Open robert1112 opened 2 weeks ago
We probably won't store utm_*
parameters in cookie. We generally consider polluting cookies as a bad idea, especially considering the fact that cookies are becoming less reliable.
You could always persist utm's by anonymousId
key in the store
Speaking of gclid
/ fbclid
. Here's a design we think makes sense here:
clickIds
node and populate it with most popular click ids: gclid
and fbclid
clickIdsCapture
and cookieCapture
to let user control what additional cookies / parameters to capture
Current Behavior
Suggested Improvement
1.Storing gclid and fbclid: Store gclid and fbclid in cookies, allowing them to be overwritten if new values are present. Currently, they are only URL parameters and are not stored as cookies in the browser. Jitsu should capture gclid and fbclid from cookies and save them under “clientIds” in the JSON event data. 2.Persisting UTM Data: Capture UTM data from the URL and store it in cookies. Jitsu should read UTM data from these cookies.
3.Preventing Non-Search Key Capture: For WordPress sites, ensure that non-search keys are not captured as search keys. Specifically, the ?s parameter key should be handled correctly.
Reasons for Improvements