Product Updates Updates

End User Authentication for Widgets

by Laurent Pellegrino, Founder and CEO
New
Widgets

We’re excited to introduce end user authentication with Noticeable widgets.

End user authentication is a feature you can optionally integrate to verify the identities of your end users. This ensures that when end users engage with widgets, such as commenting, their identity is confirmed and secure from impersonation.

How does it function?

Noticeable employs Single Sign-On (SSO) tokens for this authentication process:

  1. On your server(s) side, you create an SSO token for each end user (using a secret we share).

  2. You pass this SSO token with our Javascript SDK before rendering any widget.

  3. VoilΓ ! Your end user's identity is now securely authenticated with Noticeable widgets.

Note: While it's still possible to pass end user traits using our Javascript SDK as outlined in our various identification methods, this approach is no longer recommended.

Read more

Did you like this update?

LikeNeutralDislike

{error_message}

Leave your name and email so that we can reply to you (both fields are optional):

Thanks for your feedback!

Email Sending is Now in Beta!

by Laurent Pellegrino, Founder and CEO
Announcement

We’re excited to announce that our email sending feature, which was initially launched last year in private preview and later moved to public preview, has now reached the beta stage!

Over the past months, we’ve been working relentlessly to scale and improve the platform to ensure a smooth, feature-rich experience for our users. We have also been laying the groundwork for some exciting upcoming additions.

Here's a rundown of the key features now available in the email sending beta:

  • πŸ“§ Effortlessly send emails to your subscribers with just one click.

  • πŸ” Send a preview email to yourself or your team before dispatching to everyone.

  • πŸ“Š Manage subscribers directly from our dashboard or via the Noticeable API.

  • πŸ’Ύ Export your subscribers to a CSV file.

  • ⚑️ Utilize Zapier to automate subscription-related tasks.

  • 🎨 Customize the email sender's name, reply-to address, and header logo.

  • 🌐 Set up a custom domain for your "from" email address.

  • πŸ”— Choose whether to track link clicks and/or email opens.

  • πŸ“‹ Access detailed information about email dispatches and their senders.

  • πŸ” Benefit from both double opt-in and single opt-in support.

  • πŸ“ˆ Analyze in-depth statistics on each email dispatch, including soft bounces, hard bounces, spam complaints, opens, etc.

  • πŸ“ͺ Enjoy automatic email unsubscription for hard bounces and spam complaints.

Stay tuned, as we have more amazing features coming soon!

We always welcome and value your feedback. If you have any suggestions or are interested in a specific feature, please don't hesitate to share your thoughts below.

Open dashboard

Did you like this update?

LikeNeutralDislike

{error_message}

Leave your name and email so that we can reply to you (both fields are optional):

Thanks for your feedback!

Deprecations for December 24, 2022

by Laurent Pellegrino, Founder and CEO
Announcement

We are writing to inform you that several fields, mutations, queries, and types in our GraphQL API and Zapier integration have been deprecated and will be replaced with their equivalent after May 21, 2023.

GraphQL API

  • The argument id has been renamed to projectId in project query.

  • The field creationTime has been renamed to createdAt.

  • The field posts in Project type has been renamed to publications.

  • The field updateTime has been renamed to updatedAt.

  • The mutation named createPost has been renamed to createPublication.

  • The mutation named deletePost has been renamed to deletePublication.

  • The mutation named updatePost has been renamed to updatePublication.

  • The query named post has been renamed to publication.

Zapier Integration

  • The output field with the key creationTime has been renamed to createdAt.

  • The output field with the key updateTime has been renamed to updatedAt.

  • The output field with the key publicationTime has been renamed to publishedAt.

Please make sure to update your code or integrations to reflect these changes to avoid any disruptions.

If you have any questions or concerns, don’t hesitate to leave a comment or contact us directly.

Have a great holiday season! πŸŽ„

Did you like this update?

LikeNeutralDislike

{error_message}

Leave your name and email so that we can reply to you (both fields are optional):

Thanks for your feedback!