Summary
We are updating how record_timestamp (the feedback creation timestamp) is handled for feedback records. This change ensures more predictable behavior and consistent data handling.
What's Changing
Starting with this release, the record_timestamp field becomes immutable after a record is first created. This means:
Once a feedback record is ingested into Enterpret, its timestamp cannot be changed by re-sending the same data with a different timestamp.
If you send data with the same record ID but a different timestamp, the timestamp change will be ignored and the original timestamp will be preserved.
Affected Data Sources
This change affects data sources where you control the timestamp value:
Snowflake (ERC_CREATED_AT field)
Webhook
File Upload
Note: Native integrations (such as Zendesk, Intercom, App Store, Play Store, etc.) are not affected by this change as Enterpret automatically handles timestamps from these sources.
How to Correct Timestamps
If you need to correct the timestamp on existing records (for example, due to timezone issues or incorrect date formats in your initial data load), follow this two-step process:
Step 1: Delete the Incorrect Records
Before re-sending data with corrected timestamps, you must first delete the existing records. You can do this by:
Using the Enterpret API to delete records by their record ID
Contacting Enterpret support to request a bulk deletion
Step 2: Re-send Data with Correct Timestamps
Once the incorrect records are deleted, re-send your data with the correct timestamps. The records will be ingested as new entries with the corrected timestamp values.
Example: Snowflake
If you have records in your Snowflake table with incorrect ERC_CREATED_AT values:
Identify the affected record IDs (
ERC_IDvalues)Request deletion of these records from Enterpret
Update your Snowflake table with the correct
ERC_CREATED_ATtimestampsThe corrected records will be ingested during the next sync
Best Practices
Validate timestamps before initial import: Ensure your timestamps are in the correct format and timezone before sending data to Enterpret.
Use UTC timestamps: We recommend using UTC timestamps to avoid timezone-related issues.
Test with a small batch: When setting up a new integration, test with a small batch of records first to verify timestamp handling.
Frequently Asked Questions
Can I still update other fields on existing records?
Yes, you can update other fields (such as metadata, tags, or content) by re-sending the record with the same ID. Only the timestamp field is immutable.
What happens if I accidentally send duplicate data with different timestamps?
The system will recognize the record by its ID and preserve the original timestamp. The new timestamp will be ignored, and only non-timestamp fields will be updated.
How do I request bulk deletion of records?
Contact Enterpret support with the list of record IDs you need deleted. For large deletions, please provide the data in CSV format.
Need Help?
If you have questions about this change or need assistance correcting timestamps on existing records, please contact Enterpret support.