You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 14, 2019. It is now read-only.
I am porting some ga code to use segment. There are the ga('set', .... ) calls for which I dont see a corresponding version in analytics.
It is not possible to pass in the custom dimensions as properties because they were being set in a different part of the page, and the track/page calls happen elsewhere.
What I am proposing is, we add a Analytics.prototype.set(props) method. The props would be buffered internally. And when users call track or page or identify, the api calls would be merged with those passed in with the set call. This way it would work for all integrations.
The text was updated successfully, but these errors were encountered:
Hi @ferozed, as part of the monorepo migration, this issue has been moved to new issue. Our engineers have been notified and will prioritize and work on it ASAP. Thank you!
I am porting some ga code to use segment. There are the ga('set', .... ) calls for which I dont see a corresponding version in analytics.
It is not possible to pass in the custom dimensions as properties because they were being set in a different part of the page, and the track/page calls happen elsewhere.
What I am proposing is, we add a
Analytics.prototype.set(props)
method. The props would be buffered internally. And when users calltrack
orpage
oridentify
, the api calls would be merged with those passed in with theset
call. This way it would work for all integrations.The text was updated successfully, but these errors were encountered: