Skip to main content

My name is Pedro Peixoto, and I use iterable in connection with Segment.io

I would like some help/best practices with managing our contact's properties:

I'm in the midst of some platform changes, and along with that, I am reviewing the pieces of information we pipe through Segment, and by connection, to Iterable. Our current doubts are:

- How do I move data from one property to another? IE: If I have some customers with a "phone" property, how do we move from that into the builtin "phoneNumber"

- How do we get rid of a given property throughout our user base? I might have some properties that no longer make sense to my platform, contain incorrect data, or are no longer being tracked, and would like to clean up my user base.

- How can these changes to a contact's properties be piped through Segment into Iterable? So far I have used Segment's IDENTIFY calls, but those don't seem to be able to remove data.



Thanks and Best Regards,

Pedro Peixoto.

Hi Pedro,

  • We actually convert Segment's built-in `phone_number` field to match ours, so `phone_number` will come through as `phoneNumber` in Iterable through the Segment integration.


  • Unfortunately user data can't be deleted in Iterable. This is a limitation of the database we use. A workaround is to "hide" the property so the property doesn't show up for any users in the project. You can do this by going to your Iterable project's settings -> scroll to "Select user fields to hide" -> scroll to the bottom of the page and click Save Project Settings.


  • You would need to use the above method to hide fields. Removing them via Segment's IDENTIFY call isn't possible right now.


Please let us know if you have any further questions.

Michael

Hi Michael,

Thanks for the reply. I do have some follow up questions:

  • The phone number here was merely an example. If I want to move data from "color" to "favourite_color", Is creating/hiding fields as mentioned my only solution?


  • If I hide a field, will that still be accessible on email templates or anyone other an admins? If not, then hiding fields should work for "deletions", but what if I want to invalidate the contents of a field? IE: A customer as a "default_card_id" of 10, and I want to set it to NULL, or a blank string, or something that evaluates to False?


Best,

Pedro Peixoto.

Hi Pedro,

I see, thank you for the clarification. The ability to 'map' a field from Segment to a specified field in Iterable is not yet something that is supported, but I do see that this is an existing feature request, so this is something documented with our Product team.

Regarding your question re: hidden fields, our documentation outlines this well:

User-related fields that Iterable users should not be able to select in segmentation, workflow filters, or template editors.


If a hidden field is already being used in a template, it will remain there and continue to insert data into associated sends.


In your example where a customer has a "default_card_id" of 10, you can also update the user's data so that "default_card_id": null. When setting a field to null, it will no longer show on the user's fields. And you can make updates to the user fields whether they are hidden or not. The next time the field is 'unhidden', the latest update to the field will be displayed.

I hope this helps!

Best,

Michael

Reply


Terms & ConditionsCookie settings