Skip to main content
Solved

Update on timestamps to Customer.io?

  • March 10, 2026
  • 5 replies
  • 218 views
tobysola1
Forum|alt.badge.img+10

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/. 

    5 replies

    wes_clark
    RevenueCat Staff
    Forum|alt.badge.img+6
    • wes_clark
    • 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+10
    • tobysola1
    • 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
    • wes_clark
    • 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.

      tobysola1
      Forum|alt.badge.img+10
      • tobysola1
      • Author
      • Dedicated Member
      • March 23, 2026

      ​@wes_clark Great, thanks! 

        wes_clark
        RevenueCat Staff
        Forum|alt.badge.img+6
        • wes_clark
        • RevenueCat Staff
        • May 27, 2026

        ​@tobysola1 I just wanted to reach back out to update you that the Engineering team has implemented a change to allow for events to be sent in Epoch timestamp format. It will be the default for newly created integrations going forward, but existing integrations can select which format to use via the “Timestamp format” field in the Customer.io integration. If you want to switch over to having the Epoch timestamp format be what is sent, just make sure that you turn off the workaround that I linked in my first reply to your post.

        Here is a screenshot of that field:

         

        Terms & ConditionsAccessibility statement