Getting Started

Before you begin onboarding, you’ll need your Onboarding pack from Publift. This contains details such as a snippet to

Overview

The onboarding process consists of several stages:

  1. Configure ads.txt on your domain
  2. Add the fuse.js header script to pages that will display ads
  3. Determine whether you will be using a Static or Dynamic Initialisation strategy
  4. Insert Fuse <div> elements (Zones) into your page which act as placeholders for ads
  5. Technical testing
  6. Pre and Post-Live Yield Optimisation

ads.txt

Your onboarding pack contains instructions for adding/modifying your ads.txt file.

Header Script

This will include a <script> snippet that must be placed in the <head> section of any page which will display ads.

For example:

<!-- Example only - DO NOT USE -->
<script async src="https://cdn.fuseplatform.net/fuse-web/tag/2/999/fuse.js"></script>

It is strongly encouraged to place this as close to the top of the <head> section as possible, as this usually improves both page yield and technical measures of user experience such as Core Web Vitals.

Static or Dynamic Initialisation?

When integrating fuse, it is necessary to determine how the fusetag will initialise.

  • Statically Initialised sites are those where the page is generated by the server, and sent to the client to be rendered.
  • Dynamically Initialised sites (including Single Page Applications) are those where the initial page is partly fully generated in the client browser using Javascript.

Pages which initialise statically, i.e. the browser sends the initial HTML verbatim are considered Statically Initialised, even if subsequent user-interaction with the page (such as viewing an Image Gallery) causes client-side Javascript to modify the DOM.

Publift make this distinction because Statically Initialised sites send a reliable signal, Document.docReady, that the document is complete and therefore that all Zones have been inserted.

With Dynamically Initialised sites, Document.docReady can be misleading because it may signal ‘complete’ even if components responsible for inserting Zones haven’t finalised.

Publift will remotely adjust the tag configuration depending on whether your site is Static or Dynamic. If unsure which category your site belongs to, please discuss with Publift and we will help make the determination.

Zones

Zones are regular <div> elements which act as placeholders for ad-insertion. Each Zone has a mandatory data-fuse attribute, which determines the ad format/size/etc to be used.

In your onboarding pack, you will receive a list of Zones, and an associated guide visually showing where they should placed on the page.

For example:

<!-- 71161633/your-company/home_hrec_1 -->
<div data-fuse="1234567890"></div>

<!-- 71161633/your-company/home_hrec_2 -->
<div data-fuse="987654321"></div>

Insertion requirements differ between static and dynamic sites, so please proceed to the appropriate guide.