Go to website

• What is called a Noticeable request?

  Each plan includes a limit on the number of requests allowed per month. The limit is there to protect our infrastructure but also to provide the best quality of service by allocating resources based on your needs. Requests correspond to calls (e.g. Widget data loading, Timeline page views or API calls) that reach our servers to retrieve fresh content. By default, content that is returned to clients for a request is cached for 5 minutes thanks to a first-class Content Delivery Network(httSome readers

• Where should I place the Widget?

  Where to place the Noticeable Widget The widget element can be placed at any position. It's an HTML element as a div element is. Usually, the most appropriate location is near your app logo, in the header bar or your page menu. Here is an example: For advanced customization, see the page below (coding knowledge required): [https://widget.noticeable.io/v1/Some readers

• How is multi-languages supported?

  Multi-languages is managed with multi-projects. If you need to create posts in multiple languages, we recommend setting up a project per language. This has multiple benefits since you can manage per project and thus language: post analytics. feedback and reactions. the labels used to classify posts. the integrations with third-party services. the Timeline and Widget options. the default texts for the Timeline and the Widget. who has read and write access (collaborators).Some readers

• Why Noticeable?

  The most important moment for your users to care about new product features or improvements is when they're using your product, so that's exactly where you should be announcing your updates: in-app. With Noticeable, you can easily announce relevant news, your latest features, and updates using a nice widget. Users can send feedback, which provides immediately interpretable, and actionable data to improve your product and reduce churn. That's not all. A single channel to communicate your impoFew readers

• Why may changes take up to 5 minutes to propagate?

  Noticeable makes use of a first-class Content Delivery Network (CDN) for reducing latency and improving users experience when the API, Widget or Timeline is accessed. Upon content change, up to 5 minutes are required to synchronize all worldwide edge nodes with your new content. If you want to bypass the CDN or test a setting right away, we provide the following mechanisms: API: perform a POST request instead of a GET request. Timeline: add `?cacFew readers

• Browsers compatibility

  Noticeable Timelines and Widgets have support for the latest two versions of all major browsers: Safari 10+, IE 11+, and the evergreen Chrome, Firefox, and Edge. What about old browsers such as IE 9 and 10? Older browsers such as IE 9 and 10 have no guaranteed support. Please note that even Microsoft has dropped support since more than 2 years: https://www.microsoft.com/en-us/windowsforbusiness/end-of-ie-support(https://www.microsoft.com/en-us/windowsforbusiness/end-of-ie-Few readers

• Upgrading to Noticeable-Zapier Integration Version 2

  Version 2 of the Noticeable-Zapier integration is a major step. It includes new actions and triggers that open Noticeable to more use cases but also simplifies the integration with other services you like.  The side effect is that upgrading to this version requires a few minor actions on Zapier since we do not have control over their API and infrastructure. Here are the steps: Open you Zapier dashboard and click on "Zaps" in the upper left side: ![](https://storage.crisp.chat/users/helpdesFew readers