Track a variety of Website interactions in APSIS One, and use the data to create a more impactful and effective marketing campaign.

Did you set up Tracking in your domain?

This type of Events will only be displayed if you have set up Tracking in your domain. It allows you to track basic browsing behavior from your website's visitors as well as data from integrations with Facebook ads, Google Analytics, Google SEO/SEM, and many more.


In this article


Google Analytics

These interactions are fed into APSIS One if you use UTM parameters to track interactions with Google Analytics. If the APSIS One Tracking Script identifies a page load with any of the supported UTM parameters, it will enrich the Profile with a Google Analytics Event. For example: http://www.example.com/?utm_source=exampleblog&utm_medium=referral&utm_campaign=summer-sale

To read more about enabling Google Analytics, head over to this article.

Here are the types of data associated with this Event:

referrer: The page where the website traffic originated, or where the Profiles were before reaching the domain associated with the Event.

url: Refers to the specific URL associated with the Event.

domain: The domain where the Event took place.

utmcampaign: Corresponds with a Google Analytics parameter. This one refers to the text used to identify a particular campaign.

utmcontent: Corresponds with a Google Analytics parameter. Useful to differentiate similar content or links within the same Email.

utmmedium: Corresponds with a Google Analytics parameter. Refers to the communication medium used to display the content, like whether it's an Email newsletter, a banner, etc.

utmsource: Corresponds with a Google Analytics parameter. Identifies the origin on the website interaction, if it was visited by clicking on a website, via a Google search, etc.

utmterm: Corresponds with a Google Analytics parameter. In the case of the campaigns being Tagged with certain keywords, this parameter allows you to specify the keyword.


Google SEO/SEM

These interactions are fed into APSIS One if you have a Google SEO/SEM integration. If the APSIS One Tracking Script identifies that a visitor has arrived to the website from a google domain. They can be from a paid source, identified with a Google Click ID (GCLID) parameter in the URL, or an organic source.

Here are the types of data associated with this Event:

referrer: The page where the website traffic originated, or where the Profiles were before reaching the domain associated with the Event.

url: Refers to the specific URL associated with the Event.

domain: The domain where the Event took place.

type: Corresponds with Google SEO/SEM. Determines whether the traffic comes from a paid (GCLID parameter in the URL) or an organic source.


Page view

They viewed or browsed a page in your website. Note that all this data is fed to APSIS One as it is mapped in your website's code. Here are types of data associated with this Event:

referrer: The page where the website traffic originated, or where the Profiles were before reaching the domain associated with the Event.

url: Refers to the specific URL associated with the Event.

domain: The domain where the Event took place.

title: The name of the product viewed by the Profile upon browsing your website.


File download

They downloaded a file from your website. This is detected when the link contains a file extension (like .PDF, .EPUB, .ZIP...) or a "download" parameter. Here are the types of data associated with this Event:

referrer: The page where the website traffic originated, or where the Profiles were before reaching the domain associated with the Event.

url: Refers to the specific URL associated with the Event.

domain: The domain where the Event took place.

link: A link to the file that was downloaded.

title: Title of the file's link.


They performed a search in your website. This Event is picked up by the URL's search key, which you entered when setting up Tracking for your domain.

Here are the types of data associated with this Event:

referrer: The page where the website traffic originated, or where the Profiles were before reaching the domain associated with the Event.

url: Refers to the specific URL associated with the Event.

domain: The domain where the Event took place.

term: The search term used by the Profile.


Facebook Ad Referral

They reached your website from a Facebook ad, with a Facebook Click ID (FBCLID) parameter that is automatically added by Facebook when linking to your website. For example: http://www.site.com?fbclid=juihd8239732buibiee32809jeee2i90. Here are the types of data associated with this Event:

referrer: The page where the website traffic originated, or where the Profiles were before reaching the domain associated with the Event.

url: Refers to the specific URL associated with the Event.

domain: The domain where the Event took place.

term: The search term used by the Profile.

type: (In development...)


LinkedIn

They reached your website from a link on LinkedIn.

activityId: The id of the activity in the website tool.

referrer: Referrer of the page.

url: URL on which the Event occurred.

location: Empty string.

domain: Domain of the site on which the Event occurred.

type: Will be "ads" by default until further notice.


External Links

They left your website by clicking a link that sent them to another page.

activityId": "string", // the id of the activity in the website Tool

activityId: The id of the activity in the website tool.

referrer: Referrer of the page.

url: URL on which the Event occurred.

location: Empty string.

domain: Domain of the site on which the Event occurred.

linkUrl: The URL the visitor clicked.

Did this answer your question?