Tracking Script & Data Collection

General Information

The Tracking Script is hosted on a CDN provided by Apsis, which means it's a third-party script. The requirements for the Tracking Script to properly perform are:

  • JavaScript.
  • LocalStorage.
  • Cookies.
  • Internet connection.

 


 

Sample

Here's a sample of a typical APSIS One Tracking Script:

<script type='text/javascript'>

(function (d) {

var apc = d.createElement('script'), fs;\n apc.type =

'text/javascript';

apc.charset = 'UTF-8';

apc.async = true;

apc.src = 'https://static.ws.apsisbeta.one/live/d/1340-

20190117115235/370484f1.js';

fs = d.getElementsByTagName('script')[0];

fs.parentNode.insertBefore(apc, fs);

})(document);

</script>

 


 

Tracked Data

The web data collected is stored in 2 places: in visitors’ browsers and in APSIS One’s cloud.

All data is stored as long as the APSIS One account admin has activated all options available in all Website tool activities in APSIS One, and that the visitor has given cookie consent. All events are stored with a timestamp.

Here’s all data collected according to activity:

 

Signup bar

  • Signup bar is viewed/shown on website.
  • A value is submitted (email address, phone number).
  • Click on return offer (CTA that appears after visitor has already sent value).

All above events include:

  • A unique activity ID for the signup bar. A website may have more than one active signup bar.
  • The web domain the signup bar is active on.
  • The URL where the signup bar is displayed on.
  • Referrer page: the webpage the visitor came from, before arriving to the page where the signup bar is displayed.

 

Cookie banner

  • The cookie banner is viewed/shown on website.
  • Cookie consent is submitted. 

All above events include:

  • A unique activity ID for the cookie banner. A website may have more than one active cookie banners, by using the advanced Match cookie/Language option.
  • The web domain the cookie banner is active on.
  • The URL where the cookie banner is displayed on.
  • Referrer page: the webpage the visitor came from, before arriving to the page where the cookie banner is displayed.

 

Auto collect

Page views

Site searches

  • The search term used by the visitor.
  • URL of page viewed/shown.

Google Analytics

  • UTM parameters present in URL of the page viewed/shown. 

Google SEO/SEM

  • Whether the visitor’s page view originated from an organic or paid source.

Facebook Ads Referral

  • The domain associated with the ad.
  • URL of page viewed/shown.
  • Type of data source, in this case it will show as "ads".

File Downloads

  • The domain where the file is hosted.
  • URL of page where the file was downloaded.
  • Link to the file and its link title.

  

Product Views

  • Name of the product viewed/shown.
  • Name of the product category that the product viewed/shown belongs to.
  • Price of the product viewed/shown.
  • Image of the product viewed/shown.
  • Any other data that corresponds with elements mapped with the Product views activity.

 


 

Cookies

All cookies are set by the JavaScript code on your domain, which means all cookies tracked with APSIS One are first-party cookies.

Here's the cookies APSIS One collects according to storage:

 

Cloud storage

  • Ely_vID: Profile ID.
  • Ely_cc_answ: Cookie consent.
  • Elytil: Whether the visitor is a first time visitor or not. Appears only once per profile.
  • Elytis: Whether it's a new browser session. Appears once per browser session.
  • Cookie-banner-session, capture-bar-session-<hash>: Cookies that help monitor the status of Signup bar and Cookie banner activities.

 

Local storage

  • Ely.deferred_events: Events that took place up to an hour before visitor provided cookie consent. If consent is not provided within an hour, events are deleted.
  • Ely.profile: A visitor's local profile.
  • Innometrics-cookie-banner-variable: Shows the correct status of the Cookie banner.
  • pcdc:  The service structure for the events being sent to Audience.

  


 

 

Was this article helpful?