Youbora Source


This is an Event Cloud Source which can not only export data into your Segment warehouse, but they can also federate the exported data into your other enabled Segment Destinations.

This source is maintained by YOUBORA. For any issues with the source, you may contact their team.

NOTE: Youbora is currently in private beta and this doc was last updated on July 2nd, 2018. This means that there may still be some bugs for us to iron out and we’re excited to hear your thoughts. If you are interested in joining or have any feedback to help us improve the Youbora Destination and its documentation, and please let us know and your YOUBORA representative know!

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.

Adding YOUBORA as a Source to Segment will allow you to leverage 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.

Getting Started

  1. From your Sources page in Segment, click Add Source.
  2. Choose YOUBORA.
  3. Click Connect.
  4. Give the Source a nickname. The nickname is a label used in the Segment interface.
  5. Copy the Segment write_key for YOUBORA from the Overview page.
  6. Reach out to your YOUBORA representative to enable the event-source with the write_key provided.
  7. Click Save.
  8. 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.

Components

Stream

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.

Events

For now, YOUBORA is sending all the auto-tracked events as Youbora Event

YOUBORA Event Properties

Below is a table outlining the properties included in the event listed above.

Property Description Magnitude
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 Avg fps fps
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
browser_name Browser name
browser_ver Browser version -
buffer_ratio Buffer ratio (buffer time / viewtime) Double
cdn Cdn name
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_model Device-model -
device_name Device name
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_metadata Error metadata -
error_player_code Error Code reported by plugin -
error_player_desc Error Player reporder by plugin -
error_severity Error severity -
error_type Error type -
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
happiness_score_label Happiness tag -
ip Detected IP from user -
isp Detected isp from user -
lat Latitude double
lon Longitude double
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 -
os OS name -
os_version OS version -
out_bytes Traffic consumed on the view (represented on bytes) Bytes
play_time PlayHead of content on current event in seconds Seconds
player Player name -
player_version Player version -
plugin_metadata Plugin metadata (advanced details about plugin) -
plugin_version Plugin version -
postal_code Detected postal code from user -
region Region
rendition First rendition at start -
state_province State or Province detected from user -
streaming_protocol Streaming protocol
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
title View title -
title2 View channel title (or secundary title) -
token View unique identifier -
transaction_code Transaction code -
type_view LIVE / VOD -
user_agent User Agent detected by the data collector -
user_id User identifier -
user_type User type
viewtime Viewtime in milliseconds (from start to stop) Milliseconds

Adding Destinations

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 there are any issues with how the events are arriving to Segment, please contact the YOUBORA team.

User Identification

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.

Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
or
Create free account