Skip to main content
Solved

Update on timestamps to Customer.io?

  • March 10, 2026
  • 3 replies
  • 45 views

tobysola1
Forum|alt.badge.img+9

Hi, 

Any update on changing the timestamps you’re sending to Customer.io via the direct integration from ISO to Epoch? I asked in this post before: 

Customer.io doesn’t run on ISO, they use Epoch. As it stands, this integration isn’t very useful (the most important piece of data that I need in Customerio is the user’s expiration date!).

Best answer by wes_clark

Hi! I am following up on this internally, but in the mean time and in case you had not seen this documentation, I found this documentation from Customer.io on updating attributes to Epoch on their end if they are not added in that format originally: https://docs.customer.io/journeys/how-to-use-attribute-updates-to-reformat-timestamps/

3 replies

wes_clark
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • Answer
  • March 12, 2026

Hi! I am following up on this internally, but in the mean time and in case you had not seen this documentation, I found this documentation from Customer.io on updating attributes to Epoch on their end if they are not added in that format originally: https://docs.customer.io/journeys/how-to-use-attribute-updates-to-reformat-timestamps/


tobysola1
Forum|alt.badge.img+9
  • Author
  • Dedicated Member
  • March 13, 2026

@wes_clark Oh that’s interesting, I hadn’t seen that. Pretty nifty! And thanks for following up internally. 


wes_clark
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • March 20, 2026

@tobysola1 You’re welcome. I am glad that this doc will be useful for you. I do not currently have an update regard the change to the Customer.io, but I have made sure that the Product/Engineering teams are aware that this change would be very useful for you and other developers.