/
Data Storage

Data Storage

GumGum Contextual stores information for processed request URLs in the GumGum Contextual database. Data stored includes:

  • Page and Video classifications

  • Page metadata

  • Image metadata

  • Video metadata

If a request for a processed page URL is received, GumGum Contextual recreates a JSON response based on the stored data (unless the ignoreCache flag is explicitly set for a page analysis request).

Time to Live (TTL) for GumGum Contextual Data

JSON response data is maintained by GumGum Contextual for a time-to-live (TTL) period. There are different TTL periods for Page, Video, Image, and Text content.

Pages are further analysed to differentiate between website home pages and all other pages on the site (as website home pages typically update frequently). For example, https://www.latimes.com/ (the home page of the Los Angeles Times) updates frequently, so GumGum Contextual assigns a TTL of 30 minutes. The page https://www.latimes.com/travel/list/la-best-dog-friendly-hikes-trails-beaches-parks is unlikely to be updated frequently, so GumGum Contextual assigns a longer TTL of 30 days.

GumGum Contextual considers a home page to be a web page accessed at either:

  • <website URL>/

  • <website URL>/index.html

Content Type

Default TTL

Content Type

Default TTL

Page

Website home page

30 minutes

All other pages

30 days

Video

360 days

Image

14 days

Text

30 days

Every GumGum Contextual response includes processedAt and expiresAt fields, indicating the date and time that classification data was generated and will expire from GumGum Contextual storage:

"processedAt": "2021-05-25T17:57:03.690Z" "expiresAt": "2021-06-24T17:57:03.690Z"

GumGum backs up GumGum Contextual page and video analysis classification data for 11 months. The page, image, and video metadata is backed up for 180 days.

Client Cache TTL Configuration

GumGum expects clients to store GumGum Contextual classification result data in their own environment. GumGum recommends that clients configure a TTL of at most 30 days for their cached classification data. Beyond the configured TTL period, updated classifications can be requested from the GumGum Contextual API.

Note: Although GumGum recommends a TTL of at most 30 days, the configuration of caching parameters is at the discretion of the client.



Related content


The contents of these documents and any attachments contain GumGum, Inc. confidential information and are legally protected from disclosure.