Find answers to your broad questions here
Choose a Self-serve plan on a monthly subscription or an Enterprise agreement on a yearly license.
Self-serve plans are scaled depending on your usage, to help you choose based on your catalogue size and monthly traffic.
The Enterprise plans are for if you want us to work with you in areas such as trial setup, implementation support and guidance, commercial advice, and UX best practice. You also have access to Bibblio's personalization solution. In-person support channels and a service-level agreement guarantees a lasting relationship that will pay dividends.
A content item is any article or page within your catalogue that you want to provide recommendations from and to. Sets of metadata are collected for each content item, which are then stored.
Only the API calls to Bibblio's recommendation endpoint count towards your plan's monthly limit. An API call of this kind results in related posts being delivered for the post you’re currently viewing.
If you have a Bibblio pre-designed module on your site, the number of API calls will equate to your number of pageviews. So 1M page views = 1,000,000 API calls per module.
No, there are no extra costs to signing up to a Self-serve plan.
All major debit and credit cards are accepted. For our paying Self-serve plans, you will be invoiced at the beginning of each month for the previous month.
The Enterprise plan can be settled annually by mutual arrangement.
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.
We have Master Account functionality coming soon, but in the meantime it is advisable to create one Bibblio account per domain.
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 poitning to staging URLs.
Once signed up you can get going instantly by adding a code snippet to the pages you wish to recommend from and to. Our Quick Start 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.
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 English, Dutch, French, German, Italian, Mandarin, Polish, Portuguese, Russian, Spanish and Swedish.
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.
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, without gathering any personal user data.
They do! Our modules are fully responsive, collapsing gracefully for display on the smallest devices.
If you are installing Bibblio via our Wordpress plugin or our Quick Start code, you will have to use our pre-built modules.
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 build your own module but you will have to send us tracking events in order to get the recommendations to improve over time.
We offer support across all major browsers (Chrome, Firefox, Safari, Brave 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 serve our assets via our own CDN for a faster installation and easy access to latest versions. If you are thinking of doing an API integration and would like to host the assets yourself instead they can be installed via Bower and npm.
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 organize your content to ensure that certain topics and genres are only recommended on certain parts of your platform.
If you are planning to do a full API integration, you can learn more about catalogue management.
If you are using our Quick Start wizard, learn how to sort your items into catalogues.
Our WordPress plugin does not support the catalogue functionality. If you are a WordPress plugin user who really wants catalogues, talk to us about switching integration method.
Yes, our Syndication tool lets you share your content with, or exclusively receive content from, other publishers you've agreed to partner with. Find out more about Syndication.
Our dashboard allows you to see how many enriched content items you have imported to Bibblio and how many recommendations have been served and clicked on a monthly basis.
We also report on two crucial metrics: click-through rate and in-view click-through rate. The first gives you the ratio of module clicks to API calls, but the second gives you the ratio of clicks to module views. This can be very helpful if the module is placed below your articles, as it determines how many users reached the bottom of the page.
You can also add tracking parameters to the module and monitor your Bibblio audience directly from your Google Analytics or similar platforms.
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.
We do all the caching on our side, and our JS and plugin are optimised for page speed.
During installation, this will depend on the size of your corpus and your integration method:
For WordPress plugin users, we run a WordPress cron job that imports 100 posts every five minutes.
For Quick Start wizard users, we rely on users visiting a page to trigger the import. Once we receive a url request it will take a few minutes before it appears in the Content section of your Bibblio account, but may be longer if you are hitting our servers with a lot of URL requests. Our module can run in hidden mode so you can import all your content before your readers get to see the recommendations.
For API users, you can expect the response times for content item ingestions to take between 150ms and 1000ms on average.
After the initial onboarding, every time you publish a content item, importing will be much faster, so you should expect to see it in your storage within 5-10 minutes.
On average, you can expect recommendations to take between 150ms and 1000ms to load. We only load the module once your page has finished loading to avoid slowing down your site.
After 48 hours of gathering interaction data, we will automatically generate a set of popular recommendations. These will be displayed as temporary recommendations for every newly published content item whilst we're busy indexing it. This means you will never be without a set of recommendations on a page.
Yes we are. We do not process any personal information from visitors on a customer's page, and we only process personal information from our customers when strictly necessary to provide our services. We are committed to being fully transparent regarding our processing of customers' data. We are happy to provide a compliance statement upon request.
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 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.