[PE-103] Update group action to use created_at as a reserved key #2500
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, our Mixpanel group action only treats the
name
trait field as a reserved property for Mixpanel.A customer has raised a concern that they would like the created field to be handled in the same way as name. As currently, when
createdAt
,created
, orcreated_at
are not sent as$created
, these fields are added to group profiles as regular profile properties instead of being treated as reserved properties.The ask from the customer is to update the group action to operate in the same way that the identify action does regarding reserved properties. Similar to this update: #801
Testing
before update
after update