Content categorization forms a crucial element in Rayn's approach to data organization and analysis. This process is instrumental in enabling Rayn to create refined user cohorts, which are essential for targeted marketing strategies.
Essential Step in Data Processing:
Content categorization is not just a preliminary step but a core necessity in Rayn's data processing. It sets the stage for the creation of user cohorts, which are vital for personalized marketing campaigns and audience segmentation.
Utility Beyond Rayn's Internal Processing:
The context data derived from content categorization extends its utility beyond Rayn's internal mechanisms. This data can be directly applied on the page level, offering enriched insights for analytics purposes. Additionally, it can serve as an asset in enhancing monetization strategies. The integration with prebuilt adtech connectors allows for seamless application in advertising and marketing initiatives.
Guide to Working with Context Data
Understanding the Categorization Process: The categorization process involves analyzing page content and classifying it into relevant categories. This classification is based on predefined parameters and industry standards, ensuring relevance and accuracy.
Leveraging Context Data in Analytics: By incorporating context data into analytics, marketers gain a deeper understanding of user interactions and preferences. This insight is invaluable for optimizing content strategy and user engagement metrics.
Enhancing Monetization Efforts: The utilization of context data in conjunction with adtech connectors opens avenues for more effective monetization. It allows for targeted advertising, better alignment of marketing messages, and improved ROI on advertising spends.
Understanding the Categorization Process
Check for context
Rayn JS handles the obtaining and caching of content categories to ensure that context .
Are content categories present in local storage?
Check the Context API if the website content has changed. If website content has changed since the last time it was processed then the website content will be sent to the Context Engine for reprocessing.
Get content categories from Context API. If there are no content categories stored for the given URL then the website content will be sent to the Context Engine for processing and the Context API will return a 202 until the processed categories are available.
When the Context API returns the content categories they are stored in local storage.
Content Ingestion
Rayn JS obtains the content on the webpage and sends it into the content stream. More on how Rayn JS can be configured to selectively obtain content can be found here. If Rayn JS content ingestion is left without any restrictions then it will send the entire page body for ingestion. It is advisable to set some restrictions to have higher content relevance.
Note
Processing is not a real time process and can take up to an hour depending on the load. The first users on a new page will not receive content categories until the page content has been processed.
Content categorisation
The ingested content is placed in a queue for processing in the context engine. Once the content is processed it is stored in the Context DB which contains the mapping of URL to contextual categories.
Content reprocessing
There maybe situations where pages content changes over time. Rayn tracks changes in website content and will reprocess the content if the content has changed.
Obtaining content categories
The content categories can be retrieved on page using the Rayn JS API functions.
Context categories and ad tech
Integrations with Google Ad Manager and Prebid come as a part of Rayn JS. Learn more about how Rayn JS interfaces with GAM here and Prebid here.