Hello all!
My team and I are on-boarding to Iterable this week and I'd love to hear some of the do's and don'ts in the early stages of the Iterable set up process. We are moving from a less than good system and are super excited for the blank slate that is Iterable!
any tips, tricks, and general 'you should know's' are greatly appreciated!
Thankks
Page 1 / 1
Hi @Jahan Walsh! Welcome to the community! I hope you get some great feedback from other customers.
I wanted to share some materials from the Iterable team that might help you out as you get started. Check 'em out:
* Guide to welcome campaigns
* Guide to onboarding series
* Really Good Emails has some great examples as well!
I'd love to hear from the rest of the community as well! What tips and tricks do you have for Jahan? Let us know in the comments.
I wanted to share some materials from the Iterable team that might help you out as you get started. Check 'em out:
* Guide to welcome campaigns
* Guide to onboarding series
* Really Good Emails has some great examples as well!
I'd love to hear from the rest of the community as well! What tips and tricks do you have for Jahan? Let us know in the comments.
Hi @Jahan Walsh ! Welcome to iterable 😀 . We started using iterable about 2 years ago, and I highly recommend working with your CSM to go through the IP warming process correctly.
Also, if you're planning on putting data in the user profile always test in sandbox first and documentation is your best friend. You can't reset a data field type after you've created it, so it's always a great idea to test creating it in sandbox to make sure it's correct and you can pull segmentation correctly.
Those are my two top tips!
Also, if you're planning on putting data in the user profile always test in sandbox first and documentation is your best friend. You can't reset a data field type after you've created it, so it's always a great idea to test creating it in sandbox to make sure it's correct and you can pull segmentation correctly.
Those are my two top tips!
Welcome @Jahan Walsh !
One thing I have found throughout my career implementing/migrating platforms is the more prepared you are with what you want to accomplish, the easier it is to make decisions. Particularly for Iterable, knowing which campaigns/workflows you want to migrate initially and what data is needed to make those run, will help ensure a better data schema discussion. It also helps the Iterable team guide you on options for implementing aspects of personalization, pulling in data for events vs lists, and triggering more real time communications vs batch & blast.
Hope that helps!
One thing I have found throughout my career implementing/migrating platforms is the more prepared you are with what you want to accomplish, the easier it is to make decisions. Particularly for Iterable, knowing which campaigns/workflows you want to migrate initially and what data is needed to make those run, will help ensure a better data schema discussion. It also helps the Iterable team guide you on options for implementing aspects of personalization, pulling in data for events vs lists, and triggering more real time communications vs batch & blast.
Hope that helps!
Reply
Create a new Iterable Plaza community account
Already have an account? Login
Login to the Iterable Plaza Community
Not a customer? Create an account
Log in to Iterable (SSO)
Iterable customers and employees login/create an accountor
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.