The $p("init") function acts as the 'start button' for all other LiftIgniter SDK functions. It must be invoked first in order to use the rest of the Javascript integration method. 

It also allows a significant number of default settings to be enabled, disabled, or modified to cover a number of special use cases or site architectures. For most integrations, there is no need to modify any of the default settings. These config options are covered below.

Settings Structure

Configs are controlled via JSON and specific key-value pairs. There are some general options available at the global config level, and several nested JSON objects that contain the settings for specific parts of the integration, like the inventory and activity tracking.

In general, we recommend placing all config options within a variable between the beacon snippet code and the $p("init") function. Here's an example with some of the more common configuration options:

<script type="text/javascript">
if (typeof $igniter_var === 'undefined') {
// Ensures that our client code is updated.
(function(w,d,s,p,v,e,r) {w.$ps = (w.performance &amp;amp;&amp;amp; w.performance.now &amp;amp;&amp;amp; typeof(w.performance.now) == "function") ? w.performance.now() : undefined;w['$igniter_var']=v;w[v]=w[v]||function(){(w[v].q=w[v].q||[]).push(
arguments)};w[v].l=1*new Date();e=d.createElement(s),r=d.getElementsByTagName(s)[0];e.async=1;
e.src=p+'?ts='+(+new Date()/3600000|0);
r.parentNode.insertBefore(e,r)})(window,document,'script','//cdn.petametrics.com/JAVASCRIPT_KEY.js','$p');
// Don't forget to REPLACE JAVASCRIPT_KEY for cdn url.

var customConfig = {
  apiRegex: /JS Regular Expression/
  sdk: {
    requestFields: ["url", "author", "title", "rank", "thumbnail", "category"],
    requestFieldsAON: true
  },
  inventory: {
    mandatoryFeatures: ["title", "url", "category"]
 }
}

$p("init", "JAVASCRIPT_KEY", {config: customConfig}); // REPLACE JAVASCRIPT_KEY
$p("send", "pageview");
}
</script>

Global Config Options

These options appear in the first level of JSON (see the apiRegex option in the sample code above)

SDK Options

These settings are nested within the sdk object in the JSON (see the requestFields and requestFieldsAON options in the sample code above)

Activity Tracking Options

These options allow the URLs picked up by our $p("track") function to be automatically rewritten. This is useful if you have different URLs for desktop and mobile (www. and m. for example), but are using only the desktop version of the URLs in your inventory. Rewriting the mobile URLs to use the desktop path will allow widget and pageview events to be correctly matched with those inventory items and can have a significant impact on recommendation quality.

Inventory Collection Options

These settings allow you to turn inventory collection on or off, and filter out unwanted items from being collected by setting requirements around fields and URL paths that must be present.

Browsing History Options

Very rarely used, these options modify how LiftIgniter collects URLs in the browsing history of a user. If your site uses query strings or hashes to generate URLs for content, these settings will allow us to correctly match user history to inventory items.