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
For a custom event on clevertap, we are passing a string value for a particular property, but on clevertap events dashboard it is reflecting in integer formats.
Following is the code snippet we are using to record our custom events:
clevertap.event.push("submit_info", {
user_info:"087888975005" // this property is passed as *string*
});
Here, the property user_info although passes as string, is reflecting as integer on the dashboard.
Alternately, for the same event if I limit the user_info property's value to 10 or less characters, it correctly reflects as a string on the dashboard.
We have also updated the custom event schema in project settings by defining the property to accept string format values only, but still the they are being populated in integer format.
Please correct us if we are missing something here, although from our findings it is only happening in case of the property value being more than 10 characters.
The text was updated successfully, but these errors were encountered:
For a custom event on clevertap, we are passing a string value for a particular property, but on clevertap events dashboard it is reflecting in integer formats.
Following is the code snippet we are using to record our custom events:
Here, the property user_info although passes as string, is reflecting as integer on the dashboard.
Alternately, for the same event if I limit the user_info property's value to 10 or less characters, it correctly reflects as a string on the dashboard.
We have also updated the custom event schema in project settings by defining the property to accept string format values only, but still the they are being populated in integer format.
Please correct us if we are missing something here, although from our findings it is only happening in case of the property value being more than 10 characters.
The text was updated successfully, but these errors were encountered: