LTV forecast ingestion

1. Endpoint and Authentication

  • LTV forecasts are provided through CSV file upload via REST API
  • The endpoint follows the format https://ltv.bubbleye.com/{network} – E.g.:
    https://ltv.bubbleye.com/ironsource
  • Authentication happens through Bearer token, to be provided by Bubbleye upon project start

2. Upload Frequency

  • Recommended: at least daily, ideally hourly (no strict requirement)
  • No matter the frequency, the Kraken will utilize the most recent CSV available. It will be notified as soon as new LTV forecasts are available, and will immediately update bids and allocate budgets accordingly

3. Data Format

  • Expected one .CSV file per network, named however convenient, uploaded to the specific network folder
  • The file must follow the standard CSV specifications: https://tools.ietf.org/html/rfc4180
  • Columns expected in each CSV:
    • app: your app’s android package name or iTunes app id in pure digits – e.g. “com.rovio.angrybirds2” or “880047117”
    • geo: the 2-letter identifier of the country that a certain LTV originates from – e.g. “US” or “DE”
    • pub_id: network specific publisher ID or site ID as utilized in blacklists or site-level bids – e.g. “1019221”
    • creative_type: the type of the creative that generated a certain LTV from the specific publisher in the specific geo. Must be either of the following:
      • “image” (for image-only ads, such as banners or static interstitials)
      • “video” (for all video ads, with or without complementary start- or end-card images)
      • “playable” (for html5 interactive ads)
    • *creative_id: the ID of the creative responsible for a certain LTV on the specific network – e.g. “abc123” [Optional]
    • *creative_name: the Name of the creative responsible for a certain LTV on the specific network – e.g. “Angry Birds 2” [Optional]
    • installs: the total amount of installs originated from the specific publisher in the specific geo with the specific creative, which the LTV forecast is based upon; this will be used by the Kraken to intelligently administer bids and budgets across established publishers and early stage publishers
    • dx: the cohort size used for defining LTV – e.g. “180” if LTV is defined as “D180 ARPU”
    • dx_arpu: the LTV forecast for the specific publisher in the specific geo with the specific creative