Back in February, we released Global Suppression List, Creative Library, and Data Sync. If you missed it, explore the February Product Spotlight.
Over the past month, teams have started putting these into practice, and we’re already seeing patterns take shape in real workflows. These features are enabling more dynamic messaging by centralizing content and data, allowing for a more comprehensive view of customers by connecting Iterable data with warehouse systems, and simplifying suppression and governance as programs expand across campaigns and projects.
With that, a few common questions and use cases have come up along the way.
Here’s what we’re seeing so far and how to help you navigate it.
Global Suppression List
What we’re seeing:
Teams are quickly adopting this for governance and compliance use cases, especially where suppression was previously managed manually.
Where questions are coming up:
- Do I need to add this to journeys, or is it automatic?
- Global Suppression List is enforced at the project level and applies automatically to new campaigns and journeys.
- For existing campaigns and journeys, you’ll need to manually enable it.
- Can suppression be applied by channel?
- Suppression is applied globally across the project. Channel-specific control would still require additional segmentation or logic.
- What happens if users re-enter Iterable after being suppressed?
- If a user is included in the Global Suppression List, they will continue to be excluded from messaging even if they re-enter your project or qualify for campaigns.
- Do I need to update all my existing journeys?
- For existing campaigns and journeys, suppression must be enabled manually. Teams with many active journeys may need to plan a phased rollout.
Why this matters for you: This removes the need to rebuild suppression logic repeatedly and gives you a more reliable way to protect audiences as your programs scale.
Creative Library
What we’re seeing:
Teams are adjusting from legacy asset workflows to a more centralized way of managing creative.
Where questions are coming up:
- How do I know what’s been migrated or updated?
- Supported assets and folders migrate automatically, and your existing image links continue to work. The platform maps legacy references to new paths in the background, so you don’t need to worry about broken links.
- Why do I need to upload and link assets now?
- Creative Library centralizes asset management within Iterable, improving reuse, consistency, and long-term stability across campaigns.
- Can I still use PDFs in my messages?
- Yes. PDFs can be uploaded to Creative Library and referenced via a hosted URL. This replaces the previous file manager workflow and ensures assets are centrally managed and reusable.
Why this matters for you:
Once set up, this reduces time spent searching for assets and helps keep every message aligned and on-brand.
Data Sync
What we’re seeing:
Teams are evaluating how Data Sync fits into their warehouse and analytics workflows, especially as they look to reduce reliance on custom pipelines.
Where questions are coming up:
- If I don’t use Data Sync, can I still access data?
- Yes. Existing APIs and webhooks remain available. Data Sync provides a managed way to deliver data into your warehouse for analysis.
- What destinations are supported?
- Data Sync supports destinations including BigQuery, Databricks, Redshift, and Amazon S3.
- For Snowflake users, Snowflake Data Share is the recommended approach.
- Is this real-time?
- No. Data Sync is designed for scheduled batch delivery, not real-time workflows.
Why this matters for you: This creates a more dependable foundation for reporting, modeling, and connecting engagement data to business outcomes.
What This Signals
Across all three features, you’re likely seeing the same shift:
It’s less about what the feature does and more about how it fits into your existing workflows.
There’s also a clear move toward:
- Built-in governance, reducing reliance on manual workarounds
- More centralized systems, replacing fragmented tools and processes
- More reliable data foundations to support reporting and decision-making
We’ll continue surfacing patterns and conversations in the Plaza as teams implement Iterable features.