We’re extremely excited to announce that Iteratively is joining @Amplitude_HQ 🎉🎉 In Amplitude we see an ally in the pursuit to solve the acute pain points around data quality and we couldn’t be more thrilled about this next chapter of Iteratively 🚀 buff.ly/3hlOYEO
Iteratively is part of @Amplitude_HQ – now what's next for us? Join the live Q&A tomorrow where Ondrej & Patrick will share more about their strategic vision together with Amplitude: info.amplitude.com/amplitude…
🤩🤩🤩
Data quality is the largest blocker to successfully using Product Analytics. I'm excited to announce we've acquired Iteratively to help all Amplitude customers with data governance and quality. techcrunch.com/2021/05/12/am… Welcome @iteratively @patrickt010 @ondrej421 to Amplitude!
Iteratively, an Amplitude Company retweeted
“As we spoke to our customers, we consistently heard from them the importance of proactively and continuously increasing the quality of data." Our own @justinjbauer shares more on our acquisition of @iteratively. Read it in @TechCrunch @fredericl
We're super excited too 💙 Thank you for the warm welcome!
Data is only useful if you can trust it. We’re excited to announce the acquisition of @iteratively, a data planning solution that eliminates human error during analytics instrumentation. Read more and give a warm welcome to our newest #Ampliteers 🎉 bit.ly/3eHmOSK
We enjoyed this too. Great inspiration for data-led startups to get up and running quickly!
Check out this nice write-up on their product-led growth stack from our customer Jonathan Sanders from Juni - linkedin.com/pulse/no-code-d…
This is a must read from @emilieschario and @tamurphy on why you should run your data team like a product team (and avoid the death spiral of becoming/remaining a reactive services team): buff.ly/3grtCVZ 👏 👏 👏
We can't wait for this to go live 🤩
🤩 LIVE on April 22nd:
@dataledpodcast: #WebAnalytics vs. #ProductAnalytics,
And The Data That Powers Them
🌟 Ft. special guest, Patrick Thompson, Co-Founder of @iteratively 🌟
Catch the latest episode here:
bit.ly/3svDPD0
#datacollectiontool #customerdata
Totally! @RudderStack + Iteratively = 🚀
Hi @ezramechaber, a few notes from RudderStack the team 😎:
- RudderStack + @iteratively = power combo
- RudderStack pipelines are bi-directional (we support Reverse ETL)
Thanks for the getting this convo started!
Missing tracking? Fail the build ⛔️Here's our take on how you can make event tracking a more integrated part of your release process: buff.ly/3cyHbPH
Lots of great speakers at this one 👀
Today is the beginning of our week-long Operational Analytics Conf 🎉
First session is at 6pm PT and we will discuss the next generation of data w/
🔎 Barr Mosses - @montecarlodata
🚀 @martin_casado - A16Z
🎢 @frasergeorgew - @Fivetran
Add to your cal hubs.la/H0K_1DX0
We really enjoyed this interview with @episod from @SlackHQ. Full of learnings we can adopt here at Iteratively 🤩
🚨 Today we're thrilled to introduce a new content series: Masters of Product Change!
And what better way to kick off this series than with 10 question for @episod, the Director of Developer Relations Education at @SlackHQ?! 🚀
launchnotes.com/blog/masters…
@SlackAPI #launchawesome
It's official, we're SOC 2 compliant 🔒⚡️You can read more about what this means for you on our blog: buff.ly/2Q5hSNE. And thanks to @DrataHQ for guiding us along the way 🙏
Want to get started with #PLG but drowning in an ocean of tools? Here's a look inside our PLG stack and some thoughts on what has worked for us so far: buff.ly/2Q68lpq
If you have 15 minutes to spare and a ☕️, this is a great read by @getcensus buff.ly/3wIjEoW
Who owns the tracking plan in your company?
Here's what we found from speaking to more than 400 data and product teams (a thread):
👩💻 PMs should be the main driver and ensure analytics tracking is part of every feature release. Depending on your team size, this could be one or more product managers or a dedicated product analyst. They should be held accountable for tracking as a part of their role and OKRs.
👀 Check out our blog post for more on this topic so you can avoid this: buff.ly/3bRBYSP
















