Help with enrichment and discovery
Yes, you can. We recommend keeping two separate accounts for your staging and live environments, or alternatively contact us so we can clear your catalogue once you’re done testing. This is to avoid recommendations on your site pointing to staging URLs.
When we speak about discovery, we mean the process through which a user finds and interacts with content, whether that’s by traditional search, on-platform content recommendations, or in the form of a personalized newsletter.
Recommendation keys are Bibblio’s own access tokens you will need to access recommendations.
These keys are distinct from the standard OAuth mechanism for two important reasons:
We only use the text to generate metadata. All other information you send us (tags, keywords, type of resource, etc) will not affect the indexing and is only there to organise your content and give you control over what you want to display on the module.
We store the source URL and module image URL when you add the content, so we can easily populate the module and don’t double up on server storage. When the user clicks, we simply send the user to the original content URL.
Read our guide on how to get started.
We recommend using our elegantly designed modules that are ready to go and fully customizable, for a faster installation. You can use CSS to override our style classes and make it match your site’s design. We track user behaviour and generate analytics stats through these modules, meaning you will immediately get visibility over the module’s performance from the moment it is live on your page.
When doing an API integration you can also build your own module but you will have to send us tracking events in order to get the recommendations to improve over time.
Content needs to be formatted in valid JSON to be pushed to our API via a POST request.
The maximum size for an individual item of content is currently 200 KB.
We only require the following fields in order to generate recommendations: “url”, “text”, “name”.
We strongly recommend you add an image in “moduleImage”, and the “datePublished” if you are planning on using our recency parameter. A little excerpt of the article in “description” is also a nice-to-have if you’re planning on giving more information to the user when they hover over a recommendation.
The rest is entirely up to you and will depend on your internal taxonomy. Most of our API users supply a “customUniqueIdentifier” to match our content items to their internal blueprint.
We follow the Schema.org CreativeWork format for attributes on content items. If you want to send us some information about a content item that does not correspond to any of the ones we already have, let us know which one and we’ll look to incorporate it in the next release.
Content items can be grouped into what we call ‘catalogues,’ which means you can organise your content to ensure that certain topics and genres are only recommended on certain parts of your platform. It can also be useful if your site supports different languages. Learn more about catalogue management.