Skip to main content
Buzzmonitor (by E.life) is a social listening and brand-monitoring platform. It collects posts, comments, and mentions about your brands across social networks (X/Twitter, Instagram, Facebook, YouTube, Bluesky, TikTok, and more), classifies sentiment, and organizes everything into monitoring projects.
This connector uses the Buzzmonitor API with your account email and API key. If you cannot find your API key in your Buzzmonitor account settings, request it from the Buzzmonitor support team.

​
1. Add your Buzz Monitor access

  1. In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Buzz Monitor option from the list of connectors.
  2. Click Next and you’ll be prompted to fill the configuration.
    • Account Email: The email of the Buzzmonitor account used to authenticate API requests.
    • API Key: The Buzzmonitor API key of that account.
    • Monitoring Brands: The names of the Buzzmonitor monitoring brands (projects) you want to pull posts from, exactly as they appear in Buzzmonitor. You can leave it empty and use a search query instead.
    • Search Query (advanced): An optional free-text search term to filter posts (for example, a brand name).
    • Tag Query (advanced): An optional Buzzmonitor tag filter to narrow the posts.
    • Services (advanced): The social networks to search. Defaults to twitter, bluesky, facebook, youtube, and instagram.
    • Start Date (advanced): The earliest post date to sync.
    • Timezone (advanced): The UTC offset used to interpret dates (default -3.0).
    • Account Username (advanced): The Buzzmonitor account username used to reference monitoring brands. Defaults to the account email stripped of special characters.
  3. Click Next.

​
2. Select your Buzz Monitor streams

  1. The next step is letting us know which streams you want to bring. You can select entire groups of streams or only a subset of them.
    Tip: The stream can be found more easily by typing its name.
  2. Click Next.

​
3. Configure your Buzz Monitor data streams

  1. Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
    • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
    • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
    • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
    • Sync Type: depending on the data you are bringing to the lake, you can choose between INCREMENTAL and FULL_TABLE. Read more about Sync Types here.
  2. Click Next.

​
4. Configure your Buzz Monitor data source

  1. Describe your data source for easy identification within your organization. You can inform things like what data it brings, to which team it belongs, etc.
  2. To define your Trigger, consider how often you want data to be extracted from this source.
  3. Optionally, you can define some additional settings (if available).
    • Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
    • Determine when to execute an Additional Full Sync.

​
Check your new source!

  1. Click Next to finalize the setup. Once completed, you’ll receive confirmation that your new source is set up!
  2. You can view your new source on the Sources page. Now, for you to be able to see it on your Catalog, you have to wait for the pipeline to run. If needed, manually trigger the pipeline by clicking on the refresh icon.
If you encounter any issues, reach out to us, and we’ll gladly assist you!

​
Streams and Fields

Below you’ll find all available data streams from Buzz Monitor.
Every post, comment, and mention collected by the configured monitorings and filters. Synced incrementally on the post publish date.Fields:
  • post_id: String - Unique identifier of the post within its source network
  • service: String - Source network of the post (twitter, facebook, instagram, youtube, bluesky, tiktok, news, blogs, and others)
  • type: String - Kind of content within the network (post, comment, reply, video, channel, and others)
  • date: DateTime - Timestamp when the post was published on the source network, used as the incremental replication key
  • collected_time: DateTime - Timestamp when Buzzmonitor collected the post
  • content: String - Text content of the post or comment
  • title: String - Title of the content, when available
  • caption: String - Media caption, when available
  • description: String - Longer description of the content, when available
  • url: String - Public URL of the post, when provided
  • link: String - Alternative link to the content, when provided
  • sentiment: String - Sentiment classified by Buzzmonitor (positive, neutral, negative)
  • language: String - Language detected for the content
  • author: String - Author of the post — id, name, username, avatar, bio, and follower count, serialized as a JSON string
  • gender: String - Gender inferred for the author (male, female, unknown)
  • brand: String - Monitoring brand (project) in Buzzmonitor that matched the post
  • engagement: Number - Engagement metric computed by Buzzmonitor for the post
  • archived: Boolean - Whether the post is archived in Buzzmonitor
  • likes: Integer - Number of likes/reactions on the post
  • shares: Integer - Number of shares/reposts of the post
  • replies: Integer - Number of replies to the post
  • comment_replies: Integer - Number of replies on comments of the post
  • hashtags: Array of Strings - Hashtags present in the content
  • fb_reaction_love: Integer - Facebook-specific count of Love reactions
  • fb_reaction_wow: Integer - Facebook-specific count of Wow reactions
  • fb_reaction_haha: Integer - Facebook-specific count of Haha reactions
  • fb_reaction_sorry: Integer - Facebook-specific count of Sorry reactions
  • fb_reaction_anger: Integer - Facebook-specific count of Anger reactions
  • fb_reaction_thankful: Integer - Facebook-specific count of Thankful reactions
  • fb_reaction_pride: Integer - Facebook-specific count of Pride reactions
  • view_count: Integer - Number of views (video content)
  • dislikes_count: Integer - Number of dislikes (YouTube content)
  • favorite_count: Integer - Number of favorites (YouTube content)
  • interaction_type: String - Type of interaction, for networks that report it
  • video_id: String - Identifier of the parent video, for video comments and replies
  • channel_id: String - Identifier of the YouTube channel that published the content
  • channel_name: String - Name of the YouTube channel that published the content
  • page_id: String - Identifier of the Facebook page related to the post
  • real_id: String - Native identifier of the object in the source network
  • reply_id: String - Identifier of the reply, for reply records
  • content_type: String - Content type flag reported by Buzzmonitor
  • collected_from: String - Collection source that captured the post
  • origin: String - Origin of the post within the network, serialized as JSON when structured
  • application: String - Application used to publish the post, when reported
  • source: String - Original source attribution of the content
  • location_name: String - Name of the location attached to the post, when available
  • location_id: String - Identifier of the location attached to the post, when available
  • location_geo: String - Geographic coordinates of the post (latitude and longitude), serialized as a JSON string
  • icon: String - URL of the author’s avatar or icon, when provided