Good to know: Event source
The Youbora Source is an event 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.
YOUBORA is the most advanced and holistic suite of integrated video analytics and business intelligence for broadcasters, OTTs, telcos and media companies to help you make data-driven, business, operational and technical decisions to drive performance and maximize revenue across your entire video service. The latest version of YOUBORA has been thought through from the ground up to deliver the most detailed intelligence for your service.
This source is maintained by YOUBORA. For any issues with the source, contact the YOUBORA Support team.
This document is about a source which is in beta
This means that the Youbora Source is in active development, and some functionality may change before it becomes generally available.
Adding YOUBORA as a Source to Segment will allow you to use YOUBORA data with other Segment collected data.
These events can be passed to your Segment Destinations such as data warehouses and analytics tools. Joined with data from other marketing programs, you can start telling a unified story of each customer’s journey and tailor your reporting to the KPIs that matter most.
- From your Sources page in Segment, click Add Source.
- Choose YOUBORA.
- Click Connect.
- Give the Source a nickname. The nickname is a label used in the Segment interface.
- Copy the Segment
write_keyfor YOUBORA from the Overview page.
- contact your YOUBORA representative to enable the event-source with the
- Click Save.
- From your Segment account, click into your YOUBORA Source and you will be able to add other downstream Destinations where you want to see the YOUBORA auto-tracked events.
You’re all set! YOUBORA auto-tracked events will now be sent to Segment and any other destinations that you’ve enabled.
YOUBORA uses our stream Source component to send events to Segment. These events are then available in any destination that accepts server-side events, including your data warehouse.
For now, YOUBORA is sending all the auto-tracked events as
YOUBORA Event Properties
Below is a table outlining the properties included in the event listed above.
|ad_campaign||Ad Campaign name||-|
|ad_duration||Ad media duration in seconds (duration of ad content)||-|
|ad_init||Init time for current ad||Milliseconds|
|ad_number||Ad number for current position: From 1 to N||1…N|
|ad_play_time||Ad play head for current event (playtime)||-|
|ad_position||Ad position (Pre / Mid / Post)||-|
|ad_resource||Ad url resource||-|
|ad_status||Ad status: Skipped / Finished||-|
|ad_title||Ad title name||-|
|ads_time||Ads time in milliseconds||Milliseconds|
|anonymous_user||Anonymous user token|
|asn||Detedted asn number||-|
|avg_bitrate||Avg bitrate in the view (bps)||bps|
|avg_bitrate_count||Number of ping received with bitrate||Number|
|avg_fps_count||Number of pings with fps informed||Number|
|avg_latency||Avg latency (in milliseconds)||Milliseconds|
|avg_latency_count||Number of pings with latency informed|
|buffer_ratio||Buffer ratio (buffer time / viewtime)||Double|
|city||Detected city from user||-|
|connection_type||Detected connection type from user||-|
|country_code||Detected country (ISO Code 2) from user||Country code ISO-2|
|device_type||Device type (table, pc)||-|
|device_vendor||Device vendor (sony, apple)||-|
|domain||Domain from which events have been received||-|
|duration||Media duration in seconds||seconds|
|effective_time||Effective time in milliseconds (viewtime minus ads, buffer, jointime, seeks, etc)||Milliseconds|
|error_player_code||Error Code reported by plugin||-|
|error_player_desc||Error Player reporder by plugin||-|
|event_time||Event time represented in unixtime (UTC). Get as "timestamp" on NiceDruidLib||Milliseconds|
|event_type||Event Name: PLAY, STOP, BUFFER, etc…||-|
|event_value||Event value for the current event, for error for example, is the error code||Depends of the event|
|exit_ad_status||Exit Ad Status value: "ExitOnAds" for example||-|
|exit_status||Exit status: Stopped or Expired||-|
|exit_type_crash||Exit type crash||-|
|extraparam1||Extraparam 1 provided by plugin / customer||-|
|extraparam10||Extraparam 10 provided by plugin / customer|
|extraparam11||Extraparam 11 provided by plugin / customer|
|extraparam12||Extraparam 12 provided by plugin / customer|
|extraparam13||Extraparam 13 provided by plugin / customer|
|extraparam14||Extraparam 14 provided by plugin / customer|
|extraparam15||Extraparam 15 provided by plugin / customer|
|extraparam16||Extraparam 16 provided by plugin / customer|
|extraparam17||Extraparam 17 provided by plugin / customer|
|extraparam18||Extraparam 18 provided by plugin / customer|
|extraparam19||Extraparam 19 provided by plugin / customer|
|extraparam2||Extraparam 2 provided by plugin / customer|
|extraparam20||Extraparam 20 provided by plugin / customer|
|extraparam21||Extraparam 21 provided by plugin / customer|
|extraparam3||Extraparam 3 provided by plugin / customer|
|extraparam4||Extraparam 4 provided by plugin / customer|
|extraparam5||Extraparam 5 provided by plugin / customer|
|extraparam6||Extraparam 6 provided by plugin / customer|
|extraparam7||Extraparam 7 provided by plugin / customer|
|extraparam8||Extraparam 8 provided by plugin / customer|
|extraparam9||Extraparam 9 provided by plugin / customer|
|happiness_score||Happiness score double value (from 0 to 1)||Double|
|ip||Detected IP from user||-|
|isp||Detected isp from user||-|
|media_resource||Media url resource||-|
|metadata||Json object with media info||-|
|node_host||Node Host (CDN info)||-|
|node_type||Node Type (CDN info)||-|
|offline_view||String that represents if is offline view||-|
|out_bytes||Traffic consumed on the view (represented on bytes)||Bytes|
|play_time||PlayHead of content on current event in seconds||Seconds|
|plugin_metadata||Plugin metadata (advanced details about plugin)||-|
|postal_code||Detected postal code from user||-|
|rendition||First rendition at start||-|
|state_province||State or Province detected from user||-|
|streaming_type||Streaming Type (is P2P or not)||-|
|system_id||System ID (integer value), for example Antena 3 TV is "65"||-|
|throughput||Avg throughput in the view (bps)||bps|
|throughput_count||Number of ping received with throughput||Number|
|title2||View channel title (or secundary title)||-|
|token||View unique identifier||-|
|type_view||LIVE / VOD||-|
|user_agent||User Agent detected by the data collector||-|
|viewtime||Viewtime in milliseconds (from start to stop)||Milliseconds|
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 YOUBORA team.
YOUBORA will only send in events that have a value for a
userId. You must send in the same value for
userId to YOUBORA as you are sending into Segment.
This page was last modified: 15 Oct 2020
Questions? Problems? Need more info? Contact us, and we can help!