Using Country, Language, and Source Contexts
GVD provides Contexts to help deliver data based on Country and Language. This is useful to target content to specific audiences and regions. For example, any Program object is derived by combining two context objects: its primary context object and one or more of its relevant context objects.
Context Object Types
Primary Context Object
The primary context object consists of attributes that apply to every instance of that Program object, regardless of the target country or language.
Relevant Context Objects
The relevant context objects are specific to the target country, the language, or both. The most relevant context is the one that is most specific to your use case and target audience.
Context Examples
Examples of relevant contexts include:
- The context object matches the Country/Language of the desired Program (A Country/Language or CL context)
- The context object matches just the Language of the desired Program (A Language or L context)
- The context object matches the Source ID of the catalog it is in (A Source or SRC context)
Context Combinations
With this model, you can combine the primary context object along with the most relevant context object to retrieve the best program object for your use case. For example:
Primary + _enspecifies the English context programPrimary + us_enspecifies the USA English context programPrimary + esspecifies the Spanish context program
Context Types
There are three kinds of Contexts:
| Context | Description |
|---|---|
CTX_CL_<country_iso_code>_<lang_iso_code> | Represents the Country/Language Context for a specific market. Attributes that define these are typically Market Original Air Date (Releases), Schedule/Catalog Rating, and Alternate Season Episode for a market (Source) |
CTX_L_<lang_iso_code> | Represents Language Context of the Program. |
CTX_SRC_<GNID_of_source> | Represents the specific Source Context. |
To see how Contexts relate to other objects and entitlement, see Data Delivery Model and GVD endpoints.
Note: Catalog endpoints automatically point to the most relevant context.