Find the answers here
Bibblio is available as a Self-serve or Enterprise package.
Under Self-serve, you can choose a monthly subscription plan that's sized to suit your catalog and usage needs, starting at $19 per month. You can be up and running in minutes. You can also try Bibblio for free on a starter plan, which will allow you up to 25,000 recommendation calls per month across 500 content items.
The Enterprise package is for those who want to maximize Bibblio's potential by having us work with you in areas such as trial setup, implementation guidance, commercial advice, and UX best practice. In-person support channels and a service-level agreement guarantees a lasting relationship that will pay dividends. It's the whole toolbox with a team behind you!
A content item is any article or page within your catalog that you want to provide recommendations to and from. Sets of metadata are collected for each content item, which is then stored in our Smart Graph.
A recommendation call happens when a set of recommendations is served to your web page. This is achieved via a request to the discovery endpoint of the Bibblio API.
No, there are no hidden costs to sign up.
We accept all major debit and credit cards.
If you have forgotten your password you will need to reset it. You can do so here.
Yes, you can. If you’re logged into Bibblio, just select Account and then Edit Personal Details. Your email and other details can be updated there.
Not currently, but watch this space.
Once signed up you can get going instantly by adding a code snippet to the pages you wish to recommend from and to. Our snippet wizard lets you choose how you'd like your recommendation module to look and whitelist the domains that house your content.
If you’re on WordPress, you can also get up and running rapidly by using our Wordpress plugin instead.
Alternatively, you can work with the API itself. Our documentation generates basic scaffold code for each endpoint in a wide variety of languages. You can find it by switching to the console mode on an endpoint, calling the resource, clicking Code Example, then selecting your language.
We can produce recommendations for all languages using the Latin alphabet, and we can generate in-depth semantic analysis for Dutch, English, French, German, Italian, Mandarin, Polish, Portuguese, Russian, Spanish and Swedish.
Currently Bibblio can only enrich text, but we’re working on accommodating speech and video in the near future. Get in touch if you would like to be involved in a preliminary speech or video project with us.
At the moment, content needs to be formatted in valid JSON to be pushed to our API, but we’re currently working on tools to help with URL scraping and pulling directly from RSS feeds.
The maximum size for an individual item of content is currently 200 KB.
A 422 is often because the payload is invalid. For example, required fields could be omitted or dates might be incorrectly formatted.
If that doesn’t seem to be the case, please get in touch.
Metadata is data about data. Bibblio’s metadata is split into structural metadata about the data container (the file), and descriptive metadata about the content itself, such as the relevant keywords in an article. Descriptive metadata is what Bibblio creates, and it serves as a factor in our recommendations.
If you want to dig a little deeper, check out the Wikipedia entry on metadata.
Metadata is automatically added to the content items, but it won’t appear as tags on your web page or platform unless you engineer that.
In order to make the tags generally applicable, we don’t match tags to individual client taxonomies. Any filtering of Bibblio’s tags based on a pre-existing taxonomy would have to be accomplished through logic on your side.
You may not have supplied enough text to derive concepts, keywords, entities and alignments. (Generally, a few lines of text should be sufficient.) Alternatively, the text might be in a language that our enrichment endpoint does not currently support.
Your access token is probably not valid anymore. We mitigate the risk of exposing user credentials by using a temporary token according to the OAuth2 Bearer Token authentication mechanism. You'll notice an expires_in field in the token response. Clients generally create an authorization wrapper that renews the access token according to the expires_in value provided by the token endpoint. Learn how to get a new token.
If you’re experiencing this problem while using a valid access token, please get in touch.
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.
Bibblio does not drop any cookies on the page. All user tracking is carried out from within the related content module itself, or is sent to us directly by our partners.
Not by default, but Bibblio’s technology can be used to recommend sponsored content, if required. Despite being sponsored, it will still only recommend those items that are actually relevant to the article the user is currently reading.
Yes, our recommendations are tailored to the user they’re presented to. We integrate user session data with our in-depth content analysis approach to create a more personalized recommendation experience.
bower install bibblio-related-content-module
They do! Our modules are fully responsive, collapsing gracefully for display on the smallest devices.
You can use the recommendations however you like, but our elegantly designed modules are ready to go and fully customisable. For most clients they make getting recommendations a lot more convenient. In addition, we also track user behaviour directly through our module.
We offer support across all major browsers (Chrome, Firefox, Safari etc.).
The module does not block rendering. The module populates an HTML element of your choice with content. An empty <div> (or any tag) can be rendered quickly, and the module can be initiated to fill it with content at any point during page load, such as page ready. Any delay in loading the module content will not affect the rest of the page in any way.
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.
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.
We are in the process of enabling 'open catalogues' which means that anyone using Bibblio’s service will be able to access content from our curated open catalogues or from other Bibblio clients who open their catalogues. As a client, you will also be able to distribute your content to other users.
Our dashboard allows you to see how many enriched content items you have stored in Bibblio’s Smart Graph and how many recommendations have been served, both monthly and in total.
The latency of recommendation delivery via our modules is below 400 milliseconds, which is often quicker than the other page elements on our clients’ platforms.
On average, you can expect recommendations to take between 150ms and 1000ms, and the response times for content item ingestions are roughly the same (from the UK).
When you register for a Bibblio account, we ask for your contact details and your credit card details if you are on one of our paid plans. We do not collect payment information directly and the processing of such information is made by our trusted third-party service providers.
We have access to your user ID and your Explorer page, your content items and the tracking data generated from having the module on your page.
The content items you add on Bibblio in order to generate recommendations may contain some personal information (For example, if you submit articles from your personal blog).
The anonymized metadata generated from your content gets used by Bibblio to improve our algorithms and for the purposes of fulfilling our obligations under the Terms of Service.
Our module on a customer’s page only collects anonymous data from the visitors. The module tracks data about whether a recommendation has been viewed/clicked but does not link to a specific session. Customers can access this data at any time through their Explorer page.
Our module does not drop cookies from a customer’s page during a visitor’s session.
Content items you send are deleted once you deactivate your account.
Tracking data about visitors stops as soon as you remove the module from your page.
We keep customer data such as purchase history, communication logs, and contact details up to 2 years after you stop being a Bibblio customer, unless you submit a request for deletion. After this date, data is reviewed and if deemed not necessary for any ongoing legitimate business/lawful purposes, we will either delete or anonymize it. Contact us for more detailed information about our data retention policy.
We do not sell your information to anyone.
Raw data generated from your use of the Services is only kept to improve our algorithms and isn’t shared with anyone beyond this scope.
We use a range of service providers to run our daily operations, which involves handling customer data. We only share personal information with them when strictly necessary for fulfilling our contractual obligations with the customer. Our third-party service providers all operate under a Data Processing Agreement (DPA), meaning that we only work with companies who have provided us with sufficient guarantees that the requirements of the GDPR will be met and the rights of our customers protected. We can provide the full list of service providers upon request or through the Bibblio employee you are usually in contact with.
We take several measures to ensure your data is safe with us:
Your Explorer page is secured using SSL.
Your data is only handled by our personnel and approved processors.
Our employees do not keep any customer data outside of a password-protected and/or secured network
Regarding third party service providers:
Our service providers are legally required to disclose any data breach in their system within 72 hours.
We use PCI-compliant service providers to process your payment.
All transfers involving customer data are encrypted.
Your Explorer page is secured using SSL.
We mostly rely on cloud services for data hosting, which means data may be transferred outside of countries under GDPR.
Using our services means you adhere to your information being transferred outside of your country of residence.
When third party service providers are located in the US, they all participate with and adhere to the Privacy Shield framework.