Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Beamer Source


Source Info
  • The Beamer Source is an Event Cloud source. This means that it sends data as events, which are behaviors or occurrences tied to a user and a point in time. Data from these sources can be loaded into your Segment warehouses, and also sent to Segment streaming destinations. Learn more about cloud sources.
  • This integration is partner owned. Please reach out to the partner's support for any issues.
(warning)

This Source is supported in US data processing regions.

This Source is only supported in workspaces configured to process data in the US region. Workspaces configured with data processing regions outside of the US cannot connect to this source. For more information, see Regional Segment.

Beamer(link takes you to an external page) is a changelog and notification center that lets you announce new features, product updates, special offers and more.

This source is maintained by Beamer. For any issues with the source, contact the Beamer Support team.

(success)

Success!

This page is about the Beamer Segment source, which sends data into Segment. There's also a page about the Beamer Segment destination, which receives data from Segment!

(new)

This document is about a feature in beta

This means the feature is actively being developed, and some functionality may change before it becomes generally available.


Getting started

getting-started page anchor
  1. From your Segment UI's Sources page click on "Add Source".
  2. Search for "Beamer" within the Sources Catalog and confirm the Source you'd like to connect to.
  3. Give the Source a nickname and follow the set up flow to "Add Source". The nickname will be used to designate the source in the Segment interface, and Segment will create a related schema name. The schema name is the namespace you'll be querying against in your warehouse. The nickname can be whatever you like, but we recommend sticking to something that reflects the source itself and distinguishes amongst your environments (eg. SourceName_Prod, SourceName_Staging, SourceName_Dev).
  4. Copy the Write key from the Segment UI and go to Integrations(link takes you to an external page) in your Beamer dashboard, then paste your write key in the Integrate with Segment section.
  5. Click Save.

Beamer uses a server-side Track method to send all user interactions to Segment. Keep in mind Beamer will only send interactions from users that are identified with a userId, which must be provided by you. For more information on how to identify your users in Beamer, check out our Developer Docs(link takes you to an external page) (see the user_id parameter).

Below is a table of events that Beamer sends to Segment. These events will show up as tables in your warehouse, and as regular events in your other Destinations.

Event NameDescription
Post ViewedA post in your feed was viewed by one of your users
Link ClickedA link in one of your posts was clicked by one of your users
Push Notification ClickedA push notification was received and clicked by one of your users
Post CommentedA user has commented on one of your posts
Post Reacted ToA user has sent a reaction to one of your posts
NPS Response SentA user has sent an NPS response

Below are tables describing the properties specific to each type of events sent by Beamer.

Post Viewed

post-viewed page anchor
Property NameDescription
postTitle of the post viewed
languageTwo-letter language code for the post viewed (e.g en, es, fr, etc.)
originSource from where the Beamer view came (can be Sidebar, Standalone, Notification, API or Intercom)

Push Notification Clicked

push-notification-clicked page anchor
Property NameDescription
postTitle of the post that triggered the notification
languageTwo-letter language code for the post (e.g en, es, fr, etc.)
urlFull URL to which the user was redirected
Property NameDescription
postTitle of the post where the comment was sent
commentFull text of the comment
Property NameDescription
postTitle of the post where the reaction was sent
reactionType of reaction sent (can be positive, neutral or negative)
Property NameDescription
scoreNumeric score (0-10) sent by the user
commentFull text of the comment sent after scoring (if available)

Now that your Source is set up, you can connect it with Destinations.

Log into your downstream tools and check to see that your events are populating and they contains all the properties you expect. If all your events and properties are not showing up, refer to the Destination docs for troubleshooting.

If you experience any issues with how the events arrive in Segment, contact the Beamer team.