Bound - Help Center

Bound Technical Integration Quickstart

This Quickstart Guide provides the information necessary to quickly integrate the Bound Tag (the "Tag") into a website. This guide only covers the integration of your website and the Tag, and does not cover the creation or operation of personalization campaigns.

Implementation Overview

The successful integration of Bound with your website is as simple as dropping a line of HTML code into the header of your global page templates.

How Bound Personalizes Content for Visitors

Bound personalizes the content for a visitor based on a variety of data and visitor characteristics.  Data sources include visitor behavior (which of your pages have they visited?); browser/device technology (mobile OS, cookies, etc.); and a number of third-party data providers that you may integrate for demographic, firmographic, or ABM segmentation.

On each page load, Bound retrieves and analyzes the available data about a user, determines if the page qualifies for any content personalization, and, if so, updates the page source with the appropriate personalized content for that user. That content (including images, HTML, JavaScript, and/or CSS) is usually delivered from the Bound CDN and then dynamically injected into the page, personalizing the experience for that user. The content to be replaced, the visitors for whom it is replaced, and the pages on which it is served are all defined by cascading rules in the Bound Admin web application.

All personalization happens browser-side — there is no requirement for a server-to-server integration.

The Bound Tag

The Bound tag is a snippet of HTML that must be added to the head section of every page to enable personalization. The Tag captures visitor data to be used in targeting and facilitates the personalization of content on the page.  For best results, you should implement it as a basic script element that loads the Bound file synchronously, though it may be included via a tag manager, such as Google Tag Manager or Tealium (See Adding the Bound Embed Code via Google Tag Manager for more information.).

Note You must pull the live copy of the Bound file directly from the Bound CDN.  Do not attempt to use a cached copy stored on your own server; the Bound library is updated frequently with new features, improvements, bug fixes, and campaign configuration changes, and your copy must be up-to-date.

Bound segments your digital properties into "Websites". Each Website requires a Tag with its own unique Website ID (file name).  The recommended embed code for a Website's Tag can be found in the Bound Admin by accessing each Website's Settings menu from the top right navigation bar, and it will also be provided to you by your Customer Success Manager.  The Tag dialog will also confirm successful implementation after you have added it to your site.


This code can be copied directly into individual web pages; however, for ease of implementation, most customers add it to a list of global header includes for each site (this general concept is implemented in various ways across different content management systems and website frameworks — see your platform's documentation for more information).


Once the Tag is included on all of your pages, you and your marketing team will be ready to start personalizing content for visitors based on site behavior.

Using Bound in a Staging Environment

If you use a staging environment, you can simply include the same Tag with the corresponding templates in that environment. You may then configure your Campaign locations or Rule Filters in the Bound Admin to target the production site and/or the staging environment with new campaigns and personalized content.


If you have any other questions regarding basic implementation of the Bound tag, please contact your Customer Success Manager or create a ticket by sending an email to

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request