On this page:


Overview

A visit session is the period of time a customer (the visitor) spends on your site e.g. browsing.

Ometria counts and closes a visit session after 30 minutes of inactivity.

If...then...

a visitor browses your site for five minutes and takes no further action...

Ometria counts the session once 30 minutes has passed since their last click. 

the visitor is inactive (no clicks) for 32 (e.g.) minutes, then returns and performs an action (clicking a link on your site)...

this counts as a second visit session. 

The visitor arrives at your website from one source (e.g. email, Ometria, social), then revisits the website from a different source while the first visit is still active...

Ometria still counts it as one visit from the original source (or attributes the visit to the original source) rather than two. 

See more: Order attribution


Note: Ometria does not expire sessions at midnight. If a visit starts at 23:50 and the visitor browses for 20 minutes crossing over to the next day, Ometria will still count their visit as one visit. 


Viewing visits in Ometria

Overview dashboard

Go to Overview > Ecommerce KPIs

Realtime dashboard

To see visitors currently on your site, go to Realtime:

Contact details

To see an individual contact’s visit history, go to: Customer > Segment explorer and select the Contacts tab:

Select any contact from the list to view their profile.

You can see their number of visits in the Overview tab:

For more detail, select the Activity tab and filter the activity type on Visit:

You can click each activity instance for more information including the number of pages viewed and the Source/referrer:


Segmenting on visits

You can segment contacts on visit criteria using the customer filter, available in the Segment explorer as well as:

See: Segmenting contacts by visit


Using visits as a campaign trigger

When setting up an automation campaign, you can use ‘visited the website’ as a trigger:

You can add the following conditions to this trigger:


ConditionDescription

Contact has viewed a product

Trigger the campaign based on products a contact has (or has not viewed) on your site.

Contact has viewed a product with an attribute

Trigger the campaign based on a set of attributes (e.g. collection, colour, engraved, etc.) belonging to a group of products which the contact has viewed on your site.

Contact has viewed a product or page with an attribute

Trigger the campaign based on a set of attributes belonging to a group of products or pages which the contact has viewed on your site.

Contact has visited for a time period (in seconds)

Trigger the campaign based on the amount of time (in seconds) a contact spent on your site.

Contact has visited from a source

Trigger the campaign based on the source from which the contact arrived at your site, e.g. email, social, cpc, etc.

Contact has visited a store

Trigger the campaign based on the store the contact visited, e.g. GB, US, etc.

Find out more about entry triggers for automation campaigns.

See some trigger examples for automation flows


Using visits as an exit condition

When setting up an automation campaign, you can use ‘visited the website’ as a trigger:

This means that contacts will exit your campaign flow if they meet the condition you select here:

ConditionDescription

Contact has viewed a product

The contact exits the flow once they have viewed a specified product on your site.

Contact has viewed a product with an attribute

The contact exits the flow once they have viewed a product on your site with a selected attribute(s), e.g. collection, colour, engraved, etc.

Contact has visited for a time period (in seconds)

The contact exits the flow once they have visited your site for a specified length of time.

Contact has visited from a source

The contact exits the flow once they have visited your site from a specified source, e.g. email, social, cpc etc.

Contact has visited a store

The contact exits the flow once they have visited a specified store, e.g. GB, US etc.


Find out more about Exit conditions for automation campaigns


Identifying visitors as contacts

Ometria doesn’t associate all visits to contacts, but we do collect events for all visitors.

These events are reflected in the Visits KPI in the Overview dashboard as well as Page views, which we count for all visitors including unidentified contacts (i.e. contacts for whom we have no associated email address). 


Important: We don’t attribute a visit to a contact if there is only a one-page view without any other activity (aka a ‘bounce visit’).


Generally, Ometria identifies a visitor as a contact if:

  • The visitor enters their email address during their visit, e.g. via logging in or signing up.
  • The visitor clicks on a link which contains tracking parameters with auto-identification enabled (e.g., they are redirected through email.) 

How does Ometria identify visitors from a guest checkout?

If your site requires an email address during checkout, the customer will be saved as a contact record in Ometria with an order attributed to the email address they enter. 

Be aware that if the customer has not opted-in for marketing emails, they cannot receive any marketing emails from Ometria. 

Can you backdate visits after identification?

Not entirely.

If a visitor has not been identified, none of their visit information (page views, orders, abandoned basket, etc.) can be recorded against a contact record.

However, the visitor’s browser would still contain cookies recording the number of visits to the website and the source of the original visit.

So, when Ometria does identify a visitor that previously had no email address, it will record: 

  • the source of the first visit, and;
  • the number of visits to the website 

associated with that visitor via their cookies. 

Other than this data listed above, Ometria does not retrospectively associate any visit information with the visitor after they are identified.

For example, if a visitor comes from google.com, visits five times and then identifies themselves, Ometria will store the acquiring ‘source’ as google.com, and number of visits as ‘5’, (information retracted from the cookies) but will not record the products viewed or events before the user was identified.

How does identification work across devices?

Identification of contacts and their traffic source works the same way across all devices. 

If a visitor identifies themselves on two devices, or clicks an email link with an identification parameter in, a cookie is dropped on both devices and both are associated with the same contact.

How long does Ometria store browsing data?

All browsing data is stored indefinitely in Ometria's databases. 

However, browser sessions are only made available to the platform when they are ‘identified’, i.e. Ometria has an email address to associate with the browser.

Cookies renew each time the visitor visits your site, meaning their values are retained and their lifetimes are extended each time the user visits.