This article describes the profile properties that BlueConic collects for you out-of-the-box.
Out-of-the-box profile properties BlueConic collects
Out-of-the-box, BlueConic collects a number of profile properties (attributes) for all of your known and anonymous users. Your customer dataset doesn't end there. You can still:
Configure as many other first-party behavioral data points as you need to better understand your audience and improve relevancy and outcomes across all funnel/lifecycle stages.
Bring data in from other marketing platforms or data warehouses (dwh) to completely round out your user profiles.
Single-value data values vs. multi-value data profile property values
The attributes collected and stored by BlueConic can be single-value or multi-value. For example, you might have a profile property that contains "visit dates" (all dates the visitor has been to a specific web property). You also have the out-of-box property that contains the most recent visit date. This extends to all data points; it is common to store the same type of data in different ways to get unique views into your customers and segments. Campaign tracking parameters are often stored in three ways: first, most recent, and all.
The information gathered by BlueConic comes down to configuration. You can configure BlueConic Listeners to enrich a customer profile based on behavior or provided input. You can also configure BlueConic Connections to bring data in from other systems.
Engagement profile properties
The BlueConic Engagement Listener collect information about customer engagement, based on the user's engagement patterns. Learn more about how the Engagement Listener collect customer engagement data for you.
Profile property data the Global Listener collects automatically
The BlueConic Global Listener comes out of the box and collects several types of customer data including behavioral profile properties. There are two types of profile properties collected by the Global Listener:
The first set of values are overwritten each time they are captured (i.e. a single value is stored).
The next set of values store persistent, multi-value data.
You can disable the Global Listener if desired. Contact your Customer Success Manager for more information.
Profile properties overwritten each time they are captured
App ID (Most Recent)++
App Name (Most Recent)++
App Name and Version (Most Recent)++
Behavioral: Frequency
Behavioral: Intensity
Behavioral: Momentum
Behavioral: Recency
Behavioral: Recent intensity
Browser Name (Most Recent)^^
Browser Version (Most Recent)^^
City (Most Recent)
Continent (Most Recent)
Country (Most Recent)
Device (Most Recent)
Device DPI (Most Recent)++
Device Hardware Vendor (Most Recent) ++
Device Model (Most Recent) ++
Engagement
Entry Page
First Visited Date
Identifier Changed
Keywords (Most Recent)*
Last Modified Date
Last Visited Date
Mobile Ad ID (Most Recent)++
Operating System Name (Most Recent)
Operating System Version (Most Recent)
Page Views (Most Recent Visit)
Referrer Hostname (Most Recent)
Resolution (Most Recent)
Sample ID
Screen Height (Most Recent)
Screen Width (Most Recent)
Start Session
State (Most Recent)
State Code (Most Recent)
Time Zone (Most Recent)
Total Visit Time on Channels
UTM Campaign (Most Recent)
UTM Content (Most Recent)
UTM Medium (Most Recent)
UTM Source (Most Recent)
UTM Term (Most Recent)
Profile properties that are persistent and progressively profiled
App ID (All)++
App Name (All)++
App Version (All)++
App Name and Version (All)++
App Model (All)++
App Vendor (All)++
Browser Name (All)^^
Browser Version (All)^^
Device (All)
Device DPI (All)++
Device Hardware Vendor (All)++
Device Model (All)++
Keywords (All)*
Language (All)
Mobile Ad ID (All)++
Operating System Name (All)
Operating System Version (All)
Origin of profile level 1: Type
Origin of profile level 2: Source
Origin of profile level 3: Detail
Page Views (All visits)
Profile Property Has Value
Received from Connection
Received from System
Referrer Hostname (All)
Resolution (All)
Sent to Connection
Sent to System
UTM Campaign (All)
UTM Content (All)
UTM Medium (All)
UTM Source (All)
UTM Term (All)
Variants Clicked
Variants Converted Directly
Variants Converted Indirectly
Variants Viewed
Visited Channels
Visited Domains
Visited Sites
Visits
++ SDK implementations
Certain profile properties (marked above with ++) are collected only with SDK implementations.
^^ Browser detection
BlueConic recognizes a user’s browser (i.e., browser name and version, marked above with ^^) using the User-Agent Client Hints API, in addition to the User-Agent header.
*Note about search keywords
The Global Listener stores keywords from search engine results that include referral keywords.
What is the difference between visited sites and visited channels?
The Visited sites property is collected by the BlueConic Global Listener, so it is fully client-side and requires a page view to be collected. The Visited channel profile property is captured server-side, based on the referrer of the initial request from browser to BlueConic. If the Global Listener doesn’t fully execute, the Visited Sites property will be empty, while Visited Channel may still have a value.
Profile properties that are read-only
All BlueConic tenants include the following read-only profile properties. You can view these properties on the Profile Properties page (More... > Properties) but cannot modify their settings:
Creation date
Last visited date
Domain group
Last modified date
System has property
For more information, review the article Managing read-only, system-created profile properties.
Note: There may be a slight discrepancy between the read-only, system-generated "Last visited" property and the Visit Listener-populated "Last visited" property for the same timeframe. This is because the Visit Listener property is set client-side, while the read-only property is updated server-side whenever there’s a web visit, external tracking pixel view, AMP view, or shortened URL view.