The "New Audience" Section
The New Audience section became live on September 2017. This section allows you to create advanced audience configurations.
When creating a new Audience you have the option to select it as a "Segmentation". This allows you to make the audience persistent, and to use it at a later time.
You can find more information about Segmentation in the following article.
Convert allows you to include or exclude visitors in your experience based on the UTM tags listed in the URL with which they entered your site. The tags that we support are:
You can use visitor specific data to include in your experience. You can choose from:
Average Time on Page
This time is calculated when a page-view occurs and it is obtained by subtracting the time when the session began from the current time divided by the number of pages visited.
A session is being kept active for 20 minutes after no further browsing...therefore, if the user does something else and comes back to your site, generating another page view within 20 minutes from the last page view, that duration would be counted.
If they come back after 20 minutes, a new session would be opened, and then the duration time will count from then on.
Please note, that the duration there is counted in seconds, therefore if you need to count 20 minutes you'd need to enter 120.
You can choose the city or country to include or exclude visitors on your experience.
We get this data handed over from the Akamai Content Delivery Network (CDN), and/or MaxMind geo-ip location databases. You can do very accurate geographical targeting. It is also a world database, so you will find cities and regions anywhere in the world.
Using Metro Codes (available for US-only)
Although you can't target directly by zip code, you can target by Metro Codes for the US. MaxMind has free downloadable IP geolocation databases called GeoLite2. According to MaxMind, they are comparable to, but less accurate than MaxMind’s GeoIP2 databases (which are not free).
To find metro codes, you can download their GeoLite2 City database and look up the cities that belong to a particular metro code here: https://dev.maxmind.com/geoip/geoip2/geolite2/
In order to use metro codes for your audience targeting, you would download the city database file as mentioned above, open it on your computer and search for the metro code you are interested in. You should proceed to find all of the city names with that same metro code. Once you have all this information, create a new Audience and look for the category called Visitor Data. Under Visitor Data you will see that you can select City, and you can drag it over to the right to build your Audience conditions. You can do this multiple times, once for each city you found that matches the metro code, separating them with an OR condition.
Note also in the case where a city name may exist in different States, you can add an AND condition for Region with the State name so that you will only target cities in that particular State.
Days since last visit
You can include or exclude visitors based on the days since the last visit to your site.
Here you can include or exclude visitors to your experience, based on the number of pages they have visited before.
Besides, countries and cities you can also use regions to include or exclude its visitors from your experience. Regions are the equivalent to states in the USA.
You can use Maxmind region database as a reference for the world regions you can include.
You can search for Maxmind databases online. There are free and more complete paid versions you can download.
The duration is calculated when a page-view happens and is obtained by subtracting the time when the session began from the current time.
A session is being kept active for 20 minutes after no further browsing. If the visitor does something else and comes back to your site, generating another page view within 20 minutes from the last page view, that duration would be counted. If they come back after 20 minutes, a new session would be generated.
You can include or exclude users by comparing a provided value with the value of the cookie. For this, you would have to provide the cookie name and the value that you are comparing to.
For Convert to be able to read cookie value, the cookie would have to have been written under the same site domain.
You can include or exclude "New Visitors" or "Returning Visitors" to your site. These new visitors have to be fresh visitors, and a "Returning Visitor" would be considered one if they have visited the site since the Convert tracking code was installed. And even before the experience was created.
You can include or exclude a visitor depending on the number of visits or sessions a visitor has on the site. It is easier to start creating this with a "Preset" and then use the "Advanced Audience" to tweak it further to your needs.
A session is being kept active for 20 minutes after no further browsing. If the visitor does something else and comes back to your site, generating another page view within 20 minutes from the last page view, that would be counted as one visit. If they come back after 20 minutes, a new visit would be counted.
You can include or exclude visitors that are part of another experiment which is currently running, or visitors which are not included in any other experiment currently. This allows you to run simultaneous tests on the same page, without fearing that they could interfere with one another. This is what is known as "Collision Avoidance" or "Collision Prevention".
You can include or exclude a visitor if its visit falls within a certain time period. For setting this up, is better to start on the "Presets tab" and then, go the "Advanced Settings tab" to further tweak to your own needs.
Default UTC Time Zone
The default visit time reference is based on the UTC time zone.
Project Time Zone
You can also use as reference the time zone specified in your project settings. All of this settings include "Project tz" at the beginning.
You can target your visitors based on the system they are browsing your website from:
You can use the browser type to include or exclude visitors on your experience, such as "Chrome", "Mozilla", or "IE". This audience is based on the User Agent of the visitor's browser.
You can use the release version of the visitor's browser to include them on an experience. Let's say 11.00, 1.01, etc. This audience is based on the User Agent of the visitor's browser.
You can use the operating system of the visitor device to include them or exclude them on experience. For example Android, Window Os, Mac OS. This audience is based on the User Agent of the visitor's browser.
You can also use the User Agent of the visitor browser to include or exclude visitors on your experience.
Device is desktop or mobile
You can include or exclude visitors based on the type of device he/she is using to visit the site. The device is determined using the User Agent provided by the visitor browser. This is determined by the Akamai CDN network which hands the device type to the Convert tracking script.
You can use "Page Tag" values to include or exclude visitors, that you had mapped with the Convert tracking code. Please find more info on the following article: "Targeting with Advanced Page Tagging".
The condition should return true to run. Anything else it returns, it will cause the experience to not run.
An example would be:
customer_group == "frequent"
You can find more information in the following article: "Targeting Experiments and Firing Goals Based on a JS Condition".
Customer ID and Custom Tags
The Customer ID is a page tag that can be mapped with an advanced tracking code, and you can use it to include or exclude visitors in your experience. Please find more info on the following article: "Targeting with Advanced Page Tagging".
Logical Joins for your Audiences
By default, separate audiences are joined with OR operator. But all the conditions inside the same audience can logically be joined with AND / OR operators. These operators allow you to create sophisticated audiences.
To use this, just drag and drop your condition from the left panel, into the right one by placing them in the correct area corresponding to this operators.
These instructions pertain to the new Audiences Interface. This applies to all experiences created after the new Legacy Audiences launch before September 16th, 2017.
You can find documentation related to the legacy audiences interface here.