console.springserve.com Open in urlscan Pro
2600:1f18:1390:4a02:e45f:6f68:90fe:9f69  Public Scan

Form analysis
3 forms found in the DOM

POST /users/pre_otp

<form accept-charset="UTF-8" action="/users/pre_otp" class="new_user ng-pristine ng-valid-email ng-invalid ng-invalid-required" id="step_1" method="post" ng-hide="$userSessionFormCtrl.step2" role="form"> <input autocomplete="off"
    name="authenticity_token" type="hidden" value="pPUtw3WwW_XJRuaaDnBUhbSQCYAtmgFsBJ264eHFKBBgLUGytCPH6Ed4Dabak4TB2FNsObuYV-kj8CrUtjwI6w">
  <div class="form-group"> <label for="user_email">Email</label> <input autocomplete="off" autofocus="autofocus" class="form-control ng-pristine ng-untouched ng-empty ng-valid-email ng-invalid ng-invalid-required" id="user_email" name="user[email]"
      ng-model="$userSessionFormCtrl.email" required="required" type="email"> </div>
  <div class="form-group"> <input class="btn btn-ss-submit btn-block" data-disable-with="Next" name="commit" type="submit" value="Next"> </div>
</form>

POST /users/sign_in

<form accept-charset="UTF-8" action="/users/sign_in" class="new_user ng-pristine ng-valid ng-hide" id="step_2" method="post" ng-show="$userSessionFormCtrl.step2" role="form"> <input autocomplete="off" name="authenticity_token" type="hidden"
    value="pPUtw3WwW_XJRuaaDnBUhbSQCYAtmgFsBJ264eHFKBBgLUGytCPH6Ed4Dabak4TB2FNsObuYV-kj8CrUtjwI6w">
  <div class="form-group"> <label for="user_email_2">Email</label> <input autocomplete="off" class="form-control" id="user_email_2" name="user[email]" required="required" type="email"> </div>
  <div class="form-group"> <label for="user_password">Password</label>
    <div class="input-group pw-input-group"> <input autofocus="autofocus" class="form-control" id="user_password" name="user[password]" required="required" type="password"> <span class="input-group-addon clickable"
        ng-click="$userSessionFormCtrl.toggleShowPassword()">
        <i class="far fa-eye" ng-class="{&quot;fa-eye&quot;: $userSessionFormCtrl.passwordInputType === &quot;password&quot;, &quot;fa-eye-slash&quot;: $userSessionFormCtrl.passwordInputType === &quot;text&quot;}"></i> </span> </div>
  </div>
  <div class="form-group ng-hide" id="step_2_otp" ng-show="$userSessionFormCtrl.showTwoFactorFields()"> <input class="hidden ng-pristine ng-untouched ng-valid ng-empty" id="user_reset_two_factor_token" name="user[reset_two_factor_token]"
      ng-model="$userSessionFormCtrl.resetTwoFactorToken" type="text"> <label for="user_otp_attempt">Two factor authentication code</label>
    <div class="inline-block" data-placement="top" data-toggle="tooltip" title="If you cannot find your device enter one of the backup codes you downloaded."> <i class="fa fa-info-circle"></i> </div> <input autocomplete="off" class="form-control"
      id="user_otp_attempt" name="user[otp_attempt]" tyoe="tel">
  </div>
  <div class="form-group ng-hide" id="step_2_otp_remember" ng-show="$userSessionFormCtrl.showTwoFactorFields()"> <form-check-box-tag field-id="user_remember_device" field-name="user[remember_device]" label-display="Remember this device for 30 days"
      model="$userSessionFormCtrl.rememberDevice" class="ng-isolate-scope">
      <div> <input name="user[remember_device]" ng-disabled="$formCheckBoxTagCtrl.readOnly" type="hidden" value="0" autocomplete="off"> <input class="checkbox-custom ng-pristine ng-untouched ng-valid ng-empty" id="user_remember_device"
          name="user[remember_device]" ng-change="$formCheckBoxTagCtrl.formCheckBoxTagClicked()" ng-disabled="$formCheckBoxTagCtrl.readOnly" ng-model="$formCheckBoxTagCtrl.model" type="checkbox" value="1"> <label
          class="checkbox-custom-label checkbox-custom-label-sm ng-binding" for="user_remember_device">Remember this device for 30 days</label> </div>
    </form-check-box-tag> </div>
  <div class="form-group"> <input class="btn btn-ss-submit btn-block" data-disable-with="Log in" name="commit" type="submit" value="Log in"> </div>
</form>

POST https://springserve.us9.list-manage.com/subscribe/post?u=78e73646f04511c08f6bf93e6&id=3ea9bee599

<form target="_blank" action="https://springserve.us9.list-manage.com/subscribe/post?u=78e73646f04511c08f6bf93e6&amp;amp;id=3ea9bee599" accept-charset="UTF-8" method="post"><input type="hidden" name="authenticity_token"
    value="wWGqymFYVVGGBMk3X35cnpe-VQizd7subbnooaSJeCQFuca7oMvJTAg6IguLnYza-30wsSV17atK1HiU83BY3w">
  <div class="modal-header">
    <button aria-label="Close" class="close" data-dismiss="modal" type="button">
      <span aria-hidden="true">×</span>
    </button>
    <h4 class="modal-title" id="subscribeModalLabel">Subscribe</h4>
  </div>
  <div class="modal-body">
    <div class="form-group clearfix">
      <div class="required-asterisk">
        <label class="control-label" for="email">Email Address:</label>
        <input type="text" name="EMAIL" id="EMAIL" value="" class="form-control">
      </div>
    </div>
    <div class="form-group clearfix">
      <label class="control-label" for="first_name">First Name:</label>
      <input type="text" name="FNAME" id="FNAME" value="" class="form-control">
    </div>
    <div class="form-group clearfix">
      <label class="control-label" for="last_name">Last Name:</label>
      <input type="text" name="LNAME" id="LNAME" value="" class="form-control">
    </div>
    <div class="form-group clearfix">
      <label class="control-label" for="email_format">Email Format:</label>
      <div class="btn-group" data-toggle="buttons">
        <label class="btn btn-default btn-ss-default" for="email_format"><input type="radio" name="EMAILTYPE" id="EMAILTYPE_text" value="text" checked="checked"> Text </label><label class="btn btn-default btn-ss-default active"
          for="email_format"><input type="radio" name="EMAILTYPE" id="EMAILTYPE_html" value="html" checked="checked"> HTML </label>
      </div>
    </div>
  </div>
  <div>
    <div class="clear" id="mce-responses">
      <div class="response" id="mce-error-response" style="display:none"></div>
      <div class="response" id="mce-success-response" style="display:none"></div>
    </div>
    <!-- real people should not fill this in and expect good things - do not remove this or risk form bot signups -->
  </div>
  <div aria-hidden="" style="position: absolute; left: -5000px;">
    <input name="b_78e73646f04511c08f6bf93e6_3ea9bee599" tabindex="-1" type="text" value="">
  </div>
  <div class="clear"></div>
  <div class="modal-footer clearfix">
    <div class="btn-footer clearfix">
      <input type="submit" value="Subscribe" class="btn btn-ss-submit" data-disable-with="Subscribe">
      <button class="btn btn-default btn-ss-default" data-dismiss="modal" type="button">Cancel</button>
    </div>
  </div>
</form>

Text Content

Toggle navigation

Welcome to SpringServe


CLIENT LOG IN

Email

Email
Password

Two factor authentication code

Remember this device for 30 days

Or
Log in with Google
Forgot your password?
Lost second factor device?


NOT AUTHORIZED

Please contact an account administrator to enable 2-Factor Authentication.


HELPFUL LINKS

Visit Our Website
Learn more about SpringServe
View Our Platform Documentation
View SpringServe's Documentation and Best Practices
SpringServe University
Watch videos and tutorials to learn more about the platform
Contact Us
Get in touch with SpringServe


LATEST NEWS

In an effort to make reporting clearer, SpringServe is renaming select metrics
in the UI and API. No changes need to be made to API requests, but reporting
metric names are updated. This change will take effect on Tuesday, March 8th.
Supply Metrics Pod metrics have been renamed for clarity. When calling a pod
tag, SpringServe keeps track of the information about the request and its
response. Metrics have been renamed as follows, with the API metric name
displayed with this format <api_metric_name> Pod Avail Time
<ap_slots_seconds_available> → Pod Time Req <pod_time_requested> Pod Opp Time
<ap_slots_opportunity_seconds> → Pod Time Ret <pod_time_returned> Pod Fill Time
<ap_slots_seconds_filled>  → Pod Time Fill <pod_time_filled> Pod Slots Avail
<ap_slots_count> → Pod Slot Req <pod_slot_requests> Pod Slot Opps
<ap_slots_opportunity> → Pod Slots Ret <pod_slots_returned> Pod Opp Time %
<ad_pod_opportunity_rate>  → Pod Time Ret % <pod_time_returned_rate> = Pod Time
Returned / Pod Time Requested Pod Time Fill % <ad_pod_fill_rate> → Pod Time Req
Fill % <pod_time_request_fill_rate> = Pod Time Filled / Pod Time Requested Pod
Opp Fill Time % <ad_pod_opportunity_fill_rate> → Pod Time Ret Fill %
<pod_time_returned_fill_rate> = Pod Time Filled / Pod Time Returned Slot Opp %
<slot_opportunity_rate> → Pod Slot Ret % <pod_slot_return_rate> = Pod Slots
Returned / […]

The post Metric Makeover in the UI & API appeared first on SpringServe.

Metric Makeover in the UI & API

Solution enables video publishers to more intelligently integrate programmatic
campaigns into their primary ad server NEW YORK – (March 3, 2022) – SpringServe,
the leading independent TV ad serving platform, today announced the launch of
BidLink. Bidlink is designed to communicate with a publisher’s primary ad server
to send dynamic programmatic demand insights from integrated video SSPs,
enabling competition between traditional-direct and programmatic campaigns.
Publishers can leverage BidLink’s capabilities regardless of which ad server
they use.  “We developed BidLink to be the best mechanism for unifying ad
decisioning across programmatic and traditional direct-sold deals,” said Joe
Hirsch, GM of SpringServe. “BidLink provides publishers with an out-of-the-box,
fully transparent integration with over 22 SSPs. This gives publishers the
opportunity to uplevel their programmatic demand capabilities, whether or not
they use SpringServe as their primary ad server.”  “We’re excited about the
prospect of using SpringServe’s BidLink to help improve yield by holding a true
real-time auction across all demand partners,” said Tom Sly, vice president,
programmatic revenue, for The E.W. Scripps Company. BidLink communicates with a
publisher’s primary ad server to send dynamic programmatic demand insights from
integrated video SSPs, including price, ad category and priority levels, to help
better inform decisioning […]

The post SpringServe Unveils BidLink, Advanced Decisioning for CTV and OTT
appeared first on SpringServe.

SpringServe Unveils BidLink, Advanced Decisioning for CTV and OTT

SXSW Will Leverage SpringServe’s Ad Serving Technology to Deliver High Quality
Video Ad Experiences to Attendees NEW YORK – March 2, 2022 – SpringServe, the
leading ad serving platform for connected TV (CTV), today announced a strategic
collaboration with SXSW, to power inventory on their video on demand content,
both online and on the SXSW TV apps. SpringServe’s advanced ad serving and
inventory management technology helps publishers streamline their monetization
to capture the full value of their inventory, all while ensuring high quality ad
experiences. SXSW will leverage SpringServe to ensure high-quality in-app video
advertising experiences for attendees. “We created SXSW TV to provide our
audience with a premium viewing experience wherever they are. SpringServe’s
industry-leading technology has allowed us to effortlessly connect our sponsors
to our audience in new and exciting ways,” said Justin Bankston, CTO, SXSW. With
their online schedule and connected TV apps, SXSW is able to bring its amazing
content directly to attendees, whether they are in the audience in Austin or on
the other side of the world. The chronological and geographic barriers have all
come down, for both the creators who make the event, and the audience eager to
learn from them. In the […]

The post SpringServe Powering Video Advertising on SXSW TV Apps appeared first
on SpringServe.

SpringServe Powering Video Advertising on SXSW TV Apps

Magnite and SpringServe to power OTT video advertising on CH Media’s streaming
platform oneplus SWITZERLAND – March 3, 2022 – Magnite (NASDAQ: MGNI), the
world’s largest independent sell-side advertising platform, today announced that
leading Swiss media company CH Media will leverage the Magnite SSP and
SpringServe ad server to monetize its video inventory across CTV, online video
(OLV), and mobile. Magnite’s robust platform provides CH Media with technology
for premium, long-form video and supports the high-quality viewing experiences
that this content demands. By also leveraging the SpringServe ad server, CH
Media will benefit from reduced complexity, better inventory management, and
enhanced functionality.  “We are very selective about the ad technology
providers we work with and it’s important for us to align with those who
understand the intricacies of the video landscape and have a digital-first
perspective, particularly as we grow our CTV business,” said Roger Elsener,
managing director at CH Media Entertainment. “With Magnite and SpringServe’s
strong CTV and video capabilities, we’re excited about the potential this
collaboration will bring.”  CH Media is the leading provider of high quality
entertainment in Switzerland and reaches more than 3 million viewers daily
across all of its channels. In late 2021, they launched […]

The post CH Media Selects Magnite as Primary Programmatic SSP and SpringServe as
Ad Server appeared first on SpringServe.

CH Media Selects Magnite as Primary Programmatic SSP and SpringServe as Ad
Server
Subscribe
×

SUBSCRIBE

Email Address:
First Name:
Last Name:
Email Format:
Text HTML



Cancel
Read More News and Releases >>