Data integration

Systems integration solutions represented by digital connections graphic

Empowering publisher with integrated BI

1: Disparate enterprise data


A world-leading publishing group was struggling to extrapolate data for reporting. With more than 6,500 employees and numerous sites worldwide, the publisher dealt with huge volumes of data.


At the same time, the company had no central viewpoint for company-wide sales and inventory information, while data had to be manually extrapolated and translated into actionable insights.

2: Bespoke integration and search


Our solution was to integrate data feeds from multiple systems worldwide into a single location. This gave an aggregated view of data for products, sales, and customers. Our team designed, built, and implemented an enterprise data warehouse that we called the Books Management Information System (BMIS).


The final step was a browser-based PHP system that let over 1,000 users perform searches and enquiries via 200 screens and send outbound data feeds to internal applications through APIs.

3: A single source of business truth


The BMIS now handles data for 150 inbound feeds, half a million titles, and millions of sales records on a daily basis. A higher SAP BusinessObjects Universe was created to produce reports for business intelligence. Our timely intervention resulted in reduced costs, a streamlined system, and improved ROI with the scope to grow further.


Is disparate data slowing your growth?

Our integration team will provide a solution.


15th May 2020
integration, data, publishing, PHP, development

Privacy Preference Center




Analytics cookies collect information that is used either in aggregate form to help us understand how our Websites are being used or how effective our marketing campaigns are, or to help us customise our Websites for you.

Google Analytics
The cookie _gcl_au is used by Google Analytics to understand user interaction with the website.

For example, in order for Google Analytics to determine that two distinct hits belong to the same user, a unique identifier, associated with that particular user, must be sent with each hit.

The analytics.js library accomplishes this via the Client ID field, a unique, randomly generated string that gets stored in the browsers cookies, so subsequent visits to the same site can be associated with the same user.

By default, analytics.js uses a single, first-party cookie named _ga to store the Client ID, but the cookie's name, domain, and expiration time can all be customized. Other cookies created by analytics.js include _gid, AMP_TOKEN and _gac_. These cookies store other randomly generated ids and campaign information about the user.

Google Analytics
_gcl_au, _gid, _ga, gtm_preview


WordPress uses cookies for authentication. That means that in order to log in to our WordPress site, you must have cookies enabled in your browser.

There are two types of cookies set by WordPress.
1 — Session cookies — These are ‘strictly necessary’ cookies as WordPress will not be able to function without it.
2 — Comment cookies — These are not ‘strictly necessary’ cookies and are set when users leave a comment on a post.

Wordpress Session cookies:
Users are those people who have registered an account with the WordPress site.

Wordpress comments:
Comments are usually turned off by default.
If by chance they are still active on a post, asides being turned off when spotted, data from these are not saved by Influential.
- When visitors comment on a post, they too get cookies stored on their computer. This is purely a convenience so that the visitor won’t need to re-type all their information again when they want to leave another comment. Three cookies are set for commenters:

Wordpress, Intercom
comment_author_{HASH} comment_author_email_{HASH} comment_author_url_{HASH} wordpress_[hash] wordpress_logged_in_[hash] wordpress_test_cookie wp-settings-{time}-[UID]