+9Hi,
I’m using the direct integration between RC and Customerio. For the expiration_at parameter, RC sends an ISO timestamp. However! Customerio only uses Epoch (specifically in seconds–not milliseconds). Please change the integration such that the timestamp for expiration_at is an Epoch timestamp in seconds. Otherwise, this integration isn’t very useful (the most important piece of data that I need in Customerio is the user’s expiration date!).
I mentioned this to
cc
Thanks!
Toby
+6Thanks
I’ll make sure this feedback is noted internally as well.
+9Hi Kaitlin,
Great, thanks! Can you let me know when this is fixed?
Relatedly, as far as I can tell, aliasing is not handled as part of this integration. For example, if RC creates an alias for a user, RC doesn’t communicate that in anyway to Customerio. This creates all sorts of problems. For example, if a user who has an alias in RC subscribes, the updated subscription might only make it to one profile in Customerio. And then, when I go to send a sales email out, the profile that didn’t get the subscription update will receive the email. That’s bad to send a discount to someone who is already subscribed!
I think the way to fix this would be to trigger Customerio’s merge function if RC creates an alias. So when an alias is created in RC, you ping Customerio’s API to merge the two profiles. This is the type of syncing that I’d expect from a “direct integration” between two tools. What do you think? Will you build this functionality? cc
Thanks,
Toby
+6Hi
Currently, we don’t send an event to customer.io when an alias has occurred, but all aliased ids will be included in the `alias` object within the event, if that’s helpful.
I can definitely bring this feedback to our team working on the integration as well for a better way to handle aliasing!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.