Tracking Script and Data Collection

By installing the Tracking Script in your website, you will be collecting visitor browsing data into APSIS One Profiles. Here's some valuable information regarding the actual script, details about data collection as well as the advanced Manual Data Tracking capabilities available today in the platform.

In this article

Tracking Script Sample

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

<script type='text/javascript'>
(function (d) {
var a1 = d.createElement('script'), fs;
a1.type = 'text/javascript';
a1.charset = 'UTF-8';
a1.async = true;
a1.src = '';
fs = d.getElementsByTagName('script')[0];fs.parentNode.insertBefore
(a1, fs);

Tracked Data

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

All data is stored as long as the APSIS One Account Owner or Admin User has activated all options available in Section Settings, 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:

Sign-up bar

  • Sign-up 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 Sign-up bar. A website may have more than one active Sign-up bar.

  • The web domain the Sign-up bar is active on.

  • The URL where the Sign-up bar is displayed on.

  • Referrer page: the webpage the visitor came from, before arriving to the page where the Sign-up 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.

Section: Tracking

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 visitors 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.


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 Sign-up bar and Cookie banner activities.

Local storage

  • apsis-cookie-banner-variable: Shows the correct status of the Cookie banner.

  • pcdc: The service structure for the Events being sent to Audience.

Temporary cookies

  • apsis-cookie-test: APSIS One generates one temporary cookie per page in order to check whether the tracking script is able to store cookies on the visitor's browser. The test cookie will be deleted immediately after.

Did this answer your question?