Today, we have a big update to share: Emoji Reactions. They are a fun, low-effort means for users to engage on updates and for you to better understand what people think.

Why Emoji Reactions?

Getting people to actively participate is key to developing stronger relationships. Users who engage consume, on average, 4 times as much content compared to passive users. Converting more passive users to active participants means more time on site, direct traffic, and audience loyalty.

How is it working?

Emoji Reactions are available with the Business and Enterprise plans right now. When you create/edit a post, you have a new option to enable/disable reactions. Upon publications, users can share their feeling about your update in just one click. Statistics are aggregated over time and made visible per post in your dashboard to analyze performances:

What do you think?

As you probably guessed, the Emoji Reactions feature is enabled for this post. Be sure to react to let us know what you think. If you have ideas or feedback, let us know by leaving a comment below.

Recently, the second version of our Zapier integration has been released. It enables new use cases via additional triggers and actions. Especially, post creations and editions are handled through 2 different events. We know this may require some tedious configurations to handle both events the same way.

We’ve listened to your feedback and are happy to say that a new Zapier trigger called "Post Created or Updated" has been added. It allows triggering a Zap when a post is created or updated and the “Forward to integrations” is enabled for that post.

Available triggers, actions and templates are explained on the next page:

https://zapier.com/apps/noticeable/integrations

We’ve updated the pages to create and edit posts:

• Clicking on the preview button disable all Markdown action buttons.
• Markdown action buttons better handle how the text is wrapped/unwrapped.
• An alert is displayed when other collaborators edit the same post as you.

We are thrilled to announce the second version of our Zapier integration. It includes new triggers and actions.

What's new?

You can trigger an action to external services when a post is deleted (new Post Deleted trigger). That's a simple solution to keep posts visible for a specific period of time with no code!

Besides, we have added 2 new actions: Create Subscriber and Delete Subscriber. Let's say you are already managing a mailing list with Mailchimp or another service, these new actions allow keeping in sync your existing list with your Noticeable Timeline subscribers.

What's changed?

Post creation and edition are now triggering 2 different events. In addition, you have the choice to trigger an action when the post that is created or edited is a draft, published, scheduled, or has any of these statuses. The default option is published.

What about existing Zaps?

If you already had a Zap configured, you should have received an email claiming that version 1.0.8 of our integration has been deprecated. You have until September 1, 2018 to upgrade to version 2.0.0. One month after this date, triggers configured with a version lower than 2.0.0 will have no guarantee to be executed.

Look at our guide to upgrade your existing Zaps in no time.

We have made several improvements to the Widget:

1. Its definition is smaller. Fewer data to fetch, less time to first display. The Widget is now speedier than ever 🗲

2. Setup instructions have been updated to reference a new script element. Instead of 4 line of codes, a single is now required to import the Widget definition:

   <script async defer src="https://cdn.noticeable.io/v1/noticeable-widget.js"></script>
   

   The async and defer attributes guarantee the content is loaded in parallel and executed after your page is parsed, no matter where the import is placed in.

   Although we recommend switching to the new import script, old ones remain available but are deprecated.

3. Unread posts displayed in the Widget popup now include a left border. This allows distinguishing unread messages from read ones:

   

   The color of the left border is based on the project accent color but can be changed programmatically. You can set it transparent to mimic the old style:

   <custom-style>
       <style>
           noticeable-widget {
               --noticeable-widget-popup-entry-unread-border-color: transparent !important;
           }
       </style>
   </custom-style>
   

4. Widget but also Timeline code snippets are rendered with the Atom One Dark style to improve readability.

We have updated our API to support posts edition and deletion.

Please have a look at the API overview page for explanations about how to consume the API (authentication required).

We also took the opportunity to create a public repository that provides samples for the most common operations. If you need help with integration, do not hesitate to drop us a message 🙋

Last but not least, our GraphQL schema is now documented.

Do you have a lot of posts? are you managing posts with different labels? do you want to display draft posts only? segmented posts?

Today, we have deployed a new version of the service that allows filtering posts in your projects dashboard per status (draft, published, scheduled, segmented) and labels. Both filtering criteria can also be combined to perform fine grain filtering.

We want to make Noticeable work for you, and therefore your feedback is important to us. Feel free to contribute to our public roadmap with new ideas 💡

We are proud to announce the availability of our new Help Center. This last centralizes the most frequent questions we receive but also share tips and discuss advanced features. You can search by keywords and leave reactions. The content will expand with time.

If you have questions or need help, you can also reach us by chat on our pages or by email.

A new version of the service has been deployed. It allows configuring your Job title per project. It is particularly useful in a multi language context where a project per language is used.

How to proceed

1. Go to your account page.
2. Tap on the toothed wheel on the right side of the Job title field.
3. Configure your Job title per project.
4. Click on Save changes.

If you leave a field empty, your default Job title will be used.

Existing posts aren't updated with Job title updates. Only new posts reflect the changes. If you want to update the Job title associated with an existing post, simply edit the post and save it again.