search

1. Gravity Field Script

hashtag
1. Implementing preconnect, prefetch & core.js scripts

On every site page in the <head> section:

<link rel="preconnect" href="//cdn-01.gravityfield.ai">
<link rel="preconnect" href="//evs-01.gravityfield.ai">
<link rel="dns-prefetch" href="//cdn-01.gravityfield.ai">
<link rel="dns-prefetch" href="//evs-01.gravityfield.ai">

Additionally, on every site page in the <head> section core.js script must be implemented:

<script type="text/javascript" src="//cdn-01.gravityfield.ai/core/core.js"></script>

hashtag
2. Implementing GF, Section ID, Page Context variables

Each page must declare a GF variable. It is declared within a separate script consisting of three parts:

<script>
window.GF = window.GF || {}; 
GF.section = "111aaa222bbb"; // Section ID, string
GF.pageContext = { type: "PAGETYPE", data: [] }; // PAGETYPE and an empty array just as an example
</script>

  1. GF variable itself;

  2. GF.section - unique section ID which must be of string type;

  3. GF.pageContext - variable passing the information about the page context and its description. In the Page Context you can pass a localization parameter lng. You can use lng in the case that your site/app is available in more than one language/region and personalization campaigns need to adjust content according to the language/region. You can also use this parameter if there are different product attributes (price/discount amount, etc) in different regions/cities. More about page context: 2. Page Context

More about scripts: Gravity Field Scripts Workflow

hashtag
Appendix

Example of correctly installed scripts on the shopping cart page:

Script connection order:

  1. Preconnect and prefetch;

  2. Declaring the GF variable and specifying a Page Context;

  3. Core.js.

PreviousClient-Side ImplementationNextGravity Field Scripts Workflow

Last updated