Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

IndexField NameField Data Type

Field Description

1ymdhtimestampTimestamp of the event, in UTC, in ISO format. The character "T" serves as the separator between Date and Time parts. Format: YYYY-MM-DDTHH:MM:SS
2account_idint

SpringServe account ID

3supply_tag_idintSpringServe supply tag ID
4demand_tag_idintSpringServe demand tag ID
5campaign_idint

SpringServe campaign ID

6line_item_idintSpringServe line item IDCurrently not used
7creative_idintSpringServe creative IDCurrently not used
8auction_idString (UUID)Auction ID which this event belongs to. UUIDUnique ID identifying an auction; different events can be tied together through their auction ID
9user_idString (UUID)User's SpringServe cookie ID
10user_ipStringIP address of the user
11user_agentStringFull user-agent string of the user
12transaction_typeint

SpringServe transaction type for this event

  • 1 - In-
network
  • Network/Managed (no direct-connect),
    • A supply tag in your SpringServe account sold to a demand tag in your SpringServe account
  • 2 - DC-Sold
    • The initial incoming ad request was to a (non-direct-connect) supply tag in your account, and was sold (via direct-connect) to another SpringServe account.
  • 3 - DC-DC
    • Your account bought from another SpringServe account (via direct-connect) and then sold to another SpringServe account (via direct-connect)
  • 4 - DC-Bought
    • A direct-connect supply tag bought from another SpringServe account, and sold to a non-direct-connect demand tag in your account.
13countryString (max length 2)Country code (e.g. "US", "GB", "DE")
14full_page_urlString

Full-page url that is declared on the incoming ad request.

15declared_domainString (max length128)Declared domain on the incoming ad request.
16detected_domainString (max length 128)Detected DomainDomain detected by our VPAID that the player is on.
17declared_player_sizeString (max length 7)

Declared player size. Sizes are based on width and are defined by the following groupsboundaries:

  • <= 0 - "unknown"
  • 1 <= w <= 249 - "x-small"
  • 250 <= w <= 349 - "small"
  • 350 <= w <= 500 - "medium"
  • 501 <= w <= 799 - "large"
  • 800 <= w - "x-large"
18detected_player_sizeString (max length 7)Detected player sizePlayer size detected by our VPAID. Same definitions boundaries as declared_player_size
19key_valuesJSON

Key:Values associated with the event. This field is a JSON object with String keys and String values, e.g.

Code Block
 {"our_campaign_id": "123", "user_segment": "high_value_users"}


20usable_requestsintEvent is an

Incoming ad request to a supply tag that has passed

all targeting (including

global blacklist, supply tag targeting, and pre-bid

check and tag targeting

IVT filtering (if applicable)

21blocked_requestsintEvent is a request blocked by account or supply tag targeting
22PLACEHOLDERNULLPlaceholder - column will always be NULL
23flash_opportunitiesintEvent is an opportunity (flash player-load) for a supply tag

Our flash VPAID is loaded + initialized by the player (or parent VPAID)

24js_opportunitiesint

Event is an opportunity (JS player-load) for a supply tagOur JS VPAID is loaded + initialized by the player (or parent VPAID)

25flash_impressionsintEvent is an impression Impression served (flash playerVPAID)
26js_impressionsintEvent is an impression Impression served (JS playerVPAID)
27flash_errorsintEvent is a flash player error

Error our flash VPAID fires before closing. Common causes include:

  • No impressions serve in the waterfall
  • Player or parent VPAID times our VPAID out
28js_errorsintEvent is a JS player error

Error our JS VPAID fires before closing. Common causes include:

  • No impressions serve in the waterfall
  • Player or parent VPAID times our VPAID out
29clicksintEvent is a clickVideo ad is clicked on by user
30costnumeric(16,10)Cost associated with Media cost the SpringServe account pays the supply partner (for this event)
31revenuenumeric(16,10)Revenue associated with the SpringServe account is paid by the demand partner (for this event)
32third_party_feesnumeric(16,10)Any third party fees associated with for the demand partner (for this event)
33vpaid_time_on_pagebigint

Measures how long our VPAID was on the page before being timed out by the player.

Note: this is only recorded for the supply_timeouts event. Some players may erase our IFRAME from the page before timing us out, in which case a supply timeout cannot be recorded.

34player_startsintVideo startedEvent is fired when the video player on the page starts up (via a SpringServe pixel placed in the HTML player code that is fired when the player is initialized)
35first_quartileintEvent signifies player making it Video ad has played through 1/4 of way through videoits duration.
36second_quartileintEvent signifies player making it Video ad has played through 1/2 of way through videoits duration.
37third_quartileint

Event signifies player making it Video ad has played through 3/4 of way through videoits duration.

38fourth_quartileintEvent signifies video completionVideo ad has played through its entire duration.
39missed_opportunitiesintEvent is missed opportunityA usable request that we cannot attempt to fill, due to all demand in the waterfall failing targeting
40supply_timeoutsintEvent is result of player timeoutPlayer or parent VPAID times out our VPAID
41supply_response_timebigintThe amount of time it took for our VPAID to fill an impression on the supply tag
42ad_requestsintEvent is a request to (Demand-side event) Fired any time our VPAID requests a demand tag for an ad's VAST endpoint URL
43has_adsintEvent signifies demand tag has an ad to serve(Demand-side event) VAST endpoint URL responds with a non-empty VAST response
44opportunitiesintEvent is demand tag opportunity to serve an ad

(Demand-side event) Indicates the VPAID received a non-empty VAST response / media file back from VAST endpoint URL, and initiated it

45errorsintEvent is a demand(Demand-side event) Indicates an error occurred with the demand tag. Most common case is due to the demand not filling or our VPAID timing out the demand tag
46opportunity_response_timebigint(Demand-side metric) Amount of time it takes for the demand tag to fill an impression
47opportunity_timeoutsint(Demand-side event) When our VPAID times out a demand tag for taking too long to find an ad