3rd party analytics tracking for media hubs

The purpose of this document is to describe how 3rd party analytics tracking for media hubs is set up and configured.

A media hub can be implemented in 2 possible ways:

1. A reverse-proxy, in which pages are served by Creatable, a header and footer endpoint is provided to Creatable for page rendering purposes.
2. An embeddable media hub, in which a javascript widget is provided and renders the body content of an existing web page that already has a header and a footer.

Reverse-proxy media hub

A media hub that is deployed using a reverse-proxy combines a header & footer provided by the ecommerce platform and integrates it with the media hub pages through a page rendering and publishing process.

Since the header & footer of the page are provided by the ecommerce platform, this lets you control the content that is provided to Creatable for the generation of these pages. All of the resources (tag manager, style sheets, scripts, etc…) required to make the page function, including an analytics system such as Google Analytics or Adobe Analytics, are included in the page that is provided by the ecommerce platform, to enable full control and flexibility by you.

Embeddable media hub

A media hub that is deployed using an embeddable script, exists inside the context of an empty page that is generated and served by the ecommerce platform. By virtue of this, all of the existing resources, including an analytics system such as Google Analytics or Adobe Analytics, are included in the page.

In either scenario, all of the capabilities of your analytics system are fully supported by Creatable. If you have any custom requirements, please contact your client success account manager (support@creatable.io) for assistance.