We’ve refreshed our GraphQL API explorer to use Playground.

The API explorer is a great companion for development and testing purposes. The new Playground interface simplifies advanced integrations with Noticeable by providing:

• Pre-filled examples to fetch project and post data but also templates to create, update or delete posts.
• An interactive, multi-column schema documentation.
• Better iterative testing with query history.
• One click export to cURL command.
• Requests tracing to understand where time is spent and how to reduce timings for your queries.

Here is a link to give a try using a sample Access Token:

https://api.noticeable.io/graphql?accessToken=f9rdse8k7mBbuCbjAKhy

Last but not least, you will also notice better response times thanks to some tweaks we applied to our infrastructure.

If you have questions or suggestions drop us a line.

Last week we announced Emoji Reactions. Today, we are excited to introduce User Feedback!

This new feature allows your users to send you feedback by commenting on a post, directly from your Widget or Timeline. Comments are hidden, meaning users won’t be able to see others’ comments. Only your team and you are able to read messages and get users information.

How does it work?

User feedback is available with the Business plan. When creating a post, check the new User feedback option to enable the comment input below the post shown to users.

On your project dashboard, each post displays a feedback icon that summarizes the number of comments you received. Upon click, you can read the messages and get detailed information about the user who submitted the feedback:

By default, comments are anonymous. You can automatically link users name and email with comments sent from the Widget by using our SDK. Read the installation guide for more information.

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 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 💡

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.