BlueConic FAQs
BlueConic's Frequently Asked Questions page is a central hub where its customers can always go to with their most common questions. These are the 535 most popular questions BlueConic receives.
Frequently Asked Questions About BlueConic
Data collection using listeners is foundational to using the BlueConic customer data platform. The more you listentoyour individual customers and visitors, the more you know to help drive a better outcome. Listeners in BlueConic add information to individual profiles based on each individual's online behavior or provided input. There are several powerful listener types availableout of the box, for example:
Behavior Listening
Form Listening
Funnel Listening
Interest Ranking
Scoring
You can even develop custom listeners as BlueConic plugins.
About the BlueConic Global Listener
BlueConic uses a built-in Global Listener to collect some important profile properties. See What kind of data does BlueConic collect? for a list of profile property values BlueConic collects out-of-the-box (so you don't have to...).
Listeners and privacy management
Listeners can be added to Objectives, allowing for privacy management of the information that is being listened for. A listener is only executed for customers or visitors who consented to at least one of the objectives linked to the listener.
Organizing and managing listeners
To see the listeners configured in your BlueConic environment, choose Listeners from the BlueConic navigation bar. You can use different view options to configure this display. See " Object Navigation " for an overview of all available navigation options.
consent Objectives
Creating a new listener
To add a new listener in BlueConic, choose Listeners from the BlueConic navigation bar and select "Add listener" at the top right of the Listeners tab.
A gallery opens, where you can select thelistener type you want:
Find the type of listener you want to add and select it.After choosing the listener type, you can configure your listener.To maintain your Listeners, use Save, Save As, and Delete as with any other BlueConic object.
The list only shows the types of listenerscurrently installedin BlueConic. Select theShow allcheckbox to see alltypes of listeners available in the Plugins Gallery.
The "Show all" checkbox is unchecked by default and is specific for each marketer and each type of object. As a result, changing the object for the Listeners lightbox doesn't impact the display in the Dialogues lightbox for example.
The "Show all" option for Listeners is remembered over sessions; therefore, if you log out and log back in, the state of the checkbox remains the same.
If you check the checkbox:
A "Loading..." screen is placed over the plugins area for 1.5 seconds.
All plugins from the Plugins Gallery that are not installed yet are added to the list.
Only plugins of the same type as the current object type are added (for example: only uninstalled Listener plugins are added to the list if the marketer is adding a Listener on the Listener tab).
If you choose an uninstalled plugin, then selecting a new listenerwill automatically install it in BlueConic. Ifthe checkbox is unchecked (the default state) then only the installed plugins are shown in the lightbox.
Name and Description
You can change the name of the listener by clicking on the name and editing it. Optionally, you can also add a description.
"Where": Channel selection
At the "where" section, you select the channels on which you want this listener to be active. By default listeners are running on "all channels." You can select a specific channel by entering a few characters of that channel in the search box. Channels that match your criteria will appear in a list to select from. If needed you can also open the advanced search to find the right channel.
If you want to specify a specific URL on which the listener is active, you first need to select the channel to which this URL belongs. Then you can add the specific URL by clicking the "Add Rule" button.
The number of specific URL-restrictions in a channel is mentioned after the channel, and can be viewed and edited by clicking on it.
Configuring listening rules
The rest of the setup of the listener depends on the type of listener you choose. Explore the Listeners documentation for instructions on how to configure a specific listener.
Change the status of a listener
The status of a listener is displayed next to its name. By default the listener is off and will not be triggered for visitors. Only enabled listenersare triggered for visitors.Enable or disablealistener by clicking the switch button.
Consent management Objectives and related items
In the right-hand sidebar, the and "Related items" widgets are displayed. They show the other objects in BlueConic that are directly related to the listener you are managing.
Listeners can have the following types of related items:
Channels: The channels on which this listener is active.
Profile properties: The profile properties that are set by this listener.
Plugins: The plugin on which this listener is based.
View ArticleInterest Ranking allows you to add interests (keywords) to a profile property in a visitor's profile based on a points-based system. Points for an interest are scored based on the visitor's behavior, which includes viewing content, clicking something, coming to your website from a specific referring URL, and landing on a URL that contains a specified string. Once an interest has been added to a visitor's profile, you can create segments to target customers and visitors based on these interests.
Interest Ranking uses a points-based system to determine whether to add an interest to profile properties. You can define a points threshold that determines the minimum score an interest must reach before being added to the profile property. This means you can determine how interested a visitor must be before interests are added to their profile. Additionally, you can limit the number of interests that are added. You can choose whether all interests that reach a certain number of points are added or only the top N interests, where N is an integer.
Typically, how you decide to score something depends on many factors. Someone arriving from a specific referring URL might receive a relatively high score for a certain interest because the link they arrived on indicates that they are more than casually interested in what you have to offer. Likewise, in certain situations, clicking in a specific area of a web page might receive a high score because an ad appears there.
In BlueConic, you use the Interest Ranking Listener to gather customer interests and keywords. Details on configuring an Interest Ranking Listener to gather interests and keywords are provided below. For general information on listeners, see What are Listeners in BlueConic?
Configuring Interest Ranking
With Interest Ranking, you can build highly sophisticated filters. This section takes you step by step through the process.
Follow the steps below to configure an Interest Ranking listener.
Profile properties
Start by setting up the rules on what to store in which profile properties. Create a new rule by clicking the [Add rule] button:
copying and deleting rulesin BlueConic
Define the number of interests to store, typically a number of 5 or less.
Define the number of days over which interest scores will decay to about 10\% of their initial point value. For example, if you enter "30" here, and the interest "coffee" scores 10 points today, the "coffee" interest will gradually decay in value over time and only be worth around 1 point in 30 days or more. As a result, recently scored interests will rank higher than older interests.
To use an existing profile property, select the profile property to which interests will be added if the score threshold is reached. Or you can create a new profile property by clicking select profile property, typing a new name, and clicking OK.
Interest ranking will keep track of the top number of interests in the profile property that you define as a list.
Interest ranking will also keep track of each of the top interests separately in an automatically created profile property with the appendix_top.
For example, let's say you selected a profile property "Product Interest (30 days)" with the ID product_interest_30to keep track of the top 3 products in it. Interest ranking will now not only fill the original profile property, but will also keep track of profile propertyproduct_interest_30_top.
If you want to use this profile property in BlueConic, create a new profile property with the same ID, as shown here:
Interest ranking will now automatically keep track of the top interest in this profile property, and you can build segments based on it.
Interests
Here you add one or more interests that will be scored. Any interest that is added to the profile property can be used to define a segment that you can target.
To add an interest, enter a string in the text field next to Interests and click [Add].
Repeat this step for each interest you want to add. The interests that you add appear in a row next to Interests.
To remove an interest, click it and then click "Remove."
Expert settings
Set the threshold by clicking the number and entering the desired value. An interest will not considered to be added to the profile property unless it has reached the threshold number of points.
By setting a threshold you make sure interests are not picked up by accident. Only the highest scoring interests that have more than the threshold number of points will be stored in the profile property.
Scoring
Here you define how interests are scored based on visitor behavior and/or events that transpire during the visitor's browsing. Each behavior or event is assigned its own relative score. How you score behaviors or events depends completely on what you consider important in determining a visitor's interest to be high, medium, or low. To define a new rule, click [Add Rule]:
Select one of the following from the drop-down list:
Content
Click / Tap
Form submit
URL / Mobile Screen
Social Web Event
Advanced Event
Content
This option allows you to add points to interests if they appear in a specific content element or in a defined area of the page. In this scenario, an interest is treated as a keyword. Each found interest that appears on the page in a defined area will have the specified number of points added to it. It is also possible to create and score a new interest based on a jQuery Selector.
Select "Content" from the drop-down list and click [Add Rule].
Define the number of points to add to each found interest if it appears in the specified position on the web page. In this case, the interest is a keyword. If the keyword (interest) appears in the specified position, points will be added to it according to the defined criteria.
Select "each found interest" if you want to specify the interest or interest to which points will be added.
For information on adding or scoring an interest based on a jQuery Selector, see Interest based on Selector.
Click " any header " to see a list of content elements. Select the position on the web page in which the interest must be present in order for points to be added to it (in the HTML title, in a heading type, etc.). To define a custom area of the web page, select "Custom defined area". Enter a name for the custom defined area in the "Name" text box. In the "Selector" field, enter a valid jQuery selector to identify the custom area and then click [OK]. For complete information on jQuery selectors, see http://api.jquery.com/category/selectors/.
To define an area using the Visual Picker, click Visual Picker.
If the string for the interest must be an exact match, click "contains" to toggle it to "exactly matches."
For information on the advanced settings, click this link: Advanced Settings.
Click [Save].
When you have finished, the rules will be shown in the definition. For example:
Click / Tap
This option allows you to add points to each found interest if it appears in a specific content element or in a defined area of the page and if the visitor clicks on a defined area of the page. In this scenario, an interest is treated as a keyword. Each found interest that appears on the page in a defined area will have the specified number of points added to it if the user also clicks in the specified position. It is also possible to create and score a new interest based on a jQuery Selector.
Select "Click" from the drop-down list and click [Add Rule].
Specify how many points to add to each found interest if it appears at a specific position on the web page and a defined area of the page is clicked. If that area of the web page is clicked, points will be added to each found interest according to the defined criteria.
Click "each found interest" if you want to specify the interest or interest to which points will be added.
For information on adding or scoring an interest based on a jQuery Selector, see Interest based on Selector.
Click " any header " to see a list of content elements.
Select the position on the web page in which the interest must be present in order for points to be added to it (in the HTML title, in a heading type, etc.). To define a custom area of the web page, select "Custom defined area". Enter a name for the custom defined area in the "Name" text box. In the "Selector" field, enter a valid jQuery selector to identify the custom area and then click [OK]. For complete information on jQuery selectors, see http://api.jquery.com/category/selectors/.
If the string for the interest must be an exact match, click "contains" to toggle it to "exactly matches."
To define the area using the Visual Picker, click Visual Picker.
Click the "define click area" link.
Enter a name for the custom defined area in the "Name" text box. In the "Selector" field, enter a valid jQuery selector to identify the custom area and then click [OK]. For complete information on jQuery selectors, see http://api.jquery.com/category/selectors/.
To define an area using the Visual Picker, click Visual Picker.
For information on the advanced settings, click this link: Advanced Settings.
Click [Save].
When you have finished, the rules will be shown in the definition. For example:
Form submit
This option allows you to add points to a profile property when the visitor submits a form pointed to by a jQuery selector. For complete information on jQuery selectors, see http://api.jquery.com/category/selectors/.
URL / Mobile Screen
This option allows you to add points to each found interest if it appears in the URL of the current web page, in the referring URL or either one. In this scenario, an interest is treated as a keyword. Each found interest that appears in the URL of the current web page or in the referring URL will have the specified number of points added to it. It is also possible to create and score a new interest based on a jQuery Selector.
Select "URL" from the drop-down list and click [Add Rule].
Specify how many points to add to each found interest if the URL of the current web page or the referring URL contains an interest. In this case, the interest is a keyword. If the keyword (interest) appears in the URL or referring URL, points will be added to it according to the defined criteria.
Click "each found interest" if you want to specify the interest or interest to which points will be added.
For information on adding or scoring an interest based on a jQuery Selector, see Interest based on Selector.
Click the "URL or referring URL" link.
Select whether the points are scored if the interest appears in the URL of the current web page, in the referring URL or in either one and then click [OK].
If the string for the interest must be an exact match, click "contains" to toggle it to "exactly matches."
For information on the advanced settings, click this link: Advanced Settings.
Click [Save].
When you have finished, the rules are shown in the definition. For example:
Social Web Event
This option allows you to add points to interests based on the detection of an event in the specified social media. It is also possible to create and score a new interest based on a jQuery Selector.
Select "Social Event" from the drop-down list and click [Add Rule].
Specify how many points to add to one or more interests if the social media event is detected.
Click "each found interest" if you want to specify the interest or interest to which points will be added.
For information on adding or scoring an interest based on a jQuery Selector, see Interest based on Selector.
Click "select event" to select the type of social event from the drop-down list that leads to the scoring. The options are:
Event
Description
Facebook Like
The visitor has clicked a Facebook "Like" button.
Facebook Unlike
The visitor has clicked a Facebook "Unlike" button.
LinkedIn Share
The visitor has clicked a LinkedIn "Share" button.
Twitter Follow
The visitor has begun following someone on Twitter.
Twitter Tweet
The visitor has sent a Tweet from their Twitter account.
Click [Save].
When you have finished, the rules will be shown in the definition.
Advanced Event
This option allows you to add points to interests based on an advanced event in a social medium or in a custom-defined event. The event must be detected and it must contain a value in a specific context in order for points to be added to one or more interests. It is also possible to create and score a new interest based on a jQuery Selector.
Select "Advanced Event" from the drop-down list and click [Add Rule].
Specify how many points to add to one or more interests if the social media event is detected.
Click "each found interest" if you want to specify the interest or interest to which points will be added.
For information on adding or scoring an interest based on a jQuery Selector, see Interest based on Selector.
Click "select event" to select the type of event from the drop-down list that leads to the scoring. The options are:
Event
Description
Facebook Like
The visitor has clicked a Facebook "Like" button, either on Facebook itself or on a website that has a Facebook "Like" button.
Facebook Unlike
The visitor has clicked a Facebook "Unlike" button, either on Facebook itself or on a website that has a Facebook "Unlike" button.
LinkedIn Share
The visitor has clicked a LinkedIn "Share" button.
Twitter Follow
The visitor has begun following someone on Twitter.
Twitter Tweet
The visitor has sent a Tweet from their Twitter account.
To specify a custom-defined event, select "Custom defined event" and enter the name of the event in the "Name" field.
If the value received in the advanced event must be an exact match, click "contains" to toggle it to "exactly matches."
Click "any value."
Expand the drop-down list and select the value from the array that must contain the interest. The options are "any value," "first value," "second value," and "third value.". Consult your application manager if you do not know which value to select.
Click [Save].
When you have finished, the rules will be shown in the definition.
Interest based on Selector
This option adds points to one or more interests based on text found at the specified JQuery Selector. When a partial or full match with an interest is found, points are added to the specified interest(s). For example, the following HTML contains several products:
<div class="products">
<div class="product">
<div class="product-name">Bose Wave Radio</div><a rel="noopener,nofollow" target="_blank" href="https://support.blueconic.com/hc/en-us/articles/202608201-Interest-Ranking-Add-keywords-to-BlueConic-profiles#">More Info</a>
</div>
<div class="product">
<div class="product-name">Apple iPhone 5S</div><a rel="noopener,nofollow" target="_blank" href="https://support.blueconic.com/hc/en-us/articles/202608201-Interest-Ranking-Add-keywords-to-BlueConic-profiles#">More Info</a>
</div>
<div class="product">
<div class="product-name">Dell Inspiron laptop</div><a rel="noopener,nofollow" target="_blank" href="https://support.blueconic.com/hc/en-us/articles/202608201-Interest-Ranking-Add-keywords-to-BlueConic-profiles#">More Info</a>
</div>
<div class="product">
<div class="product-name">Google Glass</div><a rel="noopener,nofollow" target="_blank" href="https://support.blueconic.com/hc/en-us/articles/202608201-Interest-Ranking-Add-keywords-to-BlueConic-profiles#">More Info</a>
</div>
</div>
When this JQuery Selector is defined, all text will be examined within the HTML. If any of the interests are found, then points will be added to those that match. To define an interest based on a JQuery Selector, follow these steps:
Select "Interest Based on Selector".
Enter a name for the jQuery Selector in the "Name" field. This is the string that will appear in the rule.
Enter the jQuery Selector in the "Selector" field.
To define the area using the Visual Picker, click Visual Picker.
Click [OK]. For example:
Locationselection
By default the predefined web selector"any header" is selected.
Other options are:
Predefined Web Selector
Select one of the following:
The HTML title - Matches the rule against the contents of the <title> tag.
Any header - Matches the rule against the contents of any header tag (<h1>, <h2>, etc.).
Any Heading X - Matches the rule against the contents of the specific header (e.g. <h1>).
Any paragraph - Matches the rule against the contents of any paragraph (<p>).
Mobile screen
Matches the rule against the contents of the mobile screen.
Custom defined area
Select to define your own custom area to match the rule against. You can either use the Visual Picker or enter a valid JQuery selector that identifies the custom area in the "Selector" field. For complete information on jQuery selectors, see http://api.jquery.com/category/selectors/.
Value from JavaScript
Select this to match the rule against the value of a JavaScript variable that is available on the global scope (in other words: window.variable should exist).
To select a suitable variable, either type its name or use the VisualPicker to pick it from a webpage. Enter the URL of the webpage and the Visual Picker will display the variables and their values to the left of the page. Highlightthe variable you want and click Applyto select the variable.
Advanced settings
The following is an explanation of the Interest Ranking advanced settings.
Setting
Description
Threshold
The threshold determines the minimum number of points that an interest must have before it can be a candidate for being added to the profile property. Reaching the minimum point threshold does not actually mean that an interest will always be added to the profile property if the setting "Interests to Store" contains a value. Assuming that the setting "Interests to Store" (explained below) contains no value, all of the interests that reach the minimum point threshold will always be added to the profile property.
Interests to Store
This setting limits the number of interests that are added to the profile property. Only the top X interests that have reached the threshold are added, where X is an integer. If you specify 10, then only the top 10 highest ranking interests (according to their total number of points) that have reached the threshold will be added to the profile property. All other interests that have reached the minimum point threshold but that do not fall within the top X number of interests will not be added to the profile property.
Decay Period
This setting defines a period during which the number of points is "decayed", that is, BlueConic will decrease the number of points for all interests based on the specified time period. The decay period is in number of days. If you define a Decay Period of 30, then the visitor's point total will be reduced over 30 days to about 10\% of its starting value. This means the initial score isn't lost, but it is made less important over time.As a result recently scored interests will rank higher than older interests.
Copying and deleting rules
Learn about .
View ArticleWhat is Tracking Prevention?
Browser vendors, in particular the Apple Safari browser, are increasingly adding features to prevent third parties from tracking visitors when they visit a website. Although this tracking prevention is primarily focused on AdTech vendors, it potentially impacts any technology that collects data about customers or prospects on your website.
The major browsers have various names for tracking protection:
Apple Safari: Intelligent Tracking Prevention (ITP)
Mozilla Firefox: Content Blocking
Microsoft IE/Edge: Tracking Protection / Prevention
Google Chrome: TBD
This FAQ focuses mostly on ITP.
What is ITP (Intelligent Tracking Prevention)?
Apple announced a new version of Intelligent Tracking Prevention (ITP) in February 2019. In previous versions, third-party cookies were already disabled by default. ITP 2.1 impacts client-side cookies as well, by deleting them after 7 days. With the most recent ITP update, ITP 2.2, client-side first-party cookies that come from known trackers with querystring (for example, the utm_ parameters used by Google or Facebook) now have an expiration cap of 24 hours.
To understand the impact of this, let's unpack this by exploring the various cookie types relevant here:
First-party server-side cookies are set and read server-side through the HTTP connection of the site a visitor is visiting.
Third-party server-side cookies are also set and read server-side through an HTTP connection, but they are set because the original page references a third party (for example, to read an image or JavaScript from a third-party site) which triggers that HTTP request.
Browser or client-side cookiesare set through JavaScript in the browser and belong to the domain of the visited page.
Apple already blocked third-party, server-side cookies by default. This means that visitors cannot be tracked across different domains on the Internet. Now Apple has made an additional change so that client-side cookies only work for 7 days; this means that if a visitor doesn't come back within 7 days, those cookies are removed.
What is link decoration?
Apple is introducing link decoration limits in ITP 2.2. Link decoration is the practice of adding parameters such as UTM codes to a URL. Apple limits this by checking if a user comes from a known tracker website (such as Facebook, Google, or ad networks) to another website and there are additional parameters (like UTM codes); in this case, the first-party cookie is capped even lower, to 1 day. This isn’t an issue for BlueConic users, since it is primarily targeted at visitors clicking on an ad, for example an ad on Facebook to your own website. BlueConic runs only on your own website.
How has BlueConic updated its platform to handle this?
Apple suggested moving toward using another browser technology: localStorage. This technology is an alternative to cookies, but only works for the visited website, not for other domains of that same website or even third-party domains. We changed the BlueConic storage mechanism to store the profile UUID in localStorage, to synchronize the UUID to client-side cookies, and, depending on what browser the visitor uses, to synchronize to first- or third-party cookies as well.
Does using localStorage as primary storage impact my data?
That depends on the browser the visitor uses:
Chrome users will be tracked across subdomains and domains, as before.
Firefox users will be tracked across subdomains (so if a visitor visitswww.blueconic.comand support.blueconic.com,the visitor will have 1 profile).
Safari users will be tracked on the current visited site and across first-party subdomains, but only if they visit both sites within 7 days. (So if a visitor goes towww.blueconic.comand then after a week passes, they visitsupport.blueconic.com, that visitor will have 2 profiles instead of 1.)
This table describes if users can be tracked across domains and subdomains:
Hostname
Across Domains
Across Subdomains
Example hostname
www.company.com
www.company.com
www.company2.com
support.company.com
www.company.com
Chrome
Yes
Yes
Yes
Safari
Yes
No
Only when both are visited within 7 days
Firefox
Yes
No
Yes
With these changes, which types of traffic are impacted?
The majority of your visitors are tracked as usual. If you have the following types of traffic on your websites, you might see some impact:
If you have a lot of visitors using Safari, either from laptops or from iPhones and iPads, combined with infrequent visits that are longer than 7 days apart on average and have multiple subdomains.
If you have a lot of Firefox or Safari visitors and multiple domains.
How does this change what I see in BlueConic?
Some visitors might be represented in BlueConic by multiple profiles instead of just one. Depending on your setup and usage of BlueConic, this could lead to inflated ‘unique visitor’ counts for views, clicks, or conversions because ‘unique’ statistics are not based on the total number of views, clicks, or conversions, but are based on the number of unique profiles.
Other parts of BlueConic are not impacted. Most BlueConic Connections do not work with anonymous profiles but with identifiable profiles (meaning there is at least one additional ID such as an email address or subscriber number, in addition to the BlueConic-generated ID). Insights and dialogues will continue working as before.
Do I need to be worried about where this is going?
The industry is moving more and more toward privacy protection technologies, especially related to third-party tracking. BlueConic and other CDPs are first-party data processors. We do not own the data, you do. We are a subcontractor for you, our customers. Most privacy protection technology is focused on preventing third-party tracking, which feels logical as consumers do not expect to be tracked by third parties when visiting a website. CDPs, in general, are about giving all touchpoints with customers better data, and consequently providing better service, a great user experience, and offering customers what they want. Some CDPs, like BlueConic, also have consent management services built directly into the platform.
Technology will continue to evolve and change, but having a level playing field for everyone provides opportunities to earn trust, gain consent by providing clear value, and achieve better results.
BlueConic focuses on providing the tools you need to provide that value, by researching new privacy technology, implementing our own technology to accommodate privacy and consent, and providing you with expert guidance, so you can take advantage of these new technologies.
Why does first-party data matter now more than ever?
With industry changes such as ITP, the first-party data in a CDP like BlueConic becomes even more important. There are tactics you can employ to continue to collect data in a world of tracking protection:
Because CDP is used in a first-party context directly on your touchpoints like websites, you should focus on getting identifiers and consent from your visitors, something that would be hard or impossible for AdTech, except parties that have first-party interactions (like Google and Facebook). Having identifiers and having consent makes it easier to merge profiles back into one single profile using profile merge rules in BlueConic. For example, instead of having a paywall, you might have an intermediate step that asks for an email address and verifies the email address. Or, you might set up logins for visitors to reach restricted pages.
Request your own hostname for BlueConic. By default, customers use a blueconic.net hostname for hosting BlueConic, but we offer a premium service where you can use your own hostname. Using your own hostname integrates BlueConic more into your own websites, and makes BlueConic a first-party subdomain instead of a completely different domain. Read Deciding on the BlueConic Hostname for more information and contact [email protected] or your BlueConic CSM if you want to know more.
Where can I read more about browser tracking protection?
Apple and ITP
Firefox Enhanced Tracking
Chrome: Improving Privacy and Security on the Web
Microsoft: Tracking Prevention with Microsoft Edge
View ArticleThe BlueConic REST API is an interface that provides access to BlueConic visitor profile, segment, and interaction information. Through the API you can retrieve visitor profile information as well as add properties to visitor profiles. BlueConic segments and interaction JavaScript can also be retrieved and events can be posted to a BlueConic session.
OAuth signed requests
Methods in the BlueConic REST API that require authentication must use OAuth signed requests to do so. OAuth is an open standard for authorization of requests. OAuth allows private resources to be shared between two entities without requiring username/password credentials to be supplied. BlueConic implements "two-legged OAuth" in which a client communicates directly with BlueConic and the authentication is accomplished in one step.
BlueConic only supports OAuth version 1.0a withHMAC-SHA1 as signature algorithm.
Do not use an OAuth 2.0 library to send signed requests as these are incompatible with BlueConic.
In OAuth, the entity that grants the authorization is known as the provider and the entity requesting the authorization is known as the consumer. Each consumer is assigned a publicly known key known as the Consumer Key. The Consumer Secret, which is private for each individual consumer, paired with their Consumer Key is used to grant the authorization for access to resources. The provider knows what the Consumer Key and Consumer Secret is for each consumer. When a request for authorization is received by the provider, it checks the consumer key and consumer secret in order to verify that resources may be accessed.
Request flow
HTTP requests that require signing typically have the following flow:
An application generates an HTTP request for BlueConic.
The OAuth library signs the request and sends it to BlueConic.
BlueConic's API Access Connectionreceives the request. Using an OAuth library it validates the request and generates anHTTPS response.
The HTTPS response is sent to the consumer.
PUT https://yourserver.blueconic.net/rest/profiles/
Consumer Secret and Consumer Key configuration
In BlueConic the Consumer Key and Consumer Secret are set up by creating a BlueConic API Access Connection. The application manager that createsthis connection needs to send the developer of the external software application this information, so the developercan implement OAuth.
Signing requests
Libraries for signing requests can be downloaded here. A BlueConic java example based on Maven and Eclipse can be downloaded here.
Profile methods
The following methods allow you to create, modify, retrieve properties from and delete BlueConic visitor profiles as well as retrieve BlueConic segment information.
Create new profile
Synopsis
POST https://yourserver.blueconic.net/rest/profiles
Description
Creates a new BlueConic profile.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Form
domainGroupId
No
String
"DEFAULT"
Specifies the domain group to use when creating the new profile
Authentication
Yes
Responses
200 - Returns the created profile.
401 - Authentication failed (unauthorized).
503 - The server is too busy to handle the request.
Example
Request
POST https://yourserver.blueconic.net/rest/profiles?alt=xml
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<profile>
<id>9efb8a28-bfdf-4a10-b4f4-c0fb3a9a8dcc</id>
<properties />
<segments>
<segment>
<id>e83a67ea-1cf6-4af5-aa6d-09666d7d7781</id>
</segment>
</segments>
</profile>
Get one profile
Synopsis
GET https://yourserver.blueconic.net/rest/profiles/[profile]
Description
Retrieves the properties of the specified profile, including the IDs of the matching dynamic segments.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Path
profile
Yes
String
null
any UUID
The ID of the profile
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Querystring
expand
No
String
null
One of:
"profile.permissions.exceptions"
"profile.timeline"
Expand the information in the result set. Use "profile.permissions.exceptions" to include permission level and exception data. Use "profile.timeline" to include timeline event information. Use multiple "expand" querystring parameters to return combinations.
Querystring
Properties
No
String
null
Comma separated list of profile property IDs.
Only returns the given profile properties in the response.
Querystring
eventTypeId
No
String
null
ID of the timeline event type.
Filter returned timeline events for a specific type. Only one timeline event type ID is allowed.
Querystring
eventCount
No
String
20
any number
The maximum number of timeline events to return.
Querystring
fromDate
No
String
null
any date
Filter to only include timeline events that are dated later than this date. The format of fromDate is "2018-01-01T00:00Z" or with a timezone offset "2018-01-01T00:00+05:00"
Querystring
toDate
No
String
null
any date
Filter to only include timeline events that are dated before this date. The format of toDate is "2018-01-01T00:00Z" or with a timezone offset "2018-01-01T00:00+05:00"
Querystring
prettyPrint
No
String
null
"true"
Set to "true" to return the JSON result in a readable pretty print format.
Authentication
Yes
Responses
200 - Returns the specified profile.
401 - Authentication failed (unauthorized).
404 - The specified profile doesn't exist.
503 - The server is too busy to handle the request.
Example
Request
GET https://yourserver.blueconic.net/rest/profiles/45e2a650-ca17-4e03-8e8d-12d00ed4d9b3?alt=xml&expand=profile.timeline
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<profile>
<id>45e2a650-ca17-4e03-8e8d-12d00ed4d9b3</id>
<privacyLegislation>GDPR</privacyLegislation>
<consentedObjectives>
<objective>
<id>objective_id_1</id>
</objective>
<objective>
<id>objective_id_2</id>
</objective>
</consentedObjectives>
<refusedObjectives>
<objective>
<id>objective_id_3</id>
</objective>
</refusedObjectives>
<properties>
<property>
<id>email</id>
<values>
<value>[email protected]</value>
</values>
</property>
<property>
<id>hobby</id>
<values>
<value>soccer</value>
<value>tennis</value>
</values>
</property>
</properties>
<segments>
<segment>
<id>dd69b76f-8e0d-43bf-bf93-56d05bdcef4e</id>
</segment>
<segment>
<id>50622c8f-de0d-4a25-af0d-e52a26b68f40</id>
</segment>
</segments>
<events>
<event>
<data>
<property>
<id>product</id>
<values>
<value xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="propertyWrapper">
<value xmlns:ns3="timeline" xsi:type="ns3:timeline">
<id>listprice</id>
<values>
<value xmlns:xs="http://www.w3.org/2001/XMLSchema" xsi:type="xs:float">12.3</value>
<values>
</value>
<value xmlns:ns3="timeline" xsi:type="ns3:timeline">
<id>netprice</id>
<values>
<value xmlns:xs="http://www.w3.org/2001/XMLSchema" xsi:type="xs:float">11.7</value>
<values>
</value>
<value xmlns:ns3="timeline" xsi:type="ns3:timeline">
<id>id</id>
<values>
<value xmlns:xs="http://www.w3.org/2001/XMLSchema" xsi:type="xs:string">97b328e8ed2220ceb1b3c52d780aa334</value>
<values>
</value>
</value>
</values>
</property>
</data>
<date>2019-11-29T19:00:51Z</date>
<eventTypeId>order</eventTypeId>
<id>ba1d699eacd13e0e0b71a1a2c0eeb2d1</id>
<source>connection_33e4f51a-44e4-420b-a557-f4ba3b6d1176</source>
</event>
</events>
</profile>
Update a profile
Synopsis
PUT https://yourserver.blueconic.net/rest/profiles/[profile]
Description
Updates an existing BlueConic profile with the replaceBy parameter.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Path
profile
Yes
String
null
any UUID
The ID of the profile
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Form
replaceBy
No
String
null
any UUID
The ID of the profile that replaces this profile. All future requests for the profile ID containing the replaceBy property will be routed to the "replace by" profile ID.
Authentication
Yes
Responses
200 - Returns the updated profile.
401 - Authentication failed (unauthorized).
404 - The specified profile doesn't exist.
503 - The server is too busy to handle the request.
Example
Request
PUT https://yourserver.blueconic.net/rest/profiles/45e2a650-ca17-4e03-8e8d-12d00ed4d9b3?alt=xml
replaceBy=1af1a5ac-0fbb-40eb-91ff-f9909b3fb2d6
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<profile>
<id>45e2a650-ca17-4e03-8e8d-12d00ed4d9b3</id>
<replaceBy>
<profile>
<id>d1af1a5ac-0fbb-40eb-91ff-f9909b3fb2d6</id>
</profile>
</replaceBy>
<properties />
<segments />
</profile>
Update or create multiple profiles at once (bulk)
Synopsis
PUT https://yourserver.blueconic.net/rest/profiles
PUT https://yourserver.blueconic.net/rest/profiles?objectiveIds=objectiveID_1,objectiveID_2
Description
Update or create multiple profiles in a single request. This API call should be used when modifying large numbers of profiles instead of doing separate calls for each profile.
The format of this API call is different fromother profile APIs: it only accepts a JSON body and it will return a JSON response.
Parameters
The querystring of a profile bulk API request may contain an “objectiveIds” parameter. If present, these objective ID’s are matched against the consented objectives of a profile update, in case the profile is in the “GDPR” privacy legislation zone.
Name
Required
Data Type
Default
Value(s)
Description
objectiveIds
No
String
null
Comma separated list of objective IDs.
A list of ID’s that should map on objectives that are configured in the BlueConic UI. If passed, the profiles to be updated that are in the GDPR privacy legislation zone are matched against these objectives. If there is no match, the profile won’t be updated (or created, for that matter).
If a profile would have been created/updated, but is skipped because of an objective mismatch, the response will contain a “CONSENT_MISMATCH” state for that profile.
The body of a profile bulk API request consists of an array of profile operation objects. A singleprofile operation object (i.e. one object in the parameters array) mayhave the following parameters:
Name
Required
Data Type
Default
Value(s)
Description
identifier
No
String
null
any value
An (external) identifier which can be passed along with an operation and is returned in the response.
matching
No
Object[][]
null
[[{id: "email", value: "[email protected]"}]]
The profile properties to match. Only profile properties marked as "Unique Identifier"can be used. This isan array of arrays; the items in the outer array have an "OR" relation, the items in the inner array have an "AND" relation.
profileId
No
String
null
any BlueConic profile ID
The profile ID to search for. When used, it overrides possible matching criteria.
create
No
Boolean
"false"
"true", "false"
When true, creates a new profile if no profile is found matching the given criteria.
domainGroup
No
String
"DEFAULT"
any domaingroup ID
Specifies the domain group in which a profile is created. Used for matching and creating profiles.
permissionLevel
No
String
Default permission level of privacy tab
"PERSONAL", "ANONYMOUS", "DO_NOT_TRACK"
The permission used for creating profiles (not for matching).
privacyLegislation
No
String
null
“GDPR”, “NONE”
The default privacy legislation for creating profiles (not for matching).
restriction
No
Object
null
"isMemberOfSegment": Any segment UUID
The possible restriction rules when matching profiles. Only "isMemberOfSegment" is available at the moment.
properties
No
Object[]
null
[ { "id": "myproperty1", "values": ["value1", "value2"], "strategy": "ADD" } ]
The rules that will be executed on this profile.
Strategy mustbe one of the following types:
- ADD
- SET
- SET_IF_EMPTY
The following properties have a special meaning:
“privacy_legislation”: the value passed in this property should either be “GDPR” or “NONE”, and is used to determine if a profile should be matched against the passed “objectiveIds” in the querystring.
“consented_objectives”: the value(s) passed in this property are used to match against the passed “objectiveIds” in the querystring. At least one must match in order for the profile to be created/updated, otherwise “CONSENT_MISMATCH” is returned.
“refused_objectives”: ”: the value(s) passed in this property are used to set the explicitly refused objectives
Privacy legislation
The following values are valid privacy legislation values.
Name
Description
GDPR
Indicates that a profile is in the “GDPR zone”. Any “objectiveIds” passed in the querystring are matched against the profile that is being created.
Matching is done against the special profile property “consented_objectives”, which reflects the objective IDs that the profile has explicitly consented to. So, for the profile to be created, the “properties” should at least contain one of the objective IDs passed in the querystring, for the property with id “consented_objectives”. Otherwise, the “CONSENT_MISMATCH” state is returned in the response.
NONE
The profile is not in the GDPR zone; profile will just be created.
Strategy
The following values are valid property rule strategies.
Name
Description
ADD
Values will be added to the values that already existed in the profile property. Duplicates will not be added.
SET
Values will overwrite the values that already existed in the profile property.
SET_IF_EMPTY
Only set values if the profile property is empty.
Authentication
Yes
Responses
200 - Returns a summary of the executed bulk request.
400 - The specified body is not valid.
401 - Authentication failed (unauthorized).
503 - The server is too busy to handle the request.
Example
Request
PUT https://yourserver.blueconic.net/rest/profiles?alt=json
Request body
[{
"profileId": "dd9ba129-017f-4c54-bde9-22e66a46df28",
"properties": [{
"id": "crm_id",
"values": ["003Kz4Bsaa14"],
"strategy": "SET"
}]
},
{
"matching": [
[{
"id": "email",
"value": "[email protected]"
}],
[{
"id": "crm_id",
"value": "002wC4BadR1w"
}]
],
"properties": [{
"id": "zipcode",
"values": ["02111", "02112"],
"strategy": "ADD"
},
{
"id": "email",
"values": ["[email protected]"],
"strategy": "SET"
},
{
"id": "crm_id",
"values": ["002wC4BadR1w"],
"strategy": "SET"
}],
"create": "true",
"domainGroup": "2a9ba2ea-011c-4c2d-ada9-62e2a4b1df2b"
}]
This request contains two operations:
The first operation looks up aspecificBlueConic profile by its id, then sets the property with id crm_id to003Kz4Bsaa14. If the profile cannot be found, nothing will happen.
The second operation tries to find profiles that either have an email address [email protected] or a crm_id of002wC4BadR1w in the specified domain. If any profile is found, three properties will be set:
Zip codes 02111 and 02112 will be added
Email address will be set to [email protected]
crm_id will be set to 002wC4BadR1w
If no match can be found, a new profile is created in the specified domain andthe three properties willbe set in it.
JSON Response
Every bulk operation is returned in the response as well.
The state can be one of the following values: "CREATED", "MODIFIED", "UNCHANGED", "NOTFOUND", "RESTRICTION_MISMATCH"or “CONSENT_MISMATCH”.
[{
"state": "CREATED",
"profileId": "profile-UUID of the created profile",
"identifier": " my-external-identifier"
}]
Set the permission level of a profile
Synopsis
PUT https://yourserver.blueconic.net/rest/profiles/[profile]/permissions
Description
Updates the permission level of a profile.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Path
profile
Yes
String
null
any UUID
The ID of the profile
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Form
level
Yes
String
null
"ANONYMOUS", "PERSONAL"
The level to set.
Authentication
Yes
Responses
200 - Returns the updated profile.
400 - One or more required parameters is missing or invalid.
401 - Authentication failed (unauthorized).
404 - The specified profile doesn't exist.
503 - The server is too busy to handle the request.
Example
Request
PUT https://yourserver.blueconic.net/rest/profiles/45e2a650-ca17-4e03-8e8d-12d00ed4d9b3/permissions?alt=xml
level=PERSONAL
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<profile>
<id>45e2a650-ca17-4e03-8e8d-12d00ed4d9b3</id>
<permissions>
<level>PERSONAL</level>
</permissions>
<properties />
<segments />
</profile>
Set the permission level exceptions of a profile
Synopsis
PUT https://yourserver.blueconic.net/rest/profiles/[profile]/permissions/permissions/exceptions/[mode]/[type]
Description
Updates the permission level exceptions of a profile. Plugin IDs and profile property IDs can be used to optin or optout for the usage of them.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Path
profile
Yes
String
null
any UUID
The ID of the profile
Path
mode
Yes
String
null
optIn, optOut
Specifies optin or optout.
Path
type
Yes
String
null
plugins, profileProperties
Specifies the type of the exception.
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Form
ids
Yes
String
null
any UUID
The ids of the exceptions to set.
Authentication
Yes
Responses
200 - No specific content.
400 - One or more required parameters is missing or invalid.
401 - Authentication failed (unauthorized).
404 - The specified profile doesn't exist.
503 - The server is too busy to handle the request.
Example
Request
PUT https://yourserver.blueconic.net/rest/profiles/45e2a650-ca17-4e03-8e8d-12d00ed4d9b3/permissions/exceptions/optIn/plugins
ids=plugin1&ids=plugin2
Delete one profile
Synopsis
DELETE https://yourserver.blueconic.net/rest/profiles/[profile]
Description
Deletes the specified BlueConic profile.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Path
profile
Yes
String
null
any UUID
The ID of the profile
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Authentication
Yes
Responses
200 - Returns the deleted profile.
401 - Authentication failed (unauthorized).
404 - The specified profile doesn't exist.
503 - The server is too busy to handle the request.
Example
Request
DELETE https://yourserver.blueconic.net/rest/profiles/45e2a650-ca17-4e03-8e8d-12d00ed4d9b3?alt=xml
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<profile>
<id>45e2a650-ca17-4e03-8e8d-12d00ed4d9b3</id>
<properties>
<property>
<id>email</id>
<values>
<value>[email protected]</value>
</values>
</property>
<property>
<id>hobby</id>
<values>
<value>soccer</value>
<value>tennis</value>
</values>
</property>
</properties>
<segments>
<segment>
<id>dd69b76f-8e0d-43bf-bf93-56d05bdcef4e</id>
</segment>
<segment>
<id>50622c8f-de0d-4a25-af0d-e52a26b68f40</id>
</segment>
</segments>
</profile>
Search for profiles
Synopsis
GET https://yourserver.blueconic.net/rest/profiles
Description
Searches for BlueConic profiles based on a specific values for an indexed (unique) properties. Multiple name/value pairs can be used to refine the search.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Querystring
property
Yes
String
null
any String
Specifies the id of property to search for ("email" for example).
Querystring
value
Yes
String
null
any String
The value of the property to search for ("[email protected]" for example).
Authentication
Yes
Responses
200 - Returns the ID of the top 100 matching profiles.
400 - One or more required parameters is missing or invalid.
401 - Authentication failed (unauthorized).
501 - The specified property is not classified as indexed (unique) (not implemented).
503 - The server is too busy to handle the request.
Example
Request
GET https://yourserver.blueconic.net/rest/profiles?property=email&[email protected]&alt=xml
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<profiles total="2">
<profile>
<id>61835134-e910-49da-a09e-79d41af9b96</id>
</profile>
<profile>
<id>45e2a650-ca17-4e03-8e8d-12d00ed4d9b3</id>
</profile>
<itemsPerPage>1</itemsPerPage>
<startIndex>0</startIndex>
<totalPages>1</totalPages>
<totalResults>1</totalResults>
</profiles>
Get timeline events for one profile
Synopsis
GET https://yourserver.blueconic.net/rest/profiles/[profile]/timeline
Description
Retrieves timeline events for the specified profile.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Querystring
eventTypeId
No
String
null
ID of the timeline event type.
Filter returned timeline events for a specific type. Only one timeline event type ID is allowed.
Querystring
count
No
String
20
any number
The maximum number of timeline events to return.
Querystring
fromDate
No
String
null
any date
Filter to only include timeline events that are dated later than this date. The format of fromDate is "2018-01-01T00:00Z" or with a timezone offset "2018-01-01T00:00+05:00"
Querystring
toDate
No
String
null
any date
Filter to only include timeline events that are dated before this date. The format of toDate is "2018-01-01T00:00Z" or with a timezone offset "2018-01-01T00:00+05:00"
Querystring
prettyPrint
No
String
null
"true"
Set to "true" to return the JSON result in a readable pretty print format.
Authentication
Yes
Responses
200 - Returns the ID of the top 100 matching profiles.
400 - One or more required parameters is missing or invalid.
401 - Authentication failed (unauthorized).
501 - The specified property is not classified as indexed (unique) (not implemented).
503 - The server is too busy to handle the request.
Example
Request
GET https://yourserver.blueconic.net/rest/profiles?property=email&[email protected]&alt=xml
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<profiles total="2">
<profile>
<id>61835134-e910-49da-a09e-79d41af9b96</id>
</profile>
<profile>
<id>45e2a650-ca17-4e03-8e8d-12d00ed4d9b3</id>
</profile>
<itemsPerPage>1</itemsPerPage>
<startIndex>0</startIndex>
<totalPages>1</totalPages>
<totalResults>1</totalResults>
</profiles>
Profile Event methods
The following methods allow you to retrieve profile event information.
Get events for a profile
Synopsis
GET https://yourserver.blueconic.net/rest/profileEvents/[profile]
Description
Retrieves the events of a profile.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Path
profile
Yes
String
null
any UUID
The ID of the profile
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Authentication
Yes
Responses
200 - Returns the events.
401 - Authentication failed (unauthorized).
404 - The profile never existed.
503 - The server is too busy to handle the request.
Example
Request
GET https://yourserver.blueconic.net/rest/profileEvents/45e2a650-ca17-4e03-8e8d-12d00ed4d9b3
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<profileEvents>
<events>
<itemsPerPage>20</itemsPerPage>
<startIndex>0</startIndex>
<totalPages>1</totalPages>
<totalResults>1</totalResults>
<event>
<date>2012-08-17T14:31+0200</date>
<properties>
<property>
<id>ToLevel</id>
<values>
<value>ANONYMOUS</value>
</values>
</property>
<property>
<id>FromLevel</id>
<values>
<value>PERSONAL</value>
</values>
</property>
</properties>
<type>PermissionLevelChanged</type>
</event>
</events>
<profile>
<id>7bce7bfe-f433-4be4-82f2-5018c6dff5b2</id>
</profile>
</profileEvents>
Interaction methods
The following methods allow you to retrieve and post interaction event information.
Get interactions
Synopsis
GET https://yourserver.blueconic.net/rest/interactions
Description
Retrieves the interactions for a page view.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Querystring
url
Yes
String
null
any URL
The URL of the current page.
Querystring
profile
No
String
null
any UUID
The ID of the profile.
Authentication
No
Responses
200 - Returns the interactions.
400 - One or more required parameters is missing or invalid.
503 - The server is too busy to handle the request.
Example
Request
GET https://yourserver.blueconic.net/rest/interactions?profile=45e2a650-ca17-4e03-8e8d-12d00ed4d9b3&url=http\%3A\%2F\%2Fwww.example.com\%2F
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<interactions total="2">
<interaction>
<defaultLocale>nl_NL</defaultLocale>
<id>6d2dc916-08ce-412f-aa5d-f75eb95f8a9c</id>
<name>Sample Interactions</name>
<parameters>
<parameter>
<id>sampleparameter</id>
<values locale="en_US">
<value>en 1</value>
<value>en 2</value>
</values>
<values locale="nl_NL">
<value>dutch</value>
</values>
</parameter>
<parameter>
<id>width</id>
<values locale="en_US">
<value>800</value>
</values>
<values locale="nl_NL">
<value>800</value>
</values>
</parameter>
</parameters>
<position>position_1</position>
</interaction>
<interaction>
<defaultLocale>nl_NL</defaultLocale>
<id>demolistenerinteractiontype</id>
<name>demolistenerinteractiontype</name>
</interaction>
</interactions>
Register pageview events
Synopsis
POST https://yourserver.blueconic.net/rest/pageviewEvents
Description
Registers pageview events for reporting.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Form
url
Yes
String
null
any URL
The URL of the current page.
Form
referrer
No
String
null
any URL
The URL of the previous (referring) page.
Form
profile
No
String
null
any UUID
The ID of the profile that triggered the event. For this profile, the properties "firstvisit", "visiteddomain" and "visitedchannel" are updated.
Authentication
No
Responses
200 - No specific content.
400 - One or more required parameters is missing or invalid.
503 - The server is too busy to handle the request.
Register interaction events
Synopsis
POST https://yourserver.blueconic.net/rest/interactionEvents
Description
Registers interaction events for reporting.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Querystring
type
Yes
String
null
"VIEW", "CLICK", "CONVERSION"
The event type.
Querystring
interaction
Yes
String
null
any UUID
The ID of the interaction.
Querystring
url
Yes
String
null
any URL
The URL of the current page.
Authentication
No
Responses
200 - No specific content.
400 - One or more required parameters is missing or invalid.
503 - The server is too busy to handle the request.
URL mapping methods
The following methods allow you to retrieve and post URL mapping information.
Create new URL mapping
Synopsis
POST https://yourserver.blueconic.net/rest/urlmappings
Description
Creates a new URL mapping.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Form
url
Yes
String
null
any URL
The target URL of the mapping.
Authentication
Yes
Responses
200 - Returns the created urlmapping.
400 - One or more required parameters is missing or invalid.
401 - Authentication failed (unauthorized).
503 - The server is too busy to handle the request.
Example
Request
POST https://yourserver/rest/urlmappings?alt=xml
url=http\%3A\%2F\%2Fwww.example.com
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<urlmapping>
<id>4Q</id>
<properties />
<url>http://www.example.com</url>
</urlmapping>
Get one URL mapping
Synopsis
GET https://yourserver.blueconic.net/rest/urlmappings/[urlmapping]
Description
Retrieves the metadata of the specified URL mapping.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Path
urlmapping
Yes
String
null
any UUID
The ID of the URL mapping.
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Authentication
Yes
Responses
200 - Returns the urlmapping.
401 - Authentication failed (unauthorized).
404 - The specified URL mapping doesn't exist.
503 - The server is too busy to handle the request.
Example
Request
GET https://yourserver.blueconic.net/rest/urlmappings/4Q
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<urlmapping>
<id>4Q</id>
<properties />
<url>http://www.example.com</url>
</urlmapping>
Update URL mapping properties
Synopsis
PUT https://yourserver.blueconic.net/rest/urlmappings/[urlmapping]/properties
Description
Updates the stored properties of the specified URL mapping.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Path
urlmapping
Yes
String
null
any UUID
The ID of the URL mapping.
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Form
property=value
Yes
String
null
any name-value pair
The property and value to set, multiple values for properties are allowed.
Authentication
Yes
Responses
200 - Returns the urlmapping.
401 - Authentication failed (unauthorized).
404 - The specified URL mapping doesn't exist.
503 - The server is too busy to handle the request.
Example
Request
PUT https://yourserver.blueconic.net/rest/urlmappings/4Q/properties?alt=xml
property1=value1&property1=value2&property2=value3
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<urlmapping>
<id>4Q</id>
<properties>
<property>
<id>property1</id>
<values>
<value>value1</value>
<value>value2</value>
</values>
</property>
<property>
<id>property2</id>
<values>
<value>value3</value>
</values>
</property>
</properties>
<url>http://www.example.com</url>
</urlmapping>
Domain methods
The following methods allow you to create, modify, retrieve properties from and delete BlueConic domains, channels and positions.
Get all domains
Synopsis
GET https://yourserver.blueconic.net/rest/domains
Description
Retrieves the domains.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Querystring
startIndex
No
String
0
any number
Specifies the index of the first item to include in the result.
Querystring
count
No
String
20
any number
Specifies the number of results to return.
Authentication
Yes
Responses
200 - Returns the domains.
401 - Authentication failed (unauthorized).
503 - The server is too busy to handle the request.
Example
Request
GET https://yourserver.blueconic.net/rest/domains
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<domains>
<itemsPerPage>20</itemsPerPage>
<startIndex>0</startIndex>
<totalPages>1</totalPages>
<totalResults>1</totalResults>
<domain>
<channels>
<channel>
<aliases>
<alias>alias2</alias>
<alias>alias3</alias>
<alias>alias1</alias>
</aliases>
<hostname>www.example.com</hostname>
<id>da94cd6a-c741-4962-9feb-492fed796b26</id>
<links>
<link>
<href>
https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326
/channels/da94cd6a-c741-4962-9feb-492fed796b26?alt=xml
</href>
<rel>self</rel>
<type>xml</type>
</link>
</links>
<name>Example channel</name>
<type>WEBSITE</type>
<visitorCount>0</visitorCount>
</channel>
</channels>
<id>885f0954-fd4e-4a08-a987-e2a047c9f326</id>
<links>
<link>
<href>
https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326?alt=xml
</href>
<rel>self</rel>
<type>xml</type>
</link>
</links>
<logo>
<link>
<href>
https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/logo
?etag=005310aba7fd1ef3ff0223ca166b9c
</href>
<rel>self</rel>
</link>
</logo>
<name>Test domain 1327052341899</name>
<visitorCount>0</visitorCount>
</domain>
</domains>
Get one domain
Synopsis
GET https://yourserver.blueconic.net/rest/domains/[domainid]
Description
Retrieves a single domain.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Path
domainid
Yes
String
null
any UUID
The ID of the domain.
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Authentication
Yes
Responses
200 - Returns the domain.
401 - Authentication failed (unauthorized).
404 - The domain doesn't exist.
503 - The server is too busy to handle the request.
Example
Request
GET https://yourserver.blueconic.net/rest/domains/bf6af51d-b077-4565-9bac-8a97d42f807c
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<domain>
<channels />
<id>bf6af51d-b077-4565-9bac-8a97d42f807c</id>
<links>
<link>
<href>
https://yourserver.blueconic.net/rest/domains/bf6af51d-b077-4565-9bac-8a97d42f807c?alt=xml
</href>
<rel>self</rel>
<type>xml</type>
</link>
</links>
<logo />
<name>Example domain 2</name>
<visitorCount>0</visitorCount>
</domain>
Create new domain
Synopsis
POST https://yourserver.blueconic.net/rest/domains
Description
Creates a domain.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Form
name
No
String
null
any String
The name of the domain.
Authentication
Yes
Responses
200 - Returns the created domain.
401 - Authentication failed (unauthorized).
503 - The server is too busy to handle the request.
Example
Request
POST https://yourserver.blueconic.net/rest/domains
name=Example+domain
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<domain>
<channels />
<id>bf6af51d-b077-4565-9bac-8a97d42f807c</id>
<links>
<link>
<href>
https://yourserver.blueconic.net/rest/domains/bf6af51d-b077-4565-9bac-8a97d42f807c?alt=xml
</href>
<rel>self</rel>
<type>xml</type>
</link>
</links>
<logo />
<name>Example domain</name>
<visitorCount>0</visitorCount>
</domain>
Update a domain
Synopsis
PUT https://yourserver.blueconic.net/rest/domains/[domain]
Description
Updates a domain.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Path
domain
Yes
String
null
any UUID
The ID of the domain.
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Form
name
No
String
null
any String
The name of the domain.
Authentication
Yes
Responses
200 - Returns the updated domain.
401 - Authentication failed (unauthorized).
404 - The domain doesn't exist.
503 - The server is too busy to handle the request.
Example
Request
PUT https://yourserver.blueconic.net/rest/domains/bf6af51d-b077-4565-9bac-8a97d42f807c
name=Example+domain+2
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<domain>
<channels />
<id>bf6af51d-b077-4565-9bac-8a97d42f807c</id>
<links>
<link>
<href>
https://yourserver.blueconic.net/rest/domains/bf6af51d-b077-4565-9bac-8a97d42f807c?alt=xml
</href>
<rel>self</rel>
<type>xml</type>
</link>
</links>
<logo />
<name>Example domain 2</name>
<group>9efb8a28-bfdf-4a10-b4f4-c0fb3a9a8dcc</group>
<visitorCount>0</visitorCount>
</domain>
Delete a domain
Synopsis
DELETE https://yourserver.blueconic.net/rest/domains/[domainid]
Description
Updates a domain.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Path
domainid
Yes
String
null
any UUID
The ID of the domain.
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Authentication
Yes
Responses
200 - Returns the deleted domain.
401 - Authentication failed (unauthorized).
404 - The domain doesn't exist.
503 - The server is too busy to handle the request.
Example
Request
DELETE https://yourserver.blueconic.net/rest/domains/bf6af51d-b077-4565-9bac-8a97d42f807c
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<domain>
<channels />
<id>bf6af51d-b077-4565-9bac-8a97d42f807c</id>
<links>
<link>
<href>
https://yourserver.blueconic.net/rest/domains/bf6af51d-b077-4565-9bac-8a97d42f807c?alt=xml
</href>
<rel>self</rel>
<type>xml</type>
</link>
</links>
<logo />
<name>Example domain 2</name>
<visitorCount>0</visitorCount>
</domain>
Get channels of a domain
Synopsis
GET https://yourserver.blueconic.net/rest/domains/[domainid]/channels
Description
Retrieves all channels of a domain.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Path
domainid
Yes
String
null
any UUID
The ID of the domain.
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Authentication
Yes
Responses
200 - Returns all channels.
401 - Authentication failed (unauthorized).
404 - The domain doesn't exist.
503 - The server is too busy to handle the request.
Example
Request
GET https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/channels
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<channels>
<channel>
<aliases>
<alias>alias2</alias>
<alias>alias3</alias>
<alias>alias1</alias>
</aliases>
<hostname>www.example.com</hostname>
<id>da94cd6a-c741-4962-9feb-492fed796b26</id>
<links>
<link>
<href>
https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326
/channels/da94cd6a-c741-4962-9feb-492fed796b26?alt=xml
</href>
<rel>self</rel>
<type>xml</type>
</link>
</links>
<name>Example channel</name>
<positions>
<position>
<id>b33db6d6-93da-4275-aa68-2e87e27d06c2</id>
<links>
<link>
<href>
https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/channels
/da94cd6a-c741-4962-9feb-492fed796b26/positions/b33db6d6-93da-4275-aa68-2e87e27d06c2?alt=xml
</href>
<rel>self</rel>
<type>xml</type>
</link>
</links>
</position>
</positions>
<type>WEBSITE</type>
<visitorCount>0</visitorCount>
</channel>
</channels>
Get one channel
Synopsis
GET https://yourserver.blueconic.net/rest/domains/[domainid]/channels/[channelid]
Description
Retrieves a single channel.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Path
domainid
Yes
String
null
any UUID
The ID of the domain.
Path
channelid
Yes
String
null
any UUID
The ID of the channel.
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Authentication
Yes
Responses
200 - Returns the channel.
401 - Authentication failed (unauthorized).
404 - The channel doesn't exist.
503 - The server is too busy to handle the request.
Example
Request
GET https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/channels/da94cd6a-c741-4962-9feb-492fed796b26
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<channel>
<aliases>
<alias>alias2</alias>
<alias>alias3</alias>
<alias>alias1</alias>
</aliases>
<hostname>www.example.com</hostname>
<id>da94cd6a-c741-4962-9feb-492fed796b26</id>
<links>
<link>
<href>
https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/channels
/da94cd6a-c741-4962-9feb-492fed796b26?alt=xml
</href>
<rel>self</rel>
<type>xml</type>
</link>
</links>
<name>Example channel</name>
<positions>
<position>
<id>b33db6d6-93da-4275-aa68-2e87e27d06c2</id>
<links>
<link>
<href>
https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/channels
/da94cd6a-c741-4962-9feb-492fed796b26/positions/b33db6d6-93da-4275-aa68-2e87e27d06c2?alt=xml
</href>
<rel>self</rel>
<type>xml</type>
</link>
</links>
</position>
</positions>
<type>WEBSITE</type>
<visitorCount>0</visitorCount>
</channel>
Create new channel
Synopsis
POST https://yourserver.blueconic.net/rest/domains/[domainid]/channels
Description
Creates a channel.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Path
domainid
Yes
String
null
any UUID
The ID of the domain.
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Form
name
No
String
null
any String
The name of the channel.
Authentication
Yes
Responses
200 - Returns the created channel.
401 - Authentication failed (unauthorized).
404 - The domain doesn't exist.
503 - The server is too busy to handle the request.
Example
Request
POST https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/channels
name=Example+channel
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<channel>
<aliases/>
<id>da94cd6a-c741-4962-9feb-492fed796b26</id>
<links>
<link>
<href>
https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/channels
/da94cd6a-c741-4962-9feb-492fed796b26?alt=xml
</href>
<rel>self</rel>
<type>xml</type>
</link>
</links>
<name>Example channel</name>
<positions/>
<type>WEBSITE</type>
<visitorCount>0</visitorCount>
</channel>
Update a channel
Synopsis
PUT https://yourserver.blueconic.net/rest/domains/[domainid]/channels/[channelid]
Description
Updates a channel.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Path
domainid
Yes
String
null
any UUID
The ID of the domain.
Path
channelid
Yes
String
null
any UUID
The ID of the channel.
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Form
name
No
String
null
any String
The name of the channel.
Form
type
No
String
null
"WEBSITE", "EMAIL", "TWITTER", or "FACEBOOK"
The type of the domain.
Form
hostname
No
String
null
any String
The hostname of the channel.
Form
alias
No
String
null
any String
The zero or more aliases of the channel.
Authentication
Yes
Responses
200 - Returns the updated channel.
400 - An invalid channel type was specified.
401 - Authentication failed (unauthorized).
404 - The channel doesn't exist.
503 - The server is too busy to handle the request.
Example
Request
PUT https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/channels/da94cd6a-c741-4962-9feb-492fed796b26
name=Example+channel&type=WEBSITE&hostname=www.example.com&alias=alias1&alias=alias2&alias=alias3
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<channel>
<aliases>
<alias>alias2</alias>
<alias>alias3</alias>
<alias>alias1</alias>
</aliases>
<hostname>www.example.com</hostname>
<id>da94cd6a-c741-4962-9feb-492fed796b26</id>
<links>
<link>
<href>
https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/channels
/da94cd6a-c741-4962-9feb-492fed796b26?alt=xml
</href>
<rel>self</rel>
<type>xml</type>
</link>
</links>
<name>Example channel</name>
<positions>
<position>
<id>b33db6d6-93da-4275-aa68-2e87e27d06c2</id>
<links>
<link>
<href>
https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/channels
/da94cd6a-c741-4962-9feb-492fed796b26/positions/b33db6d6-93da-4275-aa68-2e87e27d06c2?alt=xml
</href>
<rel>self</rel>
<type>xml</type>
</link>
</links>
</position>
</positions>
<type>WEBSITE</type>
<visitorCount>0</visitorCount>
</channel>
Delete a channel
Synopsis
DELETE https://yourserver.blueconic.net/rest/domains/[domainid]/channels/[channelid]
Description
Deletes a channel.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Path
domainid
Yes
String
null
any UUID
The ID of the domain.
Path
channelid
Yes
String
null
any UUID
The ID of the channel.
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Authentication
Yes
Responses
200 - Returns the deleted channel.
401 - Authentication failed (unauthorized).
404 - The channel doesn't exist.
503 - The server is too busy to handle the request.
Example
Request
DELETE https://yourserver.blueconic.net/rest/domains/bf6af51d-b077-4565-9bac-8a97d42f807c
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<channel>
<aliases>
<alias>alias2</alias>
<alias>alias3</alias>
<alias>alias1</alias>
</aliases>
<hostname>www.example.com</hostname>
<id>da94cd6a-c741-4962-9feb-492fed796b26</id>
<links>
<link>
<href>
https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/channels
/da94cd6a-c741-4962-9feb-492fed796b26?alt=xml
</href>
<rel>self</rel>
<type>xml</type>
</link>
</links>
<name>Example channel</name>
<positions>
<position>
<id>b33db6d6-93da-4275-aa68-2e87e27d06c2</id>
<links>
<link>
<href>
https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/channels
/da94cd6a-c741-4962-9feb-492fed796b26/positions/b33db6d6-93da-4275-aa68-2e87e27d06c2?alt=xml
</href>
<rel>self</rel>
<type>xml</type>
</link>
</links>
</position>
</positions>
<type>WEBSITE</type>
<visitorCount>0</visitorCount>
</channel>
Get positions of a channel
Synopsis
GET https://yourserver.blueconic.net/rest/domains/[domainid]/channels/[channelid]/positions
Description
Retrieves all positions of a channel.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Path
domainid
Yes
String
null
any UUID
The ID of the domain.
Path
channelid
Yes
String
null
any UUID
The ID of the channel.
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Authentication
Yes
Responses
200 - Returns all positions of a channel.
401 - Authentication failed (unauthorized).
404 - The channel doesn't exist.
503 - The server is too busy to handle the request.
Example
Request
GET https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/channels/da94cd6a-c741-4962-9feb-492fed796b26/positions
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<positions>
<position>
<id>b33db6d6-93da-4275-aa68-2e87e27d06c2</id>
<links>
<link>
<href>
https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/channels
/da94cd6a-c741-4962-9feb-492fed796b26/positions/b33db6d6-93da-4275-aa68-2e87e27d06c2?alt=xml
</href>
<rel>self</rel>
<type>xml</type>
</link>
</links>
<name>New position</name>
</position>
<position>
<id>c3633c12-8ed4-45c7-ac31-d95921648189</id>
<links>
<link>
<href>
https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/channels
/da94cd6a-c741-4962-9feb-492fed796b26/positions/c3633c12-8ed4-45c7-ac31-d95921648189?alt=xml
</href>
<rel>self</rel>
<type>xml</type>
</link>
</links>
<name>New position</name>
</position>
</positions>
Get one position
Synopsis
GET https://yourserver.blueconic.net/rest/domains/[domainid]/channels/[channelid]/positions/[positionid]
Description
Retrieves a single position.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Path
domainid
Yes
String
null
any UUID
The ID of the domain.
Path
channelid
Yes
String
null
any UUID
The ID of the channel.
Path
positionid
Yes
String
null
any UUID
The ID of the position.
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Authentication
Yes
Responses
200 - Returns the position.
401 - Authentication failed (unauthorized).
404 - The position doesn't exist.
503 - The server is too busy to handle the request.
Example
Request
GET https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/channels/da94cd6a-c741-4962-9feb-492fed796b26/positions/b33db6d6-93da-4275-aa68-2e87e27d06c2
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<position>
<id>b33db6d6-93da-4275-aa68-2e87e27d06c2</id>
<links>
<link>
<href>
https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/channels
/da94cd6a-c741-4962-9feb-492fed796b26/positions/b33db6d6-93da-4275-aa68-2e87e27d06c2?alt=xml
</href>
<rel>self</rel>
<type>xml</type>
</link>
</links>
<name>Banner 01</name>
<positionIdentifier>banner01</positionIdentifier>
</position>
Create new position
Synopsis
POST https://yourserver.blueconic.net/rest/domains/[domainid]/channels/[channelid]/positions
Description
Creates a position.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Path
domainid
Yes
String
null
any UUID
The ID of the domain.
Path
channelid
Yes
String
null
any UUID
The ID of the channel.
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Form
name
No
String
null
any String
The name of the position.
Authentication
Yes
Responses
200 - Returns the created position.
401 - Authentication failed (unauthorized).
404 - The channel doesn't exist.
503 - The server is too busy to handle the request.
Example
Request
POST https://yourserver.blueconic.com/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/channels/da94cd6a-c741-4962-9feb-492fed796b26/positions
name=Banner+01
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<position>
<id>b33db6d6-93da-4275-aa68-2e87e27d06c2</id>
<links>
<link>
<href>
https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/channels
/da94cd6a-c741-4962-9feb-492fed796b26/positions/b33db6d6-93da-4275-aa68-2e87e27d06c2?alt=xml
</href>
<rel>self</rel>
<type>xml</type>
</link>
</links>
<name>Banner 01</name>
</position>
Update a position
Synopsis
PUT https://yourserver.blueconic.net/rest/domains/[domainid]/channels/[channelid]/positions/[positionid]
Description
Updates a position.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Path
domainid
Yes
String
null
any UUID
The ID of the domain.
Path
channelid
Yes
String
null
any UUID
The ID of the channel.
Path
positionid
Yes
String
null
any UUID
The ID of the position.
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Form
name
No
String
null
any String
The name of the position.
Form
positionIdentifier
No
String
null
any String
The identifier of the position, e.g. the ID of a DIV.
Authentication
Yes
Responses
200 - Returns the updated position.
401 - Authentication failed (unauthorized).
404 - The position doesn't exist.
503 - The server is too busy to handle the request.
Example
Request
PUT https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/channels/da94cd6a-c741-4962-9feb-492fed796b26/positions/b33db6d6-93da-4275-aa68-2e87e27d06c2
name=Banner+01&positionIdentifier=banner01
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<position>
<id>b33db6d6-93da-4275-aa68-2e87e27d06c2</id>
<links>
<link>
<href>
https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/channels
/da94cd6a-c741-4962-9feb-492fed796b26/positions/b33db6d6-93da-4275-aa68-2e87e27d06c2?alt=xml
</href>
<rel>self</rel>
<type>xml</type>
</link>
</links>
<name>Banner 01</name>
<positionIdentifier>banner01</positionIdentifier>
</position>
Delete a position
Synopsis
DELETE https://yourserver.blueconic.net/rest/domains/[domainid]/channels/[channelid]/positions/[positionid]
Description
Updates a position.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Path
domainid
Yes
String
null
any UUID
The ID of the domain.
Path
channelid
Yes
String
null
any UUID
The ID of the channel.
Path
positionid
Yes
String
null
any UUID
The ID of the position.
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Authentication
Yes
Responses
200 - Returns the deleted position.
401 - Authentication failed (unauthorized).
404 - The position doesn't exist.
503 - The server is too busy to handle the request.
Example
Request
DELETE https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/channels/da94cd6a-c741-4962-9feb-492fed796b26/positions/b33db6d6-93da-4275-aa68-2e87e27d06c2
XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<position>
<id>b33db6d6-93da-4275-aa68-2e87e27d06c2</id>
<links>
<link>
<href>
https://yourserver.blueconic.net/rest/domains/885f0954-fd4e-4a08-a987-e2a047c9f326/channels
/da94cd6a-c741-4962-9feb-492fed796b26/positions/b33db6d6-93da-4275-aa68-2e87e27d06c2?alt=xml
</href>
<rel>self</rel>
<type>xml</type>
</link>
</links>
<name>Banner 01</name>
<positionIdentifier>banner01</positionIdentifier>
</position>
Profile property methods
The following methods allow you to retrieve profile properties.
Get all profile properties
Synopsis
GET https://yourserver.blueconic.net/rest/profileProperties
Description
Retrieves the profile properties.
Parameter(s)
Parameter Type
Name
Required
Data Type
Default
Value(s)
Description
Querystring
alt
No
String
"xml"
"xml", "json"
Specifies the format in which to return the result.
Querystring
count
No
String
20
any integer
Specifies the number of results to return.
Querystring
startIndex
No
String
0
any integer
Specifies the index of the first item to include in the result.
Querystring
filterType
No
String
no filtering
"SELECT", "RANGE", "DATETIME"
The filterType of the profile properties e.g "SELECT", "RANGE" AND "DATETIME". Multiple values are allowed.
Querystring
filterValue
No
String
no filtering
any filter
If specified, a label of the name of the profile properties must match the value. The la
View ArticleMarketing teams use BlueConic to manage customer data privacy and consent compliance worldwide. BlueConic supports multiple legislation zones, including the CCPA, which went into effect January 1, 2020. For general information on managing privacy with BlueConic see the Privacy section of our Knowledge Base.
This FAQ covers questions specific to the California Consumer Privacy Act, or CCPA.
Webinar: Will CCPA change your marketing? Understanding the impact of privacy regulation
What is CCPA?
The California Consumer Privacy Act, or CCPA, aims to bring more transparency and control to California consumers. As part of this new legislation, California residents will have the right to:
Know what personal information is collected, used, shared or sold, both as to the categories and specific pieces of personal information
Delete personal information held by businesses and by extension, a business’s service provider
Opt-out of the sale of personal information
Consumers are able to direct a business that sells personal information to stop selling that information. Children under the age of 16 must provide opt-in consent, with a parent or guardian consenting for children under 13.
Nondiscrimination in terms of price or service when a consumer exercises a privacy right under CCPA
Where can I learn more about CCPA?
Teams charged with managing CCPA compliance should read up on the privacy act. For this FAQ, we used documents provided by the office of the attorney general in California and the National Law Review. We also suggest consulting with your legal team to understand how your company is handling compliance.
Who does CCPA apply to?
Businesses are subject to the CCPA if one or more of the following are true:
Has gross annual revenues in excess of $25 million
Buys, receives, or sells the personal information of 50,000 or more consumers, households, or devices
Derives 50 percent or more of annual revenues from selling consumers’ personal information
As proposed by the draft regulations, businesses that handle the personal information of more than 4 million consumers will have additional obligations.
What is the difference between CCPA and GDPR?
The California Consumer Privacy Act (CCPA) and the European Union’s General Data Protection Regulation (GDPR) are separate legal frameworks with different scopes, definitions, and requirements.
But a business that already complies with GDPR will likely have a leg up when it comes to complying with CCPA. However, the two legislations differ from one another in specific ways.
For example, under GDPR, companies must undertake a data inventory and mapping of data flows in furtherance of creating records to demonstrate compliance. Additional data mapping may be important to reflect the different requirements under CCPA.
Under GDPR, companies must develop processes and/or systems to respond to individual requests for access to personal information and for erasure of personal information. These processes and/or systems may be applied to handling CCPA consumer requests, although businesses may need to review and reconcile the different definitions of personal information and applicable rules on verification of consumer requests.
For other specifics on how these two legislations differ and how your company is handling these legislations, consult your legal team.
How does CCPA define personal information?
According to the National Law Review, the CCPA defines personal information broadly to include information that can identify, relate to, describe, be associated with, or be reasonably capable of being associated with a particular consumer or household. Significantly, the CCPA’s private right of action provision relating to data breaches incorporates a narrower definition of personal information (more on this below).
The statute provides a non-exhaustive list of categories of personal information, including:
Identifiers including real name, alias, postal address, unique personal identifier (UUID), online identifier, internet protocol (IP) address, email address, account name, social security number, driver’s license number, passport number, or other similar identifiers
Characteristics of protected classifications under California or federal law
Commercial information, including records of personal property, products, or services purchased, obtained, or considered, or other purchasing or consuming histories or tendencies
Biometric information
Internet or other electronic network activity information, including, but not limited to, browsing history, search history, and information regarding a consumer’s interaction with an internet website, application, or advertisement
Geolocation data
Audio, electronic, visual, thermal, olfactory, or similar information
Professional or employment-related information
Education information, defined as information that is not publicly available personally identifiable information as defined in the Family Educational Rights and Privacy Act (FERPA)
How can BlueConic help me to comply with CCPA?
Similar to GDPR we’ve enabled a new legislation zone for CCPA. For details and FAQs on our privacy and consent management, see our FAQ on privacy and consent management with BlueConic.
Watch this short video on enabling consent management in BlueConic for CCPA:
DoesBlueConicprovide consulting to its customers about how to be CCPA-compliant?
No.BlueConic is not a consulting or lawfirm. This document does not constitute legal advice.We recommend you consult your organization’s legal and/or privacy experts to determine what is required for your specific organization.
Sources
Content about CCPA adapted from the fact sheet written by the office of the attorney general in California and the National Law Review. This document was last updated on December 17, 2019.
Learn more about privacy compliance
Learn more about using BlueConic to manage privacy and consent for CCPA:
Privacy management in BlueConic
View ArticleOut-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 to completely round out your user profiles.
Single-value versus multi-value data
The attributes collected and storedby 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 intoyour customers and segments. Campaign tracking parameters are oftenstored in three ways: first, most recent, and all.
The informationgathered by BlueConic comes down to configuration.Marketers canconfigure BlueConic Listeners, which will enrich a visitor's profile based on their behavior or provided input. You can also configure BlueConic Connections to bring data in from other systems.
Profile property data the Global Listener collects automatically
The BlueConic Global Listener comes out of the box and collects the following pieces of data. The first set of values are overwritten each time they are captured (a single value is stored). The next set of values store persistent, multi-value data.
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)
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)
Origin of profile level 1: Type
Origin of profile level 2: Source
Origin of profile level 3: Detail
Page Views (Most Recent Visit)
Referrer Hostname (Most Recent)
Resolution (Most Recent)
Screen Height (Most Recent)
Screen Width (Most Recent)
Start Session
State (Most Recent)
State Code (Most Recent)
Time Zone (Most Recent)
UTM Campaign (Most Recent)
UTM Content (Most Recent)
UTM Medium (Most Recent)
UTM Source (Most Recent)
UTM Term (Most Recent)
Visits
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)
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
You can disable the Global Listener ifdesired. Contact your Customer Success Manager for more information.
*Note about search keywords
The Global Listener stores keywords from search engine results that include referral keywords, such as Lycos, Ask, and Dogpile.
Privacy management
Global listenerscan be added to Objectives, allowing for privacy management of the information that is being picked up. The Global Listener will only work if the visitor consented to at least one of the objectives that it is linked to.
View ArticleBlueConic is based on a Privacy by Design philosophy. As such, privacy is deeply integrated into BlueConic, up until the individual profile level.
Using the privacy features within BlueConic, you can make your online channels comply with online privacy laws, such as those enacted in the European Union and other countries which stipulate that any website or other online channel that stores information about a visitor in a personal profile or that adds cookies to a browser must inform the website visitor that it does so and give them the option to opt out of the tracking of personal information and remain anonymous. BlueConics privacy feature gives the visitor complete control over their personal browsing experience. By opting to allow personal data to be tracked and stored, the visitor can optimize their experience because BlueConic can target them with content that is geared toward their interests and which is relevant for them.
Privacy features in BlueConic
BlueConic offers features for privacy and consent management. You can use Objectives to manage consent across the platform. Learn more about using BlueConic Objectives for consent.
Among others the BlueConic privacy features consist of the following:
The Opt in - Opt out interaction. The Opt in - Opt out interaction displays a series of prompts that make it possible for the visitor to select their ideal permission level. The permission level they select affects their browsing experience by making it either less personal or more personal and relevant.
Default privacy settings and profile sharing. In BlueConic you can set the default permission for all website visitors. This is the permission that all visitors have before they have been given the choice to select a different privacy level (if offered). The three levels of online privacy available in BlueConic are:
Permission
Description
Level 0 (opt out)
BlueConic will gather no anonymous or personal information about the visitor.
The result is that the visitor's experience will be impersonal and they will only
be served static content.
Level 1
BlueConic gathers anonymous statistical information that is used to optimize
the visitor's experience on the website.
Level 2
BlueConic will store personal data and preferences. This setting gives the
website visitor the most personal experience.
Permission settings per profile property and interaction type. In BlueConic, it is possible to assign a privacy level to each profile property and interaction. For profile properties, this feature gives the you global control over which properties can be populated with anonymous or personal information for all visitors of the website. In this scenario, a profile property can be assigned a value only if the privacy level selected by a visitor is higher than that of the profile property. For interactions and optimizers, the permission level defines the required permission level needed to trigger the interaction or optimizer. An interaction or optimizer can only be triggered for website visitors who have at least the same permission level as that defined for the interaction or optimizer
Permission methods in the JavaScript API. The BlueConic JavaScript API contains a number of methods that allow you to add, set, and get permission levels for interaction types and profile properties.
Permission methods in the Rest API. The BlueConic REST API contains a number of methods that allow you to set the permission level of a profile. If needed, a customer can split up the profiles per subset of Domains (that contain channels), to have more fine-grained privacy and permission management. For regulation and compliance, a chosen permission level by visitor is stored in a separate database, even when the visitor is opting out. The profile is then removed; the change event is not.
View ArticleBlueConic uses first-party cookies to identify profiles with online behavior. The cookie only contains an identifier. A copy of the profile is in browser-memory for manipulation using JavaScript for the individual visitor. All profile data is persisted server side.
BlueConic checks if first-party cookies are disabled; if they are disabled, BlueConic doesn't store the profile, honoring the user's settings.
BlueConic uses third-party cookies to track a visitor when he or she switches from one (web based) channel to another channel (identity transfer). If we detect that the browser is set to block third-party cookies, we honor this setting and only use a profile per unique channel or hostname.
BlueConic can also detect if a user has used the Do Not Track (DNT) signal in the browser. More information about DNT can be found here. The DNT signal is meant to block third parties from tracking you. Because BlueConic is intendedfor owned channels only, the DNT signal does not apply to BlueConic.
Cookies and ITP
Browser vendors are increasingly adding tracking prevention, for example Apple's ITP, to prevent third parties from tracking visitors to websites.BlueConic and other CDPs are first-party data processors. We do not own the data, you do. We are a subcontractor for you, our customers. Most privacy protection technology is focused on third-party tracking and AdTech, which feels logical as consumers do not expect to be tracked by third parties when visiting a website.
For details on how BlueConic handles this, see our FAQ: BlueConic, cookies, and ITP.
Overview of cookies placed by BlueConic
Name
Description
Domain
Expires
BCSessionID
Unique identifier for the BlueConic profile
first & third
1 year
BCTempID
Temporary unique identifier for the BlueConic profile, removed after BCSessionID is created.
third
10 minutes
AWSELB
Used for elastic load balancing by Amazon Web Services
third
1 hour
BCPermissionLevel*
Opt-in level (PERSONAL|ANONYMOUS|DO_NOT_TRACK)
first
1 year
* Only when using BlueConic Permission Management.
View ArticleBlueConic has a company-wide commitment to your privacy. Our Privacy Policy covers how we collect, use, disclose, transfer, and store your information.
http://www.blueconic.com/privacy-policy/
BlueConic is certified by TRUSTe for two of their programs:
Privacy certification
TRUSTed cloud
More information about both programs can be found here.
We do internal audits of our policies every month. We have appointed a privacy officer and a security officer.
View ArticleThe content of this article is deprecated. Please see Privacy Management in BlueConic instead.
Privacy
Using the privacy features within BlueConic, you can make your online channels comply with online privacy laws, such as those enacted in the European Union and other countries which stipulate that any website or other online channel that stores information about a visitor in a personal profile or that adds cookies to a browser must inform the website visitor that it does so and give them the option to opt out of the tracking of personal information and remain anonymous. BlueConic's privacy feature gives the visitor complete control over their personal browsing experience. By opting to allow personal data to be tracked and stored, the visitor can optimize their experience because BlueConic can target them with content that is geared toward their interests and which is relevant for them.
The BlueConic privacy features consist of the following:
The Opt in - Opt out interaction
The Opt in - Opt out interaction displays a series of prompts that make it possible for the visitor to select their ideal permission level. The permission level they select affects their browsing experience by making it either less personal or more personal and relevant.
Default privacy settings and profile sharing
In BlueConic you can set the default permission for all website visitors. This is the permission that all visitors have before they have been given the choice to select a different privacy level (if offered). The three levels of online privacy available in BlueConic are:
Permission
Description
Level 0 (opt out)
BlueConic will gather no anonymous or personal information about the visitor. The result is that the visitor's experience will be impersonal and they will only be served static content.
Level 1
BlueConic gathers anonymous statistical information that is used to optimize the visitor's experience on the website.
Level 2
BlueConic will store personal data and preferences. This setting gives the website visitor the most personal experience.
Permission settings per profile property and interaction type
In BlueConic, it is possible to assign a privacy level to each profile property and interaction. For profile properties, this feature gives the you global control over which properties can be populated with anonymous or personal information for all visitors of the website. In this scenario, a profile property can be assigned a value only if the privacy level selected by a visitor is higher than that of the profile property. For interactions and optimizers, the permission level defines the required permission level needed to trigger the interaction or optimizer. An interaction or optimizer can only be triggered for website visitors who have at least the same permission level as that defined for the interaction or optimizer. See Profile properties for complete information on working with profile properties.
Permission methods in the JavaScript API
The BlueConic JavaScript API contains a number of methods that allow you to add, set, and get permission levels for interaction types and profile properties.
Permission methods in the Rest API
The BlueConic JavaScript API contains a number of methods that allow you to set the permission level of a profile.
View ArticleThe content of this article is deprecated. Please see Privacy Management in BlueConic instead.
The Cookie Consent by Continuation action is a way to implement permission management.It will display a message to the visitor, informing her that cookies will be used on the website and that continuing to browse the website means acceptance of these cookies. Up to the acceptance,no permissions are granted.
Configuring the Dialogue
To enable the Cookie Consent by Continuation for a website, follow these steps:
Create a new Dialogue.
Open the "Where" tab.
Add the channel where you want the action to appear. This is important, as it allows the action fields to appear!
Open the "Interaction" tab.
Select the plugin "Cookie consent by continuation" in the properties widget.
Save the Dialogue.
Next you edit the content of the Cookie Consent dialogue. The content is split in three parts that mustbe edited separately: the notifier, the lightbox and the footer.
Notifier
This message will be shown the first time the visitor lands on the channel. The message is typically shown as a notice at the top of the page. To display the notifier, open the Notifier tab in the Properties widget and click the [Show Notifier] button.
The notifier will be shown with an edit bar. Click the [Edit] button to edit the contents of the message. By default, the message contains a link to open the permission configuration lightbox ("click here"). This is a special link: you can edit its text, but not the link itself. If you lost the linkandwant to add itto the editor again, click the [Add Link] button.
Lightbox
The lightbox is where the visitor can change the cookie settings.By default this contains an explanation of the setting with a link to the Cookie Policy of the website and a cookie checkbox. Open the Lightbox tab in the Properties widget and click [Show Lightbox] to view the lightbox.
The lightbox is shown with an edit bar. Click the [Edit] button to edit the contents of the lightbox.
The lightbox should contain a cookie checkbox for the visitor to select his preferences. Should the cookie checkbox ever get edited away by accident,itcan be added by clicking [Add Cookie Checkbox].
Footer
The footer isa link that the visitor can use to open the permission settings. This link is optional, and when it is present it is typically embedded among the footer links of a page.
There are four options for the location:
No footer: No footer link will be shown and the [Show Footer] button is greyed out. This is the default.
Bottom left: Show the footer link fixedto the left bottom of the page.
Bottom right: Show the footer link fixed to the right bottom of the page.
Selector: Enter your preferred position on the page for the link, or use the Visual Picker to pick one.When you opt to use a Selector, you also have to indicate whether the HTML code for the link should Replace the existing HTML of the position, or if the code should be appended or prepended to the existing HTML.
View ArticleOverview: GDPR compliance
Marketing teams use BlueConic to manage customer data privacy and consent compliance worldwide. BlueConic supports multiple legislation zones, including the GDPR in Europe. For general information on managing privacy with BlueConic see the Privacy section of our Knowledge Base.
This FAQ covers questions specific to GDPR compliance.
Where can I learn more about the EU General Data Protection Regulation (GDPR)?
For all questions about the regulation, you can visit the official EU GDPR portal to learn more, including an FAQ about the regulation itself: https://www.eugdpr.org/
When did GDPR go into effect?
May 25, 2018
Is BlueConic considered a data processor or a data controller in relation to the profile data stored in the platform on behalf of its customers?
BlueConic is considered to be a data processor in this context.
When were BlueConic’s Consent and Privacy Management capabilities released?
April 2018
Will BlueConic’s Consent & Privacy Management capabilities make my organization compliant?
Not necessarily. You should consult your internal legal/privacy experts to determine which of your marketing objectives require implicit or explicit consent, as well as where and when you need to ask for consent. Once you have this determined, you can use BlueConic’s Dialogues to ask for consent and capture individual rights requests.
DoesBlueConicprovide consulting to its customers about how to be GDPR compliant?
No.BlueConic is not a consulting or lawfirm. We recommend you consult your organization’s legal and/or privacy experts to determine what is required for your specific organization.
Is BlueConic GDPR compliant in relation to the profile data stored in the platform on behalf of its customers?
Yes, all our internal processes are compliant, as well as 3rd parties, like Amazon Web Services.
Managing privacy and consent with Objectives in BlueConic
What is the Objectives object in BlueConic, and how does it relate to consent management for GDPR?
The BlueConic Objectives object lets you define purposes for personal data collection that require explicit or implicit consent. You can easily add Dialogues, Connections, Listeners and other BlueConic objects to Objectives to enable consent management for those objects.
Is it possible to only ask for consent against one overall Objective and remain compliant with GDPR?
This is a question for your internal legal & privacy experts. It depends on what types of data you collect, as well as how many different marketing purposes for which you use it.
Consent management for GDPR
How can BlueConic help me manage consent for personal data collection?
You can use BlueConic Dialogues to request consent from individual customers for the specific purposes associated with your defined Objectives in the platform. Once consent is given or denied at the individual level, that data is stored in the corresponding profile that is persistently stored in BlueConic. As a marketer, BlueConic Dialogues provide you with complete control and flexibility over how and where you ask for consent, so you can make changes as needed without the help of IT or developers. You can view what percentage of your customers has provided consent for each of your objectives at any time. The article Privacy Management in BlueConic helps you get started.
Can I see a demo of how to set up Objectives in BlueConic, as well as Dialogues for requesting consent?
Watch our GDPR and privacy tutorial video to see how to do this in under 5 minutes.
Can I limit the exposure of consent-related Dialogues to only be shown to customers in the EU?
Yes. Based on the IP address of your website visitors, BlueConic can determine the legislation of a user, and only display consent Dialogues to visits with an IP address located in the EU.
What if a customer denies or revokes consent for website tracking behavior? How would BlueConic automatically manage that?
Assuming that ‘website tracking behavior’ is defined as a BlueConic Objective, when a customer denies or revokes consent for that Objective, BlueConic will not execute Dialogues, Listeners, Connections and other related objects for that particular customer’s BlueConic profile.
Can I synchronize customer-level consent data to my external marketing platforms, such as ESP, CRM, retargeting?
Yes. You can use BlueConic partner Connections to sync with your external platforms. When exporting profiles, you can select to transfer only the profiles for customers that have given consent.
What if we are capturing consent in other platforms? Can we integrate consent data captured outside of BlueConic into BlueConic profiles?
Yes. As long as the consent is captured at the individual level and can be mapped to a BlueConic profile identifier, you can use BlueConic connections to synchronize this data. When importing profiles, you can select to only transfer profiles that have given consent.
By using the BlueConic APIs you can maintain the same objectives as that you have ‘purposes’ in the leading system. Using the JavaScript API, the legislation and consented/refused objectives can also be managed for each visitor individually.
By linking the objectives with (global)listeners, connections, trackers and dialogues BlueConic will only execute / show the items for which the visitor has given consent to.
Can I also use BlueConic’s consent management capabilities to manage cookie consent?
Cookies are seen within the GDPR as only one way to create an online identifier. With the GDPR, the focus is on getting consent for a specific purpose, of which cookies are only a part. BlueConic will only set an identifier in a cookie when the visitor has given consent to at minimum one consent, before that no identifiers are stored in cookies.
When does a visitor get a profile?
A visitor only gets a profile:
IF the visitor has legislation “NONE” and the default permission level is 1 or 2, or:
IF the visitor has legislation “GDPR” and one or more (global) listeners, connections or trackers are executed for that visitor. These are only executed:
IF they don’t require consent, or
IF they do require consent and visitor consented to one or more related objectives
A profile is also created if the visitor explicitly selects permission level 1 or 2 (this is used for the (deprecated) cookie consent).
The rules above can be translated to the following table:
Permission level
Legislation
Items open*
Consent given
Gets profile
0
NONE
n/a
n/a
No
1 or 2
NONE
n/a
n/a
Yes
0
GDPR
n/a
No
No
0
GDPR
n/a
Yes
Yes***
1 or 2
GDPR
No
No
No
1 or 2
GDPR
No
Yes
Yes**
1 or 2
GDPR
Yes
No
Yes**
1 or 2
GDPR
Yes
Yes
Yes**
* An item ((global) listener, connection or tracker) is called “open” if it is not part of an
objective that has consent management switched on.
** The “GDPR-profile” gets the default permission level.
*** The “GDPR-profile” gets permission level 2.
What happens with the consent when two profiles merge?
When two profiles merge the privacy settings for the two profiles are automatically merged.
Consented objectives The consented objectives from both profiles are added up and placed into the merged profile.
Refused objectives The refused objectives from both profiles are added up and placed into the merged profile. Refused objectives that also appear in the merged consented objectives list are removed from the refused objectives list.
Privacy legislation The privacy legislation is set to the value of the first rule that matches:
If at least one of the profiles has the value “GDPR”, then use “GDPR” as legislation.
If at least one of the profiles has the value “NONE”, then use “NONE” as legislation.
Otherwise the value for legislation will be left empty (null).
What happens with profile data when a visitor withdraws consent?
By default nothing changes to the profile data when a visitor withdraws consent for one or more objectives. You can change this behavior through a settings on the BlueConic settings > Privacy tab:
Webinar: Consent management for GDPR made simple
By checking the option After visitor withdraws consent for an objective, clear the related profile properties the visitor’s profile will be updated after a visitor withdraws consent. Profile properties that are related to the withdrawn objectives will be cleared, except for profile properties that are related to other objectives that the visitor still consents to.
Profile properties are related to objectives by items (such as listeners and import connections) that are contained by the objective and write data into profile properties.
How can I implement multilingual websites?
See our General privacy FAQ for instructions.
Learn more about privacy and consent compliance with BlueConic
Here are some other resources on the subject of privacy and consent management:
Privacy management in BlueConic
FAQ: Using BlueConic for privacy and consent
GDPR changes to BlueConic
View ArticleIn case your primary audience does not include EU residents, i.e. visitors who are not regulated by GDPR, you may just want to make sure that your channels are compliant with GDPR (or privacy regulations such as CCPA) without gathering EU visitor profiles at all. The following easy-to-implement strategy might be just for you:
Set up a listener that will only create a profile for visitors from outside of the EU. Visitors from the EU will not get a profile.
This strategy saves you from having to define objectives and setting up consent dialogues for EU visitors. If needed, you can still set these up and ask EU visitors for consent to your objectives. Only after consent has been given, a profile will be created for the EU visitor.
If you mainly serve international customers from the U.S. and EU, you can follow another strategy.
Only create profiles for non-EU visitors
Take the following steps to make sure that by default only non-EU visitors will get a profile:
Install the plugin “European visitors: only profile after consent”:
Open BlueConic Settings > Plugins
Click Add plugin
Search for “Euro”
Click Install plugin
Create a listener of type “European visitors: only profile after consent”:
Open the Listeners tab
Click Add listener
Search for “Euro”
Click the listener European visitors: only profile after consent
Enter “European visitors: only profile after consent” as name
Make sure that returning EU visitors don’t get a profile. Returning EU visitors will be ‘unlinked’ from their existing pre-GDPR profiles (i.e. from before May 25, 2018), while the pre-GDPR profile will not be deleted from BlueConic’s database.
Check the Also block European visitors that already had a profile
Make sure existing pre-GDPR profiles of returning EU visitors are deleted when they return to your channels:
Check the Permanently delete existing European profiles (when they enter your channel)
Optional: Prevent some pre-GDPR profiles from being permanently deleted (they will get ‘unlinked’ when they re-enter the channel). For example, registered customers.
Select one or more segments that contain profiles that should not be deleted.
Activate the listener:
Turn the listener on
Click Save
GDPR changes to BlueConic
Verify the default permission level to make sure profiles are created for non-EU visitors:
Open BlueConic settings > Privacy
Select Level 2 (personal)
Click Save
Set up consent for EU visitors
The strategy above will have BlueConic only collect profiles for non-EU visitors. You can optionally expand on this by creating objectives and dialogues that allow EU visitors to give consent to those objectives. Only after consenting to at least one of the objectives the EU visitor will get a profile. Read I serve international customers from the U.S. and EU on how to set this up.
Related topics
Privacy Management in BlueConic
FAQ: Consent & Privacy Management for GDPR
View ArticleWhether your primary audience consists of EU residents, or your audience is international including EU residents, you will want to engage them in a way that complies with GDPR (or other privacy regulations such as CCPA). Follow the instructions below to do this with BlueConic:
Define your objectives
Retrieve consent
Set up the visitor's Privacy Center
However, if you mainly serve visitors from outside the EU, you can follow another strategy.
Define your objectives
BlueConic’s objectives play the central role in the whole setup:
Visitors have to give consent to the objectives you offer them
You use the objectives to limit the execution of an item
You can define as many objectives as you want on the Objectives tab:
GDPR changes to BlueConic
Add a new objective:
Click Add objective
Enter a name for the objective.
Check the Enabled box to enable consent management of the objective for GDPR purposes. This means visitors will have to give consent to the objective before items in the objective can access the profile.
Verify the Objective ID, as you cannot change this once the objective has been saved.
Enter a descriptive Consent title, which is the title the visitor will see when consenting to the objective.
Enter a Consent description, which should describe the consent given in easy to understand terms to the visitor.
Place items in the objective by selecting them. See also: the impact of placing an item in an objective.
Dialogues and objectives
When creating a segment on the Segment tab or on the Who tab of a dialogue, you can make use of three profile properties that were introduced specifically for the GDPR:
Privacy legislation Contains the value “GDPR” for people coming from one of the countries that the GDPR legislation applies to. Otherwise it contains the value “NONE”.
Consented objectives Contains the objectives that the visitor consented to.
Refused objectives Contains the objectives that the visitor refused.
Use these profile properties to target your dialogue at a specific audience. In the screenshot below the dialogue is shown to visitors coming from the GDPR zone that have not given an answer to the four listed objectives.
Retrieve consent
Once you have created the objectives, you can now set up the dialogues to ask for consent for the objectives. There are several ways of doing this, so we provided three examples to illustrate. The first two examples show how to make BlueConic display a form to the visitor asking for consent. The third example shows what to do when you already have created your own form asking for consent, in which case you use a BlueConic listener to place the answer in the visitor’s profile.
Example 1: Retrieve consent with a BlueConic form using the “Manage consent” toolbar component
Example 2: Retrieve consent with a BlueConic form using the “Forms” toolbar component
Example 3: Retrieve consent with your own form using consents and refusals listener
Set up the visitor’s Privacy Center
A “Privacy Center” is an area on your channel where the visitor of your channel can manage personal privacy settings. BlueConic offers features to easily set up the following items for the privacy center:
Overview of consented / refused objectives
Profile overview (This overview may contain personally identifiable information. It is recommended to only show personally identifiable information to its rightful owner, e.g. to visitors who are logged in)
Download profile option (Similar to the Profile overview, please make sure that personal identifiable information is only shown to its rightful owner)
Delete profile option
Contact form
Read how to set up the visitor's Privacy Center for the details.
Related topics
Privacy Management in BlueConic
FAQ: Consent & Privacy Management for GDPR
View Articlehow to retrieve consent when serving international customers from the U.S. and EU
Many privacy regulations, including GDPR and CCPA, specify that individuals be able to manage their consent when visiting sites and channels. This example explicitly asks for consent to a number of objectives in a lightbox shown to non-EU visitors that have not provided consent yet. The “ Manage consent ” component is purely focused on showing a list of objectives to the visitor. Take the following steps to use the “Manage consent” toolbar component:
Click Add dialogue to create a new dialogue.
On the Who tab, define a Dialogue specific segment as shown below:
On the What tab, Edit the contents of the lightbox and open the Insert object menu and select Privacy management components.
An overlay appears; click Manage consent:
The contents of the overlay changes. Use the Search or the Add multiple objectives option to select the objectives you want to show to the visitor:
Click the Settings tab to manage the appearance of the objectives, set the text for the submit button and define what should happen after the visitor presses the Submit button:
This is an example of .
View ArticleWhat GDPR means for marketers and for CDPs
The BlueConic customer data platform can help you manage marketing objectives for privacy and consent, such as compliance with privacy regulations including GDPR or CCPA.
This example does not ask for explicit consent, but instead assigns implicit consent when a customer or visitor volunteers information. Be sure to check with your legal team whether implicit consent is compliant with the data policies and regulations in your specific case. Set consent for one or more objectives when a visitor or customer submits the form using the “Forms” toolbar component. In the example of the above screenshot:
The email address input field and sign up button are placed using the BlueConic forms toolbar component.
The consent for the objective “Daily newsletter” should be set if the visitor clicks the “Sign up” button.
Take the following steps to set consent for an objective if a visitor submits a BlueConic form:
Open the dialogue containing the form.
Setup / edit the form in the dialogue.
Click the Submit settings
Click the Add action dropdown button and select Consent / refuse objective
Select the objective(s) for which the consent must be set when the visitor submits the form:
This is an example of how to retrieve consent when serving international customers from the U.S. and EU.
See also
Privacy Management in BlueConic
Blog: CCPA: Understanding the California Consumer Privacy Act
Webinar:
View ArticleIf you already have a non-BlueConic form on your website and want to set consents or refusals for objectives depending on the answers visitors gave, use the Privacy: Consents and Refusals listener.
Adding a new Privacy: Consents and Refusals listener
ClickListenersin the navigation bar.
ClickAdd Listener.
A pop-up window appears. Check theShow allbox. Enter "privacy" in the search bar. ClickPrivacy: Consents and Refusals listener.
The listener page opens. You can expand or collapse metadata fields (favorite, labels, and description) by clicking the gray+or.
Configuring the Listener
Next, you need to configure rules for the listener. Below is an example of what a configuration could look like:
how to retrieve consent when serving international customers from the U.S. and EU
The example shows a number of typical use cases that you can implement with the listener:
Checkbox is checked / unchecked Rule 1 and 2 of the example show the configuration for My Checkbox A. The objective is consented if the checkbox is checked; the objective is refused if the checkbox is not checked. This will only be registered when the surrounding form is submitted.
Button is clicked With rule 3 of the example the visitor will consent to the objective after clicking My Button B. Clicking that button also has to trigger the submitting of the surrounding form.
Input field is filled With rule 4 of the example the consent for an objective is set if the visitor has entered any value into My Input Field C and its wrapping form is submitted.
Radiogroup / dropdown has a specific value Rule 5 and 6 of the example both handle Radiogroup / Dropdown D. You can check for any value that a radiogroup / dropdown returns and set the consent / refusal for the objective. In this example the consent is set for the value “YES” and a refusal is set for the value “NO”.
Hyperlink is clicked Rule 7 of the example will set the consent for My Objective if the visitor clicks My Hyperlink E. Note that you have to enter the selector of the hyperlink twice, as the hyperlink will not be part of submitting a form.
This is an example of .
View ArticleMany privacy regulations, including GDPR and CCPA, have provisions to let customers and visitors to your channels manage their privacy and consent. A “Privacy Center” is an area on your channel where customers and visitors can manage their personal privacy settings. BlueConic offers features to easily set up the following items for the privacy center:
Overview of consented / refused objectives
Profile overview (This overview may contain personally identifiable information. It is recommended to only show personally identifiable information to its rightful owner, e.g. to visitors who are logged in.)
Download profile option (Similar to the Profile overview, please make sure that personally identifiable information is shown only to its rightful owner.)
Delete profile option
Contact form
Jump start your set up with dialogue examples
BlueConic provides loadable examples for the “Content” and “Lightbox” dialogue types. These examples use BlueConic elements that will be described in the sections below. The examples allow you to quickly set up the framework of your Privacy Center. After using the examples it is best to check with your legal team whether the settings and configuration of the individual BlueConic elements are compliant with data policies and regulations of your organization.
To make use of a loadable example, take the following steps:
Click Add dialogue to create a new dialogue of type ‘Content’ or ‘Lightbox’. This dialogue will contain the Privacy Center.
Open the What tab of the dialogue.
In the right sidebar, click Load examples. Note that loading an example will erase the existing content of the dialogue.
A lightbox opens. Select Privacy: Settings with data overview if you want a Privacy Center with a profile overview. It’s recommended to only use this on pages that can only be accessed after the visitor has logged in. Alternatively, select Privacy: Settings excl. data overview if you want a Privacy Center without a profile overview.
The dialogue now contains a set of elements that together form the Privacy Center:
Open the settings of the Contact form element to enter the email address that should receive the messages that visitors submit.
Also open the settings of the other elements to fine tune for your situation.
Privacy management components
The sections below describe each element that are available via the “Privacy management components” toolbar item:
Article: CCPA Understanding the California Consumer Privacy Act
Manage consent
Link to privacy settings
Contact form
Profile overview table
Download profile
Delete profile
Element: Manage consent
The “Manage consent” element will show the visitor a list of objectives. The visitor can consent or refuse to each of the objectives.
When you open the element in BlueConic you will see two tabs:
Objectives Contains the list of objectives shown to the visitor
Settings Settings for the objectives list
Using the “Search” element and/or the “Add multiple objectives” link you can add as many objectives as you need. Hovering over an objective will highlight the line:
The following options are present (from left to right):
On the left a ‘drag handle’ appears that allows you to re-order the chosen objectives.
Clicking the icon to the right of the objective name will open a lightbox that allows you to enter a custom title and description for the objective. The custom title and description will only be used for this variant of this dialogue.
Clicking the ‘x’ icon will remove the objective from this list.
The Settings tab of the “Manage consent” element:
The available options:
Template This option will change the look & feel of the shown objectives. Click the “pencil icon” to the right of the name to edit the selected template. Click Select other to select another template from the list of existing templates; at the bottom of that lightbox there is an option to create a new template.
Submit text The text shown on the button that will submit the visitor’s choices.
Refuse text The text shown on the refuse button (this button is not used in all templates).
Filter Select this option to remove the objectives from the list that the visitor already has given consent to.
Actions Select the actions that must be executed after the visitor has clicked the Submit / Refuse button. By default the “Show text” option is already added to the list of actions. Click the “Add action” button to add other actions that also must be executed. Options (not all options are available in every situation) are:
Close overlay to close a lightbox, toaster, slide-out or notification bar.
Show inline text
Throw event to trigger a new interaction
Execute JavaScript
Refresh page to load new interactions
Redirect to a URL
Set / add value into profile property
Element: Profile overview table
The “Profile overview table” will show the visitor a table in which values for profile properties in his or her profile are shown. It’s recommended to only use this element on pages for which the visitor had to log in to make sure that the information is only shown to the person that is the rightful ‘owner’ of the profile.
When you open the element in BlueConic you will see two tabs:
Profile properties Contains the list of profile properties shown in the table
Settings Settings for the table
Add as many profile properties as you need using the “Search” field or by clicking the Add multiple profile properties link. Hovering over a profile property will highlight the line:
The following options are present (from left to right):
On the left a ‘drag handle’ appears that allows you to re-order the chosen profile properties.
Clicking the black text on the right allows you change the name of the profile property as it will be displayed to the visitor. This value will only be used in the table for this variant of this dialogue.
Clicking the pop-out icon to the right of the editable display name will open a popup that allows you to enter a custom name and description for the profile property. The custom name and description will only be used for this variant of this dialogue.
Clicking the ‘x’ icon will remove the profile property from this list.
The Settings tab of the “Profile overview table” element:
The available options:
Info column Check this box to add a column to the table that shows the “description” text of each profile property.
No value Check this box to hide the profile properties that don’t have a value for the visitor.
Properties Header text for the column showing the profile properties name.
Descriptions This field is only shown if the box Info column is checked. This field contains the header text for the descriptions column. The default description is entered at the profile property itself in the Description field of the meta data of the profile property.
Values Title text for the column that shows the value of the profile property for the profile of the visitor.
Add download Check this box to show an additional button that allows the visitor to download the contents of the table. Once checked you can enter the text for the button.
Note: This button does the same thing as the separate “Download profile” element, but using this option saves you from entering all the profile properties twice.
Element: Download profile
Using this element will show a button to the visitor. If the visitor clicks the button, a JSON file will be sent to the visitor that contains (parts of) the visitor’s profile.
Note: The profile overview table can automatically display a button that does the same thing if you check the box Add a download button in that element. This saves you from entering all profile properties twice.
When you open the element in BlueConic you will see two tabs:
Profile properties List of profile properties that will be present in the JSON file
Settings Settings for the JSON file
The profile properties tab works identical to the profile properties tab of the “Profile overview table” element that is described in the previous section.
The Settings tab:
The available options:
Button text Text on the download button that the visitor will see.
Info column Check this box to include the description of the profile properties in the downloaded profile.
No value Check this box to hide profile properties that have no value for that visitor from the downloaded profile.
Element: Delete profile
The Delete profile element will show a button to the visitor to delete his profile. If the visitor clicks the button, the profile of that visitor will be immediately deleted. The page will also reload after the button has been clicked and the visitor will be treated as a new visitor that pays the first visit to your channel.
Settings of the “Delete profile” element:
The available options include:
Button text The text on the button
Checkbox Check this box if you want to add an extra safeguard to the delete process. If this option is enabled a checkbox plus text (as entered in the input field of this option) is shown to the visitor. The delete button will be disabled by default and only becomes enabled after the visitor has checked the checkbox.
Element: Contact form
The “Contact form” element adds a contact form to your dialogue. The visitor can use this form to ask any question and can be used for the rectification requests.
When you open the element in BlueConic you will see two tabs:
Website text The texts that are shown to the visitors
Email settings Settings needed for submitting the email
The Website text tab of the “Contact form” element:
All entered texts are used when displaying the form to the visitor.
The Email settings tab of the “Contact form” element:
The available options:
Recipient Enter the recipient for this email; this will be the person that is responsible for handling privacy related questions. It’s also useful that the recipient has a login to BlueConic, so he/she can see the full details of the profile when following the link to the profile.
Subject The subject of the email that will be sent to your company.
Email body You can create your own formatting of the email body, using three ‘parameters’ that will be replaced with the values that the visitor entered into the form:
{email} Email address that the visitor entered
{message} The message that the visitor entered
{profileLink} This is a direct link to the profile of the visitor; following this link will open the profile on the Profiles tab in BlueConic
Element: Link to privacy settings
This element will show a hyperlink to the visitor; the visitor can then use this link to activate the dialogue that contains the privacy settings center of the visitor. This is particularly useful when your privacy settings center dialogue is contained in a lightbox dialogue.
When the visitor clicks the link, it will trigger the event “Privacy management - Open privacy settings”. Select this event on the When tab of the lightbox dialogue that contains the privacy settings center.
There is only one setting to be configured when selecting this element: the text of the hyperlink that the element will show to the visitor:
Setting up a visitor's Privacy Center is part of serving international customers for US and EU.
Related topics
Here are some other resources on the subject of privacy management:
Privacy Management in BlueConic
FAQ: Consent & Privacy Management for GDPR
GDPR changes to BlueConic
Webinar: Consent Management for GDPR Made Simple
View ArticleBlueConic gives you maximum flexibility to comply with data policies and regulations in your specific case when serving only domestic (non-GDPR) or international customers. Several visible features like objectives, profile properties and privacy management components are there to help you in setting up your channel.
This section describes less visible or obvious parts of BlueConic where the customer data platform supports new features for consent management for GDPR.
The BlueConic APIs
The existing BlueConic APIs have been extended to allow you to be fully GDPR compliant even when you’re not using BlueConic as your Consent Management System.
The client-side JavaScript API
All changes to the API have been added to the JavaScript Frontend API documentation page. In the menu on the right-hand side of that page you can select:
“Profile Methods” The following methods have been added:
getPrivacyLegislation()
setPrivacyLegislation()
getConsentedObjectives()
addConsentedObjective()
setConsentedObjectives()
getRefusedObjectives()
addRefusedObjective()
setRefusedObjectives()
“Objectives Methods” This is a fully new section
getId()
getTitle()
getDescription()
The REST API
All changes to the BlueConic API have been added to the REST API documentation page. In the menu on the right-hand side of that page you can select:
“Profile methods” The sub section “Update or create multiple profiles at once (bulk)” has been updated for the new “objectiveIds” querystring parameter.
“Objectives methods” This is a fully new section.
The EventLog REST API
The EventLog is a database that contains all privacy-related moments of a profile:
When was the profile created / deleted
When was the privacy level changed
When was consent given / refused for an objective
To gain access to these important moments you can use the REST API. Select the “Profile Event methods” in the menu on the right-hand side of the REST API documentation page.
The Profiles tab
When viewing a profile on the Profiles tab there is now a new option available in the left menu: “Profile privacy management.”
Click Profile privacy management to show the current Privacy Settings for the current profile. Only if the legislation is set to “GDPR” the Objectives section will be shown.
The “Event log” section shows a table with all the privacy-related events for this profile in your BlueConic customer data platform.
The Simulator
The BlueConic simulator has been updated so you can easily test what a channel looks like to a visitor with certain privacy settings, such as those created to comply with GDPR.
Take the following three steps to see (and change) the privacy settings:
Click Show full profile in the left side-bar of the Simulator. A lightbox opens.
The bottom bar of the lightbox displays a summary of the privacy settings of the profile that is being used in the simulator:
Click the blue link after Privacy settings to make a smaller lightbox appear that allows you to change the privacy settings for the profile that is used in the simulator:
View ArticleAs a customer data platform (CDP), BlueConic works with the data of individuals, and sometimes this is personal data. The introduction of privacy legislations such as the European General Data Protection Regulation (GDPR) and CCPA in California means that companies need to pay close attention to data that is being stored. Luckily BlueConic comes with tools that help you set up a system to help your customers and visitors manage their own privacy.
BlueConic helps you comply with data privacy laws worldwide by supporting multiple privacy legislation zones, including GDPR in Europe, CCPA in California, PIPEDA in Canada, SB220 for the state of Nevada, and potential NYPA legislation for New York State. See Managing privacy for multiple legislation zones for details.
Always check with your legal team to see if you are compliant with data policies and regulations in your specific case.
Get started
Pick the situation that matches you best:
My primary audience consists of EU residents
My audience is international, including EU residents
My primary audience does not include EU residents
Related topics
Here are some other resources on the subject of privacy management:
FAQ: Consent & Privacy Management for GDPR
GDPR changes to BlueConic
Webinar: Consent Management for GDPR Made Simple
Blog: CCPA Understanding the California Consumer Privacy Act
Implementing Privacy Management for developers
View ArticleBlueConic can be set up to let your customers and visitors manage their own privacy. This article details how to share privacy consent information from BlueConic to another system and how to activate it. For example, this way you can have BlueConic prevent a tag manager from serving tags to customers or visitors whose consent is needed first. And, alternatively, you can green light the serving of tags to customers or visitors whose consent is known.
This example uses Google Tag Manager (GTM), GDPR, and the Facebook Pixel, but the general idea works similarly for other systems, regulations such as CCPA, and tags:
Collect customer consent information in BlueConic.
Create one or more customer Segments of visitors with similar consent.
Send the segments to the other system.
Activate the segments in the other system.
Collect consent information in BlueConic
Start off by setting up privacy management in BlueConic. This will give you a clear picture of the Objectives and Consents you have at your disposal. For example, you could end up with Objectives like this:
send Segments to GTM
Let's focus on the objective "Web Retargeting" specifically. We would like to use this Objective to capture consent for being retargeted on web channels. And based on this information we want to regulate whether or not retargeting scripts, e.g. the Facebook Pixel tag, are added to the page.
Create Segments of visitors with similar consent
With the Objectives set up, we now create a Segment in BlueConic to define customers that we want to prevent from getting the Facebook Pixel tag served.
We're about to set up a Segment to prevent serving, as a precaution. This means that tags will be served unless BlueConic prevents it. If, for whatever reason, consent information never reaches the tag manager, tags will still be served by default (since nothing is preventing it).
For our purpose we create a Segment "Consent required but not given or refused: Web Retargeting" as below:
This Segment contains customers that are in the privacy legislation GDPR and that either didn't consent yet, or that have actively refused consent, combined with all customers that actively refused consent with respect to the Objective "Web Retargeting." These are the customers we want to preventfrom getting the Facebook Pixel tag served.
Send the Segments to the other system
Now that we have a Segment in BlueConic, we turn our focus to sending this Segment to the other system, in our example Google Tag Manager. Start by making sure BlueConic can using the Google Tag Manager Connection.
Map associated segments in the export goal:
Select Associated segments from the map type pulldown menu.
Click All associated segments. A pop-up opens.
Activate Only selected segments to make a custom selection of Segments.
Select the Segment we created earlier:"Consent required but not given or refused: Web Retargeting".
Enter "bc_no_consent_retargeting" as replacement value for the Segment name. This unique string of characters allows us to safely use "contains" in a GTM trigger.
Don't forget to activate and save the export goal and the Connection!
Activate the Segments in the other system
With the BlueConic Connection active, our Segment should now be communicated to Google Tag Manager. Verify this in GTM by entering preview mode and opening your website. UnderVariables you should see an event namedBlueConic. Among the information sent by this event is the variable "BcSegments." Depending on whether or not you are considered to be part of the segment, this should contain the replacement segment value "bc_no_consent_retargeting":
Events are listed under Summary in the order they occurred:
The "Page View" event occurred first.
"DOM Ready" event was next.
Then the "BlueConic" event was fired by the GTM Connection we created.
Finally "Window Loaded" is the last event registered.
This order is very important, as it determines WHEN Segment information is available. The "BcSegments" variable will not have a value until after the BlueConic event has occurred. Verify this by clicking one of the other events. Before theBlueConic event the variable is undefined, after the event it has a value.
We need to take this into account when defining triggers in GTM. Since "Window loaded" is the first (native) GTM event where the "BcSegments" variable could have a value, we have to create a trigger based off the "Page View - Window Loaded" event. Have the trigger fire when "BcSegments" does not contain "bc_no_consent_retargeting." In other words: this trigger will fire when the window is loaded, unless BlueConic signals to prevent it.
Now you have a trigger that you can use to fire tags in GTM! Define your tag as usual, and add "Consent given or not needed - Web Retargeting" as a firing trigger.
Done!
From now on, the Facebook Pixel will only be added to a page when your customers gave consent or when consent is not needed. You can verify this in preview mode:
Under Summary, you can see whether or not the Facebook Pixel fired on the page.
Remember to alwaysconsult your organization's legal and/or privacy experts to determine what is required for your specific organization.
View ArticleBlueConic helps you comply with customer data privacy regulations worldwide. With multiple privacy legislation zones (i.e. GDPR covering Europe, CCPA in California, PIPEDA in Canada, SB220 for the state of Nevada, and NYPA potential legislation for New York State), compliance gets complicated quickly.
Managing multiple data privacy zones including GDPR, CCPA, PIPEDA, SB220, and NYPA
You can use BlueConic Objectives to manage customer and visitor privacy and marketing consent across multiple privacy legislation zones. Objectives determine how and whether an individual profile has given consent for the action or content that Objective governs. Use Objectives to ensure that content is shown only to profiles that have consented to the objective or are not covered by the relevant privacy legislation.
Using Privacy Settings for multiple legislation zones
Use the Privacy settings page in BlueConic to select the privacy legislation zones you want to support.
Privacy settings
Using Objectives to manage privacy and marketing consent
You can attach Objectives to content or actions in BlueConic, to ensure that the pool of profiles exposed to these objects includes only those profiles that have given the proper consent. For example, if you use a BlueConic Dialogue to display marketing content, you may need to obtain people's consent. You could add a privacy Objective to a BlueConic Dialogue to ensure that your marketing content is presented only to profiles that have given prior consent for marketing materials.
Consent status for BlueConic Objectives
Depending on a profile's consent status, BlueConic will include or not include profiles when matching user profiles to your consent objectives. For example, you can specify that a content dialogue should be shown only to profiles with a certain privacy legislation setting.
When setting conditions for Objectives, you can specify the following consent categories for including profiles in an objective:
Consented: Include all profiles that consented to the objectives. In the case of a content Dialogue, this means show content to profiles that have explicitly consented to the selected Objective.
Not needed or consented: Include all profiles that don't need to consent (i.e. the legislation is set to "None"), and also profiles that consented to the objectives. In the case of a content Dialogue, BlueConic would show content to all profiles that have explicitly consented to the selected objectives and to profiles from a legislation zone that isn't covered by the selected objective.
Refused: Include all customer profiles that refused the privacy objectives.
Unknown: Include all customer profiles that need to consent to marketing objectives (i.e. legislation is not set to "None"), but have not yet consented or refused the objectives.
Refused or unknown: Include all customer profiles that did not consent to the objectives. These profiles fall into either the Refused or Unknown category.
See Objectives for more information on using BlueConic Objectives for privacy and consent management. See for more information on supported privacy legislation zones.
View ArticleOverview: Privacy and consent with BlueConic
Does BlueConic offer capabilities to manage privacy and consent?
Yes, BlueConic helps you comply with data privacy regulations worldwide by supporting multiple legislation zones, including:
GDPR for Europe
CCPA in California
PIPEDA in Canada
SB220 for the state of Nevada
NYPA potential legislation for New York State
Webinar: Will CCPA change your marketing? Understanding the impact of privacy regulation
Learn more about managing privacy for multiple legislation zones with BlueConic.
How can I use BlueConic to manage compliance with GDPR?
See our FAQ on using BlueConic for GDPR privacy compliance. See our video on what GDPR means for marketers and CDPs.
Where can I learn more about CCPA for privacy compliance in California?
See our FAQ on using BlueConic for CCPA compliance and watch our webinar on understanding the impact of the CCPA privacy regulation on your marketing.
Is BlueConic considered a data processor or a data controller in relation to the profile data stored in the platform on behalf of its customers?
BlueConic is considered to be a data processor in this context.
Will BlueConic’s Consent and Privacy Management capabilities make my organization compliant?
Not necessarily. You should consult your internal legal and privacy experts to determine which of your marketing objectives require implicit or explicit consent, as well as where and when you need to ask for consent. Once you have this determined, you can use BlueConic’s Dialogues to ask for consent and capture individual rights requests.
Does BlueConic provide consulting to its customers about how to comply with privacy legislations?
No.BlueConic is not a consulting or law firm. We recommend you consult your organization’s legal and/or privacy experts to determine what is required for your specific organization.
Is BlueConic compliant in relation to the profile data stored in the platform on behalf of its customers?
Yes, all our internal processes are compliant, as well as thirdparties, like Amazon Web Services.
Managing privacy and consent with Objectives in BlueConic
What is the Objectives object in BlueConic, and how does it relate to consent management?
In BlueConic, you use Objectives to define why you're collecting personal data, for puroses that require explicit or implicit consent (to send email to someone or to collect phone numbers, for example). You can easily add Dialogues, Connections, Listeners, and other BlueConic objects to Objectives to enable consent management for those objects.
Is it possible to only ask for consent against one overall Objective and remain compliant with privacy legislations?
This is a question for your internal legal and privacy experts. It depends on what types of data you collect, as well as how many different marketing purposes for which you use it.
Consent management
How can BlueConic help me manage consent for personal data collection?
You can use BlueConic Dialogues to request consent from individual customers for the specific purposes associated with your defined Objectives in the platform. Once consent is given or denied at the individual level, that data is stored in the corresponding profile that is persistently stored in BlueConic. As a marketer, BlueConic Dialogues provide you with complete control and flexibility over how and where you ask for consent, so you can make changes as needed without the help of IT or developers. You can view what percentage of your customers has provided consent for each of your objectives at any time. The article Privacy Management in BlueConic helps you get started.
What if a customer denies or revokes consent for website tracking behavior? How would BlueConic automatically manage that?
Assuming that ‘website tracking behavior’ is defined as a BlueConic Objective, when a customer denies or revokes consent for that Objective, BlueConic will not execute Dialogues, Listeners, Connections and other related objects for that particular customer’s BlueConic profile.
Can I synchronize customer-level consent data to my external marketing platforms, such as ESP, CRM, retargeting?
Yes. You can use BlueConic partner Connections to sync with your external platforms. When exporting profiles, you can select to transfer only the profiles for customers that have given consent.
What if we are capturing consent in other platforms? Can we integrate consent data captured outside of BlueConic into BlueConic profiles?
Yes. As long as the consent is captured at the individual level and can be mapped to a BlueConic profile identifier, you can use BlueConic connections to synchronize this data. When importing profiles, you can select to only transfer profiles that have given consent.
By using the BlueConic APIs you can maintain the same objectives as that you have ‘purposes’ in the leading system. Using the JavaScript API, the legislation and consented/refused objectives can also be managed for each visitor individually.
By linking the objectives with (global)listeners, connections, trackers and dialogues BlueConic will only execute / show the items for which the visitor has given consent to.
Can I also use BlueConic’s consent management capabilities to manage cookie consent?
Some privacy legislations, view cookies as only one way to create an online identifier. With GDPR, for example, the focus is on getting consent for a specific purpose, of which cookies are only a part. BlueConic will only set an identifier in a cookie when the visitor has given consent to at minimum one consent, before that no identifiers are stored in cookies.
Can I disable consent management for one plugin?
Yes, by adding the following line to the plugin.xml you disable consent management for one plugin:
<profileindependent>true</profileindependent>
It’s advised to only add this for plugins that don’t require access to the profile. Items based on a plugin for which the consent management has been disabled can still be placed into all objectives. In this situation BlueConic will not limit the execution of the item based on the objectives with consent management switched on.
Can I pass on consent when using an External Tracker?
Yes, for each objective that must be added to the consented objectives for the visitor that follows the tracker, you can add the ID of the objective to the querystring of the tracker. An example where consent is added for objectives with the ID ‘x’ and ‘y’:
https://aaa.blueconic.com/s/4?consented_objective=x&consented_objective=y
How does BlueConic keep track of consent without a profile?
If BlueConic is set up in a way that the visitor does not get a profile when landing on a website, then a profile is only created after the visitor gave consent for at least one objective. If the visitor only refuses objectives, no profile is created and the information about the refused objectives is stored in the ‘local storage’ of the browser.
You don’t have to do anything special to target these visitors without a profile that refused one or more objectives.
What happens with profile data when a visitor withdraws consent?
By default nothing changes to the profile data when a visitor withdraws consent for one or more objectives. You can change this behavior through a settings on theBlueConic settings > Privacytab:
By checking the option After visitor withdraws consent for an objective, clear the related profile properties the visitor’s profile will be updated after a visitor withdraws consent. Profile properties that are related to the withdrawn objectives will be cleared, except for profile properties that are related to other objectives that the visitor still consents to.
Profile properties are related to objectives by items (such as listeners and import connections) that are contained by the objective and write data into profile properties.
Privacy management
Can BlueConic help me manage individual rights requests, such as requests to access data, rectify data, and delete data?
Yes. You can use BlueConic’s new privacy management capabilities to create a customer-facing privacy center using BlueConic Dialogues. Customers can make these requests in the privacy center, so you can respond in a timely manner. The article Privacy Management in BlueConic will help you get started.
How do I implement multilingual websites?
If you want to set up the privacy management for multiple languages, then you can use the option to enter custom text for each objective and profile property. This way you can enter language-specific names and descriptions for all your objectives and profile properties (as used in the profile overview table).
To enter language-specific text for objectives, click the icon to the right of each of the chosen objective:
To enter language-specific text for profile properties, click the icon to the right of each of the chosen profile property:
Learn more: Using BlueConic for privacy compliance
Here are some other resources on the subject of privacy and management:
Privacy management in BlueConic
Managing privacy for multiple legislation zones (GDPR, CCPA, etc.)
GDPR compliance:
GDPR changes to BlueConic
FAQ: GDPR compliance with BlueConic
Webinar: Consent management for GDPR made simple
CCPA compliance:
FAQ: CCPA compliance with BlueConic
View ArticleMarketing teams use BlueConic to manage customer data privacy and consent compliance worldwide. You can use BlueConic to manage privacy and consent across multiple legislation zones, including GDPR and CCPA.
This tutorial teaches you how to use BlueConic to set up privacy consent management for CCPA compliance.
Watch as our customer success manager walks you through the process of setting up consent management for CCPA (detailed directions below):
California Consumer Privacy Act, Explained
Setting up consent management for CCPA involves these four steps:
Enable CCPA consent management in BlueConic
Create an Objective that describes your marketing objectives or purposes
Use dialogues to request consent
Employ CCPA objectives in your marketing campaigns
Note:BlueConic is not a consulting or lawfirm. This document does not constitute legal advice.We recommend you consult your organization’s legal and/or privacy experts to determine what is required for your specific organization.
Use BlueConic privacy settings for CCPA compliance
In the BlueConic menu bar, choose Settings > Privacy.
In the Privacy window, select US - California (CCPA).
Note: If you already have consent management for GDPR set up, leave that box checked.
You can also choose to clean up or remove profile properties when visitors withdraw consent for a certain objective.
Save your changes.
Create marketing objectives to manage consent for CCPA
In BlueConic, objectives outline your reasons for collecting marketing data for your visitors and customers. Privacy legislations such as CCPA and GDPR require that you tell customers why you are collecting data and how they can opt out or in. In BlueConic, you use Objectives to manage and communicate these reasons to customers.
Choose More > Objectives from the BlueConic menu bar.
In the Objectives window, click Add Objective.
Provide a name that describes your marketing objective inside BlueConic, for example, Create personalized browsing experience.
Your visitors and customers will not see this name.
For the Consent management check box, select Enabled to turn this objective on.
Enter a Consent title that explains your marketing purpose to your visitors and customers, for example Track website browsing behavior to receive a personalized browsing experience.
Your customers will see this title when you ask for their marketing consent.
(Optional) Add description text with details about your purposes for the customer data.
In the Contained items section, select the BlueConic objects associated with this data collection, such as connections or listeners that gather the data.
Here's where you define where the data is coming from or going to, so BlueConic knows whether or not to store the data based on your customers' consent. In our example, we have an SFTP Connection, a Keyword Interest Ranking listener, and a Behavior listener that collect customer data.
Save your settings.
Keep in mind that the items contained within an objective -- the transfer of customer data via an SFTP Connection, or collecting customer interests via a BlueConic listener -- are only executed if the customer consents to that objective. If the customer does not consent, the data for that objective won't be collected.
Request consent from customers using BlueConic dialogues
Now that you've created objectives, next you request your customers' consent using BlueConic dialogues. BlueConic provides privacy consent dialogues you can customize for CCPA consent management.
Open the Dialogues window and click Add dialogue.
Select the Lightbox dialogue from the Add dialogue window.
Give the lightbox dialogue a name, for example, CCPA consent.
In the dialogue's Who tab, select the condition for who sees this dialogue by selecting Condition > Objectives. Then select the consent objective you created earlier: Create personalized browsing experience.
On the What tab, click Place on this page to place the dialogue, and load examples in the right-hand panel Properties > Styling settings area, choose Load examples.
Select the Privacy consent via buttons example.
Click Edit to customize the default language that appears in the lightbox.
Hover over the template's buttons and click the Edit icon and click Edit. In the Privacy management - Manage consent window, open the Settings tab, where you can customize the button text and adjust styling and interaction settings.
In the Privacy management > Objectives pane, link this dialogue box with the CCPA privacy objective you created, Create personalized browsing experience.
Click Close and then Save your dialogue.
Now you're ready to ask for consent and see how this information is stored in visitors' profiles.
Employ CCPA consent objectives in your marketing campaigns
As you activate your marketing campaigns, your consented objectives are stored as profile properties, which you can use for segmentation.
To see how Objectives are stored in customer profiles, choose Profiles from the BlueConic menu bar.
In the Privacy management tab, you can see objectives and privacy legislations related to this profile.
With privacy information stored in customer profiles, you can, for example, you create a segment of customers to send to your ESP who have all consented to your CCPA objectives.
Open the Segments page, and choose Add segment to create a segment composed of profiles that have consented to one or more of your CCPA objectives.
With BlueConic objectives, you have a secure way to store and activate consent information for privacy and consent compliance for your customers and visitors -- under CCPA, GDPR, or other privacy legislations. Contact your BlueConic customer success manager to learn more about how you can apply these lessons to your marketing data.
Learn more about using BlueConic for CCPA compliance
FAQ: CCPA and privacy with BlueConic
Managing privacy for multiple legislation zones
Overview of Objectives in BlueConic
CCPA Compliance: How to mitigate your risks (Blog)
(Blog)
View ArticleIn various parts of BlueConic, you work with profile properties, which are the building blocks of customer or visitor profiles in the BlueConic customer data platform. To view or manage these profile properties, select More> Profile Properties from the BlueConic navigation bar.
Organizing and managing profile properties
All existingprofile properties are shown in a navigation list. You can restrictthe listed profile properties by searching and filtering. You can even modify the columns displayed. See " Object Navigation " for an in-depth discussion of the navigation list and its options.
Dialogues in BlueConic
Creating a profile property
To create a new profile property, click on the [Add profile property] button on the top rightof the page.
Define the following settings for a profile property:
Setting
Description
ID
The internal identifier for the profile property. The identifier must be unique for each profile property. A valid ID may consist of letters, numbers, hyphens (-), and underscores (_) and must be at least one character long. Once saved, the ID can not be modified.
Name
This is the human readable text that appears for the profile property wherever it appears in the BlueConic user interface.
Description
A shortdescription of the profile property.
Labels
Assign any number of text labels to the profile property for grouping or easy retrieval.
Segmentation
Specify whether the profile property will show upin the Segments tab for segmentation or not. If you do not show the profile property in the Segments tab, you cannot use it in a segment definition.
Type
Specifies the data type of the profile property. The options are:
Text The value stored in the profile property is in text format. Valid entries include any type of text. Examples:
, Blue Crew
Email address The value contains a valid email address. Example: [email protected]
Number The value stored in the profile property is in numerical format: 0 to 9 and -. If you select this format, you also select the units for the number. The maximum number that can be held by BlueConic is 2,147,483,647. Examples: 1234 and -9876
Decimal The value contains numbers from 0 to 9, - and . with a maximum of 4 decimal places. Examples: 12.3456 and -98
Currency The value contains numbers from 0 to 9, - and .. If you select this format, you can select from over 150 currencies, with the corresponding units. Examples: 12.34 and -98.76.
Date time The value stored in the profile property is in Unix millisecond timestamp format: the number of milliseconds since 1-1-1970 UTC. Example: 1538073598692 represents September 27th, 2018 6:39:58 PM UTC
Note: If you set these data types, BlueConic will enforce them. Once there is at least one profile with a value for the profile property, you can no longer change the data type (except for "Text" profile properties, which can be changed to the type "Email address" at all times). Learn more about validating and enforcing data types in profile properties.
Default values
Enter default values for the profile property. These values willbe available forbuilding segments even when no values have been added by listenersto visitor profiles yet.
Click [Save] to permanently save the profile property.
Expert Settings
Use the profile property expert settings to control the privacy level of the property and what happens to the value of a profile property during profile merging. You can also assign a unique identifier to a profile property that aids in the retrieving of property values using the BlueConic API.
If you aren't sure about how to configure these settings, it's best to leave them at the default value or ask your BlueConic customer success manager.
Setting
Description
Permissionlevel
Specifies what visitor permission level is minimally needed to usethe profile property. The visitor permission level is used by the Opt in - Opt out interaction to determine whether a visitor's browsing experience is personal or anonymous. There are two options:
Level 1 The profile property can only store anonymous data.
Level 2 The profile property can store personal data such as an email address or telephone number.
Merge strategy
Specifies what to do with the value of the profile property if the visitor's profile is merged with another profile. See Profile merging for complete information on profile merging. You have the following options:
Value of current profile The value of the property in the current visitor profile is kept. The current profile is the one the visitor was actively using at the time of the merge.
Keep both The values from both profile properties are kept.
Most recently updated value Keeps the value that was last set.
Sum (number, decimal, and currency only) The values from the two matching profile properties are added together.
Highest (number, decimal, and currency only) Keep the highest number from the visitor profiles as the value.
Lowest (number, decimal, and currency only) Keep the lowest number from the visitor profiles as the value.
Most recent date (date time only)Compare both date values and keep the most recent one.
Oldest date (date time only)Compare both date values and keep the most recent one.
First stored valueIf both profiles have a value, the oldest value (with the oldest timestamp) is used for merging.
Unique identifier
A unique identifier that can be used to retrieve profiles with a specific value for a property, for example, an email address. The unique identifier is also used for profile properties that can be used to create a "When to Merge" rule. See Profile merging for complete information.
Select "Create new profile when identifier changes" for improved privacy and security (to prevent profile hijacking). If checked, the visitor will switch to a new profile when a new value for this property is set.
Visitor access
Determines what access the visitor has from their browser to this profile property. Enable the "Read" option to allowthe visitor's browser to retrieve the value for this profile property. Enable the "Write" option to allow the visitor's browser to write a new value into this property.
Hide from UI
Enable the "Don’t show on Segments tab" option if you do not want this profile propertyto show upon the user interface of the Segments tab. This isuseful if you only want to be able to hand off the profile property in a connection.
Validating and enforcing data types
When you set a data type for a profile property, BlueConic enforces data validation for the number, currency, date time, decimal, and currency data types.
You can see the data type and validation status when you view profile properties in a navigation list.
See validating and enforcing data types to learn more.
Modifying a profile property
You can change any setting for a profile property except the ID of the profile property. When you change any of the settings of a profile property, the [Save] button is enabled. By clicking the [Save] button, the profile property settings are permanently modified. Note: Profile properties that are defined in plugins by a developer are read only and cannot be modified. This is indicated in the user interface by the grayed-out settings and the disabled [Save] button.
Deleting a profile property
To delete a profile property, select the [Save] button and choose[delete] from the dropdown menu. Note: Profile properties that are defined in plugins by a developer are read-only and cannot be deleted. This is indicated in the user interface by the grayed-out settings and the disabled [Delete] option.
Copying a profile property
To copy a profile property, select the [Save] button and choose[Save as...] from the dropdown menu.
A new profile property is created with the same settings as the original profile property, but with an adapted ID. You can set a new ID or change any other setting. By selecting the [Save] button, you finalize the creation of the copied profile property.
Statistics
In the right-hand sidebar, the "statistics" widget shows the number of profiles in your profile database that contain a value for the profile property that you are managing.
It also shows that last date and time a value was set in any of the profiles for this particular profile property.
Related items
In the right-hand sidebar, the "related items" widget shows the other objects in BlueConic that are directly related to the profile property that you are managing.
Profile properties can have the following types of related items:
Segmentsthat use this profile property as a filter. Learn more: Segments in BlueConic
Listenersthat are configured to set a value for this profile property. Learn more: Listeners in BlueConic
Dialoguesthat are configured to set a value for this profile property or interactions that use this profile property as a filter on the "Who" tab. Learn more:
View Articleprivacy management With BlueConic's Open-Time Email Recommendations you can deliver dynamic, individualized content or product recommendations via email based on up-to-the-minute customer data.
Use the BlueConic customer data platform to send personalized recommendations to your email program. These recommendations are updated the moment your customers open their email.
Sending up-to-the-minute recommendations via email
With Open-Time Email Recommendations from BlueConic, you can email personalized product or content recommendations that update automatically when your customers open them. Here's how the open-time email personalization feature works:
Use BlueConic to collect items to recommend in a product store or content store using a Product or Content Collector.
Set up Open-Time Email Recommendations (see steps below).
Match customers' email addresses with their BlueConic profile. (Note that the email addresses used for the recommendations must be known in BlueConic.)
Choose recommendation algorithms that select items to recommend (up to 10 items).
We'll give you the HTML code snippet to paste into your ESP editor.
Send your email. The recommendations will update the moment your customer opens the email, even taking into account clicks, views, or changes that happen between the time you send it and the moment it's opened.
Follow the steps below to get started with personalized email recommendations that update upon opening.
Creating dynamic email recommendation sets
Here's how you can compose a set of up to 10 personalized, dynamic recommendations. Use the HTML code snippet you send to customers via your ESP (email service provider).
Create an Open-Time Email Recommendation connection
Click Connections in the BlueConic navigation bar.
ClickAdd Connection.
A pop-up window appears. Enter "Open-Time Email Recommendations" in the Search bar.
ClickOpen-Time Email Recommendations.
The Open-Time Email Recommendations page opens. You can expand or collapse the metadata fields (favorite, labels, and description) at the top of the page by clicking the gray + or -.
Enter a name for your recommendations set at the top of the page. This name is used inside BlueConic and isn't visible in the recommendations you create.
Configure your personalized email recommendations
In the left-hand panel, click Create Open-Time Email Recommendations and follow these steps, laid out in the import goal.
Note:This example shows content recommendations; product recommendations work the same way in BlueConic.
Choose a BlueConic collector to gather content items or products to recommend.
Recommendations in BlueConic are based on the products or content items collected by a Product Collector or Content Collector.
Select recommendation algorithms and filter rules that determine which items or products are recommended.
Here you choose the rules that select recommendations (and optionally, fallback items) from available products or content items.
Choose the number of items (up to 10 recommended items or products) and click the recommendation algorithm names (Breaking news, etc.) to select recommendation algorithms.
Fallback items fill in any empty spots in your recommendations if the other recommendation algorithms or filters don't produce enough items for the space available.
Design and preview the styling for your recommendations.
Choose a template or customize the design that creates the image and title for each recommended item. Your email service provider (ESP) delivers the overall email message design; this step customizes the recommended item blocks. This preview shows a content recommendation block consisting of an article title with a background image from the content item.
To customize the template, click the select other link and choose from an example template (or create your own).
Identify how customers are matched between BlueConic profiles and your ESP.To match BlueConic profiles to email recipients, enter the ESP expression for your email platform from the list below.
Copy the recommendation HTML code block and paste it into the email message you send from your ESP.
Test or preview your email recommendations
In some ESPs (such as Mailchimp), when you send a “test” email and then preview the message in the browser, recommendations will not be shown. This is because the ESP creates a test email subscriber for previews, and BlueConic recommendations require a user’s email or an identifier that matches a BlueConic profile in order to create and show recommendations.
If your product or content collector is empty, there will be no items to view in step 3. Choose a different product or content collector, or allow the collector time to gather items to recommend.
Learn more about content and product recommendations in BlueConic
Product recommendations in BlueConic
Content recommendations in BlueConic
BlueConic recommendation algorithms
Adding the ESP expression for your email platform
To match customers between BlueConic profiles and your ESP, you need to add the ESP expression for your email provider. Use the table below to find the right ESP expression to use in Step 4 for matching BlueConic profiles to email subscribers on your ESP.
Email service provider (ESP)
ESP expression
Link to learn more
Bronto
\%\%!contact_email\%\%
Oracle Bronto
Campaign Monitor
[email]
Campaign Monitor
Constant Contact
$Subscriber.Email
Constant Contact
dotdigital
@EMAIL@
dotdigital
Higher Logic**
\%\%EMAIL\%\%
Higher Logic
Hubspot
{{contact.email}}
Hubspot
iContact
[email]
iContact
Klaviyo
{{ email }}
Klaviyo
Listrak
#Listrak\Email#
Listrak (see page 149 of PDF)
Mad Mimi
(email)
Mad Mimi
Marketo**
{{lead.Email Address}}
Marketo
Mailchimp
*|EMAIL|*
Mailchimp
Mailigen
#[EMAIL]#
Mailigen
Omeda**
@{email_address}@
Omeda
Oracle Responsys**
${profile.email}
Oracle Responsys
PostUp
[-emailaddr-]
PostUp
Sailthru
{email}
Sailthru
Salesforce Marketing Cloud
\%\%emailaddr\%\%
Salesforce
Silverpop IBM
\%\%Email\%\%
Silverpop IBM
** Note: For these marked email platforms, the email field name may be different.
Privacy management for personalization
The process of creating open-time email recommendations uses a BlueConic connection to the product or content store that holds recommended items. Connections can be added to Objectives, allowing for of the information that is being picked up. If you add this connection to an objective, it will only process the profiles of customers or visitors who have consented to at least one of the objectives the connection is linked to.
View ArticleUsing a customer data platform (CDP) such as BlueConic makes it much easier to manage marketing objectives such as privacy and consent. In BlueConic, you can use Objectives to manage marketing objectives and the items related to them. Objectives help you keep track of the purposes for which you store data and for which purposes actions are taken.
Enable consent management on objectives to use them for visitor or customer privacy management -- for example to use BlueConic to comply with GDPR, CCPA, or other privacy regulations. Items contained in objectives are only executed if the customer or visitor consented to at least one of the consent objectives.
Getting Started with Objectives for privacy and consent management
To use Objectives, you must have the "Objectives" permission or the default permission associated with one of the following BlueConic user roles :
Application Manager
Online Marketer
BlueConic Support
Viewing Objectives
Navigate to the Objectives tab by clicking More in the Navigation bar and then choosing Objectives.
assign objectives to connections, listeners, and external trackers
On the Objectives tab, you can see a table of your organization's purposes with the following default columns:
Name
Consent enabled
Last consent
Consent percent \%
Last modified
You can add more columns to this table through the Columns drop-down list:
Favorites
Name
ID
Consent enabled
Last consent
Consent percentage \%
Times used
Labels
Created by
Last modified by
Created
Last modified
You can filter Objectives through the Filters drop-down list:
Labels
Last modified
Creation date
Created by
Last modified by
Favorites
Consent enabled
Adding Objectives
To add an Objective, follow these steps.
From the Objectives tab, click Add objective. A page for the new Objective opens.
Enter a name for the Objective in the text box.
An Objective ID is given automatically. To edit the Objective ID, click it and enter new text.
Check the Consent management box if your customers or visitors need to have given consent before the items in this Objective can access their profiles.
After checking the box, enter a Consent title and Consent description for the consent given by your customer.
Select one or more privacy legislation zones to the current objective.
Add items that the Objective should contain by clicking the Select... text underneath each heading. Items include:
Connections
Dialogues
Trackers
Global listeners
Listeners
Segments
Notebooks
After selecting an item, clickOk.
Adding an item to objectives with consent management enabled means that it will only be executed if a visitor consented to at least one of the objectives it is contained in.
In the results list for advanced search, you can use Select all to add several items at once.
Note: You can also from the objectives widget in the right side bar of the Connection, Listener, or External Tracker window.
On the top right corner of the screen, click Save.
Editing Objectives
To edit an existing objective, click the Objective's name in the Existing Objectives table on the Objective tab.
Viewing Statistics and Related Items
To view an Objective's Statistics and Related Items, hover over the bar on the right side of the Objective's page.
The Statistics widget shows the percentage of profiles that have given consent for this Objective and the last time a visitor has given consent for this Objective. The Related Items widget shows all items the Objective contains.
Deleting Objectives
You can only delete an Objective if it contains no (0) items. To delete an Objective, click the arrow by Save, then click Delete.
A pop-up window appears. ClickOkto confirm the deletion of this Objective.
View ArticleThe Visual Form listener in BlueConic helps you quickly and easily configure Form Listening on your site. You can use Form Listening to set a value for a property in a visitor's profile based on that's visitor's input. You can use the interaction both to set the value of an existing profile property to a particular value and also to add a value to a profile property that supports multiple values. The visitor's input is derived from a form the user submits on a web page.
Visual Form Listening configuration
Navigate to the page that has the form you would like to collect data from. BlueConic will automatically highlight forms with a dotted line. Select the blue [Select Form] button that corresponds to the form you would like to listen to bring up the configuration menu:
privacy management
The blue checkbox allows you to include or exclude form fields from the listener.
The number in the orange box corresponds to the similarly numbered form field to help identify which field you're working with.
The search box allows you to specify which profile property will be holding the data for the corresponding form field. You may choose an existing profile property or create a new one.
The gear to the right of the searchbar will allow you to select the storage rules for the data.
Once everything is configured, just press the blue [Save] button, close the visual form picker, and your listener will be ready to turn on and run.
Privacy management
Listenerscan be added to Objectives, allowing for of the information that is being picked up. The listener will only update a profile if the visitor consented to at least one of the objectives that it is linked to.
View ArticleWith rule-based form listening in BlueConic, you can set a value for a property in a visitor's profile based on visitor input. You can use the interaction both to set the value of an existing profile property to a particular value and also to add a value to a profile property that supports multiple values. The input from the visitor is derived from a form submitted on a web page.
In this listener you define which form field contains the data to be written to the profile property, the profile property that is written to, and the circumstance that triggers the submission of the data to the profile property.
Configuring a Rule Based Form Listener
Follow the steps in the following sections to configure form listening.
Open the Listeners page and click Add listener.
copying and deleting rulesin BlueConic
Choose Rule Based Form Listener and enter a name for the listener.
In the Where field, define the channels and optionally the URLs where the listener will be active.
Click Add rule to define the listening rule(s).
Defining listen rules
A listen rule defines the form field from which the text or value is taken, the profile property to which the text or value is added or set, and the event that triggers the setting or addition of the text or value to the profile property. The text or value can also be converted according to a defined mapping before it is written to the visitor profile.
If you set the value of a profile property, the current text or value is replaced by the new text or value. An option to set "only if empty" exists to ensure that only the first occurrence of a value is stored in the specified profile property.
If you add the text or value to a profile property, the profile property will contain multiple entries. You must create a listen rule for each form field that you want to write to a profile property.
There are three different types of listen rules that you can create. They differ in the circumstance that triggers the submission of the data in a form field to a profile property. The three different listen rule variations are:
Write data to a profile property when the surrounding form is submitted
Write data to a profile property when a custom form is submitted
Write data to a profile property when a custom position is clicked
Note: The permission level of the website visitor and the profile property must be sufficient to allow the text or value to be written to it. For example, if the permission level of the profile property is Level 2 and the visitor has selected Level 1 permission, the text or value will not be written to the profile property.
Write data to a profile property when the surrounding form is submitted
This listen rule is triggered when an entire form is submitted. The data from the form field you specify is written to the profile property you specify.
Click [Add Rule].
Select whether this rule is an add or set operation. An add operation keeps the existing data in the profile property and adds the new data to it. A set operation substitutes the existing data with the newly submitted data, unless the "only if empty" option is checked.
Select whether this rule deals with text or a value.
Click the "define form field" link. This is the form field from which you want to take the data that is written to the profile property.
Enter a name for the form field in the "Name" text box. This is an internal name for the form field that you choose to use identify it it is not the name of the form field in the source code.
Enter a valid jQuery Selector to define the form field. For complete information on jQuery Selectors, follow this link: http://api.jquery.com/category/selectors/.
To define the area using the Visual Picker, click Visual Picker.
Click OK.
Click the "define profile property" link. You can use an existing profile property or enter a new profile property name to create a new one here. See Profile properties for complete information on working with profile properties.
If you want to convert the value, click here for complete information on configuring value conversion.
Repeat the steps above for each listen rule of this type you want to create.
Click [Save].
Write data to a profile property when a custom form is submitted
This listen rule is triggered when a specified form is submitted. Typically this option is used when you want to write data from a form field to a profile property when a specific form is submitted, not necessarily the one containing the form field in question.
Click [Add Rule].
Select whether this rule is an add or set operation. An add operation keeps the existing data in the profile property and adds the new data to it. A set operation substitutes the existing data with the newly submitted data, unless the "only if empty" option is checked.
Select whether this rule deals with text or a value.
Click the "define form field" link. This is the form field from which you want to take the data that is written to the profile property.
Enter a name for the form field in the "Name" text box. This is an internal name for the form field that you choose to use identify it it is not the name of the form field in the source code.
Enter a valid jQuery Selector to define the form field. For complete information on jQuery Selectors, follow this link: http://api.jquery.com/category/selectors/.
To define the form field using the Visual Picker, click Visual Picker.
Click OK.
Click the "define profile property" link. You can use an existing profile property or enter a new profile property name to create a new one here. See Profile properties for complete information on working with profile properties.
Click the "the surrounding form is submitted" link.
Select "Custom defined form is submitted".
Enter a name for the custom defined form in the "Name" text box.
Enter a valid jQuery Selector to define the custom defined form in the "Selector" text field. For complete information on jQuery Selectors, follow this link: http://api.jquery.com/category/selectors/.
To define the form using the Visual Picker, click Visual Picker.
Click [OK].
If you want to convert the value, click here for complete information on configuring value conversion.
Repeat the steps above for each listen rule of this type you want to create.
Click [Save].
Write data to a profile property when a custom position is clicked
This listen rule is triggered when a custom position is clicked in by the website visitor. The data from the form field you specify is written to the profile property you specify.
Click [Add Rule].
Select whether this rule is an add or set operation. An add operation keeps the existing data in the profile property and adds the new data to it. A set operation substitutes the existing data with the newly submitted data, unless the "only if empty" option is checked.
Select whether this rule deals with text or a value.
Click the "define form field" link. This is the form field from which you want to take the data that is written to the profile property.
Enter a name for the form field in the "Name" text box. This is an internal name for the form field that you choose to use identify it it is not the name of the form field in the source code.
Enter a valid jQuery Selector to define the form field. For complete information on jQuery Selectors, follow this link: http://api.jquery.com/category/selectors/.
To define the form field using the Visual Picker, click Visual Picker.
Click OK.
Click the "define profile property" link. You can use an existing profile property or enter a new profile property name to create a new one here. See Profile properties for complete information on working with profile properties.
Click the "the surrounding form is submitted" link.
Select "Custom position is clicked".
Enter a name for the custom position in the "Name" text box.
Enter a valid jQuery Selector to define the custom position in the "Selector" text field. For complete information on jQuery Selectors, follow this link: http://api.jquery.com/category/selectors/.
To define the position using the Visual Picker, click Visual Picker.
Click [OK].
If you want to convert the value, click here for complete information on configuring value conversion.
Repeat the steps above for each listen rule of this type you want to create.
Click [Save].
Converting values
Before committing text or a value to a profile property, you can convert it based on a defined mapping. You might want to do this in cases where you want to write a different value to a profile property than what was taken from the form field. For example, if a drop-down list in a form has two choices, "Male" and "Female", but you want to write "M" or "F" to the profile property, you can create a value conversion mapping to do this.
To convert text or a value based on a mapping, follow these steps:
Click the "do not convert the value" link.
Select "Convert based on mapping".
In the "Original value" text field, enter the text or value from the form field that you want to convert.
In the "Converted value" text field, enter the text or value that you want to convert the original text or value to.
Click [Save mapping].
Repeat the steps above for each mapping that you want to define.
Click [OK].
To delete a mapping, click the delete icon to the right of the mapping.
Privacy management
Listenerscan be added to Objectives, allowing for privacy management of the information that is being picked up. The listener will only update a profile if the visitor consented to at least one of the objectives that it is linked to.
Copying and deleting rules
Learn more about .
View Articleprivacy management
What:FullContact is a service that builds a clearer picture of your customers and visitors. Have BlueConic enrich the profiles of your known visitors with the information harvested from the public internet by FullContact.
About BlueConic: The BlueConic Customer Data Platform harnesses the data required to power the recognition of an individual at each interaction, and then synchronizes their intent across the marketing ecosystem. Learn more about the BlueConic CDP.
Why:FullContact can return a wealth of publicly known information based on an email address. This will help you build a clearer picture of your known audience.
Configuring a FullContact connection
Start by setting up the communication channel between BlueConic and FullContact by obtaining your API key from your FullContact environment. Open the Setup tab on the left hand side and enter your API key:
BlueConic can now connect to FullContact, but you still have to set up mapping rules on what to import. Activate and open the tab "Import data into BlueConic" on the left hand side. Follow the steps:
1. Select BlueConic segments
Select one or more segments that visitors will have to be a part of in order to have their profiles enriched by FullContact. For example: you could use this to only enrich profiles that haven't been enriched already by creating a segment that tests the mapped profile properties to be empty.
2. Select BlueConic trigger(s)
Select one or more profile properties that should be used as a trigger; when their value in the profile changes a request to FullContact will be triggered to enrich the profile. A good choice for the trigger is the profile property you will use for identifier.
3. Select identifier
Select the FullContact identifier and the BlueConic profile property whose value should match in order to enrich a profile.
4. Map FullContact data to BlueConic
Here you select the data from FullContact that you would like to import into BlueConic and determine to what BlueConic profile properties the data will be mapped. To add more mapping rules click the button [Add mapping].
Give your connection a name, switch it on, and save it. Now you're ready to go and profiles will be enriched as their trigger profile properties change! Note that this will only work from this point in time forward; existing profiles will not automatically be updated.
Privacy management
Connectionscan be added to Objectives, allowing for of the information that is being picked up. A connection will only process the profiles of visitors who have consented to at least one of the objectives that the connection is linked to.
View ArticleProfile properties are where the BlueConic customer data platform stores information on your customers or visitors. For example, if a user subscribes to a newsletter, the email address is stored in the profile. Many profile properties record information about the user or visitor (email address, interests, city, products bought, etc.).
How do I collect behavioral customer data?
In addition to profile properties you explicitly create and collect, BlueConic also observes users' behavior and stores that information in real time in behavioral profile properties that assign numerical values to your customers' behavior on your site. These values track how frequently customers are active on your site, their level of activity, the intensity of their visits, and relative increase or decrease in activity (momentum scores). Behavioral scores range from 0 to 100, making it easy to compare profiles on the same scale.
How do behavioral profile properties differ from regular profile properties?
Behavioral profile properties are distinctive in several ways:
They update in real time.
They compare the entire population of visitors.
They automatically change over time--even if the visitor is offline.
Scores are calculated at the start of each visit and remain the same during that visit.
Data is collected by the Global Listener, which tracks contact moments, such as website visits. You can inspect or visualize the behavioral scores for an individual profile by selecting Profiles from the main BlueConic menu and choosing a profile to view.
manage customer privacy and consent for GDPR and CCPA
How do marketers use behavioral profile properties?
Marketing teams can use behavioral profile properties and related segments for targeting, messaging, lead generation, and re-engagement campaigns. See the use case ideas for each profile property below and also Using real-time behavioral customer data.
To see behavioral profile properties for your profiles, select Profiles from the BlueConic menu and select the Profile overview tab.
Real-time behavioral profile properties
Behavioral: Recency
The Recency profile property measures how active a customer has been on your site lately, with a score of 100 for profiles active on your site today, ranging to 0 for profiles whose last activity was 100 days or more. A profile with a recency score of 80 was last active on your site 20 days ago.
Marketing teams use the recency score to:
Identify active users with high scores who might respond to offers.
Re-engage users who have low scores for recency, inviting them back with custom offers or discounts.
Re-activate users who haven't visited recently by sending email or mobile communications.
Recency scores are updated after the current visit.
Prebuilt behavioral segment: BlueConic provides a prebuilt "Visitors from the past 7 days" segment based on the recency score. It includes all profiles with a recency score of 93 or higher. See Behavioral customer segments for details.
Behavioral: Frequency
The frequency score shows how often a customer visits your site. Marketing teams use this information to customize messaging:
Is a certain customer already a high scorer? Elevate the conversation to a call center.
For customers who are not so active, use an email campaign to restart the conversation.
Prebuilt behavioral segment: BlueConic uses this score as the basis for a prebuilt "Highly frequent visitors" segment. It includes all profiles with a frequency score of 85 or higher. See Behavioral customer segments for details.
Behavioral: Intensity
The intensity score measures how intense the customer's interactions are on your site (i.e. the average number of page views per visit).
Marketing teams use this information to customize content and product content:
High scores identify customers who enjoy in-depth content (lots of page views), so deliver more content to this group.
Cross the list of highly intense visitors with those who have not yet supplied an email address, and spur them to action with a CTA tied to their interests.
Low intensity scores point to customers who consume content in smaller doses.
With content metering, lower intensity might show customers hitting a paywall.
Prebuilt behavioral segment: BlueConic uses the intensity score to create a prebuilt segment for "Highly intense visitors." It includes all profiles with an intensity level score of 85 or higher. See Behavioral customer segments for details.
Behavioral: Recent intensity
The recent intensity profile property shows the amount of a customer's recent activity on your site over the past 30 days. This value decays over time, so after 72 days the value is half of what it was.
Marketing teams use this information to customize messaging:
Customers with high recent intensity scores are increasing their interaction with your site, you can devise offers and messages to encourage them to buy, subscribe, or take the next step down the marketing funnel.
If a customer is suddenly less active than usual, send an email or message to re-ignite interest and activity.
Prebuilt behavioral segment: BlueConic uses the intensity score to create a prebuilt segment for "Recently very intense visitors." It includes all profiles with a recent intensity level of 75 or higher. See Behavioral customer segments for details.
Behavioral: Momentum
The momentum score compares a customer's past 7 days of activity with the same person's average 7 days of activity. Momentum scores range from 0 (this profile has visited far less this week than usual) to 100 (this profile has had much more contact with your site in the past 7 days). For example, if someone typically visits your site 5 times per week, but increases their activity to have 20 different contacts this week, their momentum score would be 95.
Momentum scores are valuable clues to determine whether a customer is trending toward more engagement or less:
A sudden increase in momentum might signal a propensity to buy or engage. You may want to target these users with special offers
You can use this score to target low-momentum customers with a re-engagement campaign that reaches out to visitors who've been inactive for the past week.
Prebuilt behavioral segment: BlueConic uses momentum scores to build two prebuilt customer segments: "Visitors with high momentum" (momentum scores over 75) and "Visitors with low momentum" (momentum scores under 10). See Behavioral customer segments for details on these segments.
Next steps
Marketing use cases: See Using real-time behavioral customer data for ideas for behavioral targeting and messaging.
Segmenting customers based on behavioral data:BlueConic provides prebuilt six behavioral segments based on the behavioral profile properties. See Behavioral customer segments for details on using these segments to reach your marketing goals.
Calculating behavioral profile property values
This section provides details and formulas for how BlueConic calculates the values stored in the five behavioral profile properties: activity, frequency, intensity, recent intensity, and momentum.
All scores are calculated at the start of each visit (20 minutes of inactivity) and remain the same during that visit. For example, if the visitor pays three visits to your channels in a single day, then the score of the behavioral profile properties will be re-calculated three times for that visitor.
The "Frequency," "Intensity," and "Recent intensity" properties compare the visitors behavioral scores to the scores of all other visitors to your channels. To avoid clutter by outliers, the top 5\% of highest scoring visitors will be ignored.The highest value that is left after removing the top 5\% of individuals, sets the mark for the 100-index value. This recalibration is done once per day.
Behavioral: Recency
Recency indicates the number of days since the visitor was last active. This value is 100 if the visitor has been active today, 99 for yesterday, 98 for two days ago, and so on. This value is 0 if the visitor has been inactive for 99 days or more.
Value
Description
Maximum
100
Active today
Minimum
0
Active 99 days ago or more
Formula:
Recency = 100 -dlv
Where:
dlv = Number of days since the last visit
Behavioral: Frequency
Frequency provides a ranking from 0 to 100 for the average number of visits this person made per day from the first visit until today. All individual profiles in your universe are considered (leaving out the top 5\% of outliers). Visitors with the highest average in your universe receive a frequency value of 100. The value is 0 for visitors with an average of (nearly) 0 visits per day from their first visit date.
Value
Description
Maximum
100
Among the most frequent visitors in the universe
Minimum
0
Among the least frequent visitors in the universe
Formula:
Frequency =(v * 100) / (dfv * fmax)
Where:
v = Total number of visits
dfv = Number of days since the first visit
fmax = Highest daily frequency of all visitors, ignoring the top 5\% of values
Behavioral: Intensity
Intensity indicates the average number of page views per visit from the person's first visit until today. This value is 100 for visitors with the highest intensity average since their first visit in your universe, leaving out the top 5\% of outliers. This value is 0 for visitors with an average intensity of (almost) 0 per day since their first visit.
Value
Description
Maximum
100
Among the visitors with the highest average intensity
Minimum
0
Among the visitors with the lowest average intensity
Formula:
in =round((pn / pmax) * 10)
Overall Intensity =(100 * i1..n) / (dfv * imax)
Where:
in = Intensity of single visit n
imax = Highest daily intensity of all visitors, ignoring the top 5\% of values
pn = Number of pageviews for visit n
pmax = Highest number of pageviews of all visitors, ignoring the top 5\% of values
i1..n = Sum of all single visit intensities
dfv = Number of days since the first visit
Behavioral: Recent intensity
Index for the recent intensity (amount of activity during one visit) of the visitor. The impact of an activity on the value will decrease over time. This value is 100 for visitors with the highest recent intensity in your universe. This value is 0 for visitors with a recent intensity of (almost) 0.
Value
Description
Maximum
100
Among the visitors with the highest recent intensity
Minimum
0
Among the visitors with the lowest recent intensity
The formula for recent intensity is basically the same as for intensity (shown above), with one difference: the value of the intensity per visit (in) decays over time. Every 72 days, the value will be the half of what it was. For example, if the intensity of a visit was 8 on the day of the visit, it will be 4 after 72 days, and 2 after 144 days.
Behavioral: Momentum
Momentum considers the past 7 days of a visitor's activity and compares it to the average 7-day activity of that visitor in all time. The value is 50 when the last 7 days' activity is the same as the average. If there is more activity than the average, the value will be higher, with a maximum of 100. If there is less activity than average, the value is lower, with a minimum of 0.
Value
Description
Maximum
100
Much more active this week than usual
Average
50
Same level of activity as usual
Minimum
0
No activity at all, or much less active this week than usual
Formula:
New visitors
IF first visit date is less than 7 days ago
THEN momentum = 50
Inactive visitors
IF number of visits in last 7 days is 0
THEN momentum = 0
Decreased momentum
IF number of visits per day since the first visit is greater than or equal to that of the last 7 days
THEN momentum = (vf / vw) * 50
Increased momentum
IF number of visits per day since the first visit is lower than that of the last 7 days
THEN momentum = 100 (vf / vw) * 50
Where:
vw = Number of visits per day in the last 7 days
vf = Number of visits per days since the first visit
Some examples
A new visitor had3 contacts since the first visit 6 days ago; their momentum is 50.
An inactive visitorhad 0 contacts in last 7 days and has 0.12 visits per day since the first visit; their momentum equals 0.
A visitor with decreased momentum has 2 visits per day since first visit and 1 visit per day over the last 7 days; their momentum is: (1 / 2) * 50 = 25.
A visitor with increased momentum has0.5 visits per day since first visit and 1 visit per day over the last 7 days; their momentum value will be: 100 (0.5 / 1) * 50 = 75.
Managing privacy, consent, and behavioral profile properties
With the privacy legislations GDPR and CCPA in mind, it's possible to disable the collection and calculation of the behavioral profile properties. The data needed for these properties is provided by the Global Listener, so consent for these behavioral profile properties is tied to the Global Listener.
You can enable consent management for behavioral profile properties by adding the Global Listener to a BlueConic marketing objective that has consent management enabled. Once this is enabled, the profile properties will only be available for profiles that have given consent to the objective.
Learn more about using BlueConic objectives to .
View ArticleBlueConic offers a range of tools to customize personalized content recommendations. The Content Recommendations toolbar plugin adds a capability to the toolbar of the content editor that lets you insert content placements, dependent on having set up a Content Collector Connection. Click on the icon to insert a content placement based on an algorithm of your choosing at theplace of the cursor.
You can vary recommendations so they are not the same on every page:
Use contextual filters and algorithms based on the current page (look-alike algorithm, metadata filters based on current page, etc.).
Create multiple variants with different settings and make them rotate.
Use the option in the filters area to exclude content if it hasn't been clicked on a after a certain number of views, for example.
Use a fallback set of recommendations to fill the recommended items area if your algorithms and filters don't produce enough new content to recommend.
To add a recommendations placement, edit an interaction and click "Insert object"from the content editor toolbar:
Top recommended items insight
Selecting "Content Recommendations" adds a placeholder placementto the content editor. Hovering over the placeholder will light it up in blue. Click and edit or double-click the placeholderto open the Content recommendations pop-up where you can configure the content placement.
Configuring content recommendations
Collector: Select a Collector, which serves as a source from which recommended items will be chosen. You define this by configuring a Content Collector Connection.
Layout: Click the dropdown menu to choose a template to display your recommendations -- for example, in a list of links, or a list with images, etc. You can also choose to edit your own template for recommendations.
Frequency cap: You can choose to exclude articles after the user has seen the article a set number of times and not clicked on them.
Recommendation sets: Choose the number of articles or posts you'd like to include in the recommendations that are displayed. By default, there is one recommendation set showing four items with one algorithm and one filter. Add new sets of recommendations with different algorithms and filters to select the recommended content.
You can have multiple sets of recommendations. Double-click the recommendation set to edit or adjust its algorithms and filters. Click copyto duplicate a recommendation set. If you have more than one, you can reorder the recommendation sets by dragging and dropping the recommendation bar up or down. Click deleteto remove a recommendation set.
Enable fallback:You can set a fallback algorithm so if the recommendation set(s) you've defined don't deliver enough results to fill a set, you can fill the empty space with other items. If you choose to enable fallback recommendations, content items that don't already appear in the recommendation set and also match the configured algorithms and filtering options are used to fill any empty spots in the recommendations area.
Algorithms
To refine the algorithms that choose recommended items, click the algorithm box in a recommendation set.
The algorithms tab opens,where you can adjust the algorithms that select content for each individual user. To return to the main content recommendations window, click the arrow in the upper left corner.
As you make changes, you should be able to see them reflected in the content placement in your editor window:
There are a number of algorithms you can introduce, to boost the prevalence of articles with certain characteristics as described below. For each algorithm added, you can control whether it is used at all, and to what degree it will be incorporated into the overall content selection.
Content recommendation algorithms
BlueConic offers recommendation algorithms that are profile-based, aggregate usage stat-based, and content-based.For details on how each algorithm operates, see BlueConic recommendation algorithms.
Aggregate stats-based algorithms:
Viral news:Content that has been popular as an entry point to the site over the last several hours.
Recent high CTRs:Contentthat hasbeen clicked within content recommendations placements served by BlueConic.
Breaking news:Contentthat has been read the most across the site over the last several hours.
Content-based algorithms:
Same category:Contentthatis in the same category as the current article being read.
Look-alike articles:Contentthat hasa similar textual makeup (title, description and text) to the current article being read.
Recency:Content that has a recent published date.
Seen articles: Boost articles the viewer recently viewed.
Profile-based algorithms:
Collaborative filtering:Content read byother users similar to the current user.
Same interest:Contentthatis in the same categories as those the user has shown the most interest in.
Tip: Not sure which algorithm to choose? Choose a few different algorithms to try. You can test them with A/B testing and optimization.
The timeframe defined for content algorithms is defined at the bottom of the Content Collector connection.
Setting the ramp up speed of profile-based algorithms
Profile-based algorithms also take a "ramp up speed" setting, which enables BlueConic to react more quickly to any information that is being populated in the user profile:
Filters
The filters area allows you to include or exclude content based on its metadata or other options.
Seen articles:Either exclude articles or only show articles the user recently viewed.
Metadata filters
You can specify how metadata filters should be applied to recommendation sets. When you click the Add filter button, you can construct a new metadata filter tailored to the data your content collector gathers. For example, if your content consists of articles tagged by the categories Sports or Entertainment, you can filter for articles that exactly match those categories.
See your top content recommendations
To see which content items are recommended most often, use the .
FAQ: Content recommendations
Q: I removed an article from my page. When will it be removed from the recommended items?
A: A content item will be added to a queue to be deleted when the required fields can no longer be scraped in the browser of the visitor, even if a visitor views the item -- for example, if the article has been deleted or if the publication date is no longer available.
Q: I cannot see item X in my personalization recommendations. What could cause this?
A: Items or articles are added to the recommendations queue when a customer or visitor views the item. Articles that have no views from customers or visitors won’t be added to the queue.
Items in the recommendations queue are evaluated and if the required fields become valid, those articles are added to the content store for personalization.
Indexing items may take some time while when the collector is still collecting items Depending on how much traffic your channel has, there might be a short delay indexing content items when the collector is still actively collecting items.
Q: When will my item be added to the queue to be evaluated?
A: Items are added to the queue for the first time when a visitor views an article. Also, when an item or content article has been clicked on twice, but no view follows the click, the system checks for all required fields and re-evaluates whether to include or delete the item.
View ArticleBlueConic offers a several tool to create personalized recommendations. To create product recommendations in BlueConic, you use the ProductRecommendations toolbar plugin in the toolbar of the content editor. This lets that you insert personalized productplacements on your pages or in an app (note that you'll need to also set up a ProductCollector ).
Inside a BlueConic dialogue, select the content editor to insert a content placement based on a recommendation algorithm of your choosing at theplace of the cursor.
To add a recommendations placement, edit an interaction and select Insert object > Product Recommendations from the content editor toolbar.
top recommended items insight
When you select "ProductRecommendations" BlueConic adds a placeholder placementto the content editor. Hovering over the placeholder makes it light up in blue. Click and edit or double click the placeholderto open the product recommendation popup for configuring the productsthat get recommended and how they appear to customers.
Configuring product recommendations for personalization
Collector:Select a Collector, which serves as a source from which recommended items are chosen. You define this by configuring a ProductCollector Connection.
Layout:Click the dropdown menu to choose a template to display your recommendations -- for example, in a list of links, or a list with images, etc. You can also choose or edit your own template for recommendations.
Frequency cap: You can choose to exclude items after the user has seen them a set number of times and not clicked on them.
Recommendation sets:Choose the number of products you'd like to include in the recommendations that are displayed. Add new sets of recommendations with different algorithms and filters that select the recommended content.
You can have multiple sets of recommendations. Double-click the recommendation set to edit or adjust its algorithms and filters. Click copyto duplicate a recommendation set. If you have more than one, you can reorder the recommendation sets by dragging and dropping the bar up or down. Click deleteto remove a recommendation set.
Enable fallback:You can set a fallback algorithm so if the recommendation set(s) you've defined don't deliver enough results to fill a set, you can fill the empty space with other items. If you choose to enable fallback recommendations, products that don't already appear in the recommendation set and also match the configured algorithms and filtering options are used to fill any empty spots in the recommendations area.
Product recommendations algorithms for personalization
To refine the algorithms that choose recommended products, select the algorithm box in a recommendation set.
The algorithms tab opens,where you can adjust the algorithms that selecta unique product setfor each individual user. As you make changes here, you should be able to see them reflected in the placement in your editor window.
To return to the main recommendations window, click the arrow in the upper left corner.
Choosing your product recommendation algorithms
You can choose from a number of algorithms to boost the prevalence of productswith certain characteristics as described below. For each algorithm added, you can control whether it is used at all, or to what degree it will be incorporated into the overallselection.
There are three types of algorithms you can apply: aggregate stats-based, product-based, and profile-based.
Aggregate stats-based algorithms for personalization
Recent high CTRs:Productsthat havebeen clicked most within recommendation placements served by BlueConic.
Top products:Productsthat have been engaged withthe most across the site over the last several hours or days (configurable in product collector).
Viral products:Products that have been popular as an entry point or landing page to the site over the last several hours or days (configurable in product collector).
Product-based algorithms for personalization
Look-alike products: Productsthat havea similar textual makeup in the description to the current product.
Same category:Productsin the same category as the current product.
Recency:Products witha recent release or availabilitydate.
Seen products:Products the user has already browsed.
Carted: Products this user has already placed in the shopping cart (and which are still there).
Products carted most often: Products most often placed in the shopping cart during the chosen time frame.
Bought: Products this user recently bought.
Products bought most often: Products most often bought during the chosen time frame.
Note that for product-based algorithms, you need to use a Product Collector to create a collection of product data (called a product store) that will feed recommendations.
Profile-based algorithms
The following profile-based algorithms also take a "ramp up speed" setting, which allows BlueConic to react more quickly to any information that is being populated in the user profile.
Collaborative filtering: Products engaged withbyother users similar to the current user.
Same interest:Products in the same categories as those the user has shown the most interest in.
See BlueConic recommendation algorithms for details on how each algorithm operates.
Filters
In the Filters tab, you can choose to include or exclude productsbased on metadata or other options.
Seen products:Products the user has already browsed.
Carted: Products the user has already placed in the shopping cart (and which are still there).
Bought: Products the user recently bought.
Hide out of stock products: Include only products that are in stock, based on an in stock indicator configured in the product collector
Metadata filtering for personalization
Metadata scraped from the product collector can be used to filter the product selection:
In this way, you can include or exclude products based on their relationship to metadata within the current product being browsed, or within the user profile:
Below is an example where an explicitly defined value, "clearance", being excluded from a selection of products:
You can also match personalized recommendations to a user's categories of interest, as in this example:
See your most recommended products
With any personalization strategy, it's important to measure your results. To see which products are recommended most often, use the .
FAQ: Personalized product recommendations
Q: I removed an item from my web store. When will it be removed from the product recommendations?
A: Products are removed from the list of product recommendations when required fields can no longer be scraped in the visitor's browser. This is true even if the visitor views the item -- for example, if the product has been deleted or if the delivery date is no longer available.
Q: I cannot see item X in my personalized recommendations. Why is that?
A: Product items are added to the recommendations queue when a customer or visitor views the item. Items that have no views from customers or visitors won’t be added to the queue.
Items in the recommendations queue are evaluated and if the required fields become valid, those items are added to the product store.
Indexing items may take some time while when the collector is still collecting items Depending on how much traffic your channel has, there might be a short delay indexing items or products when the collector is still actively collecting items.
Q: When will my item be added to the queue to be evaluated for personalization?
A: Items are added to the queue for the first time when a visitor views a product item. Also, when an item has been clicked on twice, but no view follows the click, the system checks for all required fields and re-evaluates whether to include or delete the item.
View ArticleTo create personalized product recommendations in BlueConic dialogues, you start by collecting product data using the BlueConic Product Collector Connection. This connection collects data about your products and stores it in a BlueConic product store to be used for personalization in BlueConic.
Make smarter product recommendations
You can use this information to make smarter product recommendations in dialogues. Deliver one-to-one product recommendations using toolbar plugins that use filters and product recommendation algorithms to choose the optimal products to recommend based on individual customers' behaviors, interests, preferences, and previous purchases.
Use personalization to target customers with abandoned shopping carts
By detecting the number of items in the customer's shopping cart and the last update, you can target customers who have abandoned shopping carts to complete their purchases.
BlueConic recommendation algorithms
Note: The Product Collector needs to be active on the page that fires the `shoppingcart` or `order` event on your site, such as the shopping cart or order page (not just on the product pages).
Configure the Product Collector
To create a Product Collector connection, select Connections from the main BlueConic menu and click the Add connection button. Search for 'product collector' and create the connection.
To set up the connection, select "Collect data from your channels" in the lefthand panel.
Select the channel(s) to collect product data from.
Optionally, define URL rules to specify which areas of the sites to collect product data from.
Next, paste a product URL into the "Test URL" area, and click 'Test' to review the metadata that would be collected for your product:
If the "Name", "Description", "Image", "URL," and "Categories" fields are not populated, the webpage may not surface product information in a supported format. BlueConic supports:
Schema.org Microdata or JSON-LD
Getting started with schema.org using Microdata
The complete beginner’s guide to Schema.org markup
Structured data with schema.org- the ultimate guide
Open Graph meta tags
Regular meta tags
To add custom metadata fields, select Add data field. For example, if your products have a typical gender association, or are tagged based on associated brands,influencers, or sources, you can use this data in recommendations placement filtering.
Some algorithms are based on a look-back timeframe, for example the "top products" algorithm.
You can configure this timeframe based on hours or days here:
Optional: Add request headers, to be able to scrape content for webpages that are only available after login, after a paywall, or on development sites.
Detect products in the shopping cart, order data, and last time the cart was updated.
A. Add shopping cart data to profile properties.
Select profile properties to store the number of unique products in the customer's shopping cart. You can choose an existing profile property or create one here.
B. Implement the JavaScript shopping cart event.
Add the following JavaScript code to your website to let BlueConic know which products the customer adds to or removes from the cart, and when the cart is emptied. Use this data in dialogues for recommendations.
// Replace the contents of the productIds array
// with the IDs of all products that are currently in the shopping cart.
blueConicClient.event.publish("shoppingcart", {
productIds: ["your", "product", "ids"]
});
C. Implement the JavaScript order event.
Add the following JavaScript code to your website to let BlueConic know which products the customer ordered. Use this data in dialogues to improve recommendations, using the "bought items" algorithm and collaborative filters and algorithms for order data.
// Replace the contents of the productsIds array
// with the IDs of all products the customer just ordered.
blueConicClient.event.publish("order", {
productIds: ["your", "product", "ids"]
});
Note: For both JavaScript options B and C, the product IDs in the event should exist in the content store. The configuration of the "ID" field should match the ID that is sent in the event.
For details on the recommendation algorithms that power personalized product recommendations in BlueConic dialogues, see .
View ArticleTo create personalized content recommendations in BlueConic dialogues, you start by collecting a content store, which is a pool of content to be recommended, using the BlueConic ContentCollector Connection. This connection collects data about your contentand stores it in a BlueConic contentstore, which feeds personalization in BlueConic.
Make smarter content recommendations
You can use the content items collected through the connection in BlueConic dialogues to make smarter personalized content recommendations. BlueConic recommendations are powered by algorithms and filters you set inthe content editor toolbar.
BlueConic recommendation algorithms
Configure the Content Collector
To create a Content Collector connection, select Connections from the main BlueConic menu and click the Add connection button. Search for 'content collector' and create the connection.
To set up the connection, select "Collect data from your channels" in the lefthand panel.
1. Select the channel(s) to collect contentdata from.
Optionally, define URL rules to specify which areas of the sites to collect contentdata from.
2. Manage which data is collected.
Next, paste an article URL into the Test URL field, and click 'Test' to review the metadata that would be collected for your content:
BlueConic requires a number of metadata fields out of the box. Select the checkbox for other metadata fields that are also required.
If required metadata fields are not populated, the webpage may not surface contentinformation in a supported format. The default BlueConic selector will automatically detect:
Schema.org Microdata or JSON-LD
Getting started with schema.org using Microdata
The complete beginner’s guide to Schema.org markup
Structured data with schema.org- the ultimate guide
Open Graph meta tags
Regular meta tags
Providing metadata in one of these standard ways is not only good for the content collector, it is good for Google, Facebook, Twitter, and countless other platforms, as it allows these platforms to understand your content!
Click Default to select an alternative method of retrieving metadata. You can retrieve information from metadata in the HTML, or retrieve it from the HTML using a selector, or using JavaScript.
Click Add data field to add custom metadata fields. For example, if your content has a sponsorship association, or is ;tagged based on overarching stories or topics, influencers, or sources, you can use this data in recommendation placement filtering.
3. Set the algorithm timeframe.
Some recommendation algorithms are based on a look-back timeframe (for example, Viral articles or recent high CTR). You can configure that timeframe here, based on hours or days:
For details on how each recommendation algorithm operates, see .
4. Set request headers (optional).
To enable content recommendations to be collected from webpages that are under development or behind a login or paywall, you can add HTTP request headers here. Click "Add request header," choose a channel, and add the custom header name and value used to access the content.
Content personalization tips:
Make sure images are being scraped properly.
Review article names to be sure appendages do not exist, for example " | Site.com" may be appended to every title depending where it is being scraped from.
View ArticleIn BlueConic, you can create personalized content recommendations with a number of templates to display articles collected with a content collector. The same goesfor product recommendations and the product collector. This article describes how you can edit or add to these personalization templates.
Warning: You are entering the Developer Zone!
If you are comfortable working with HTML, CSS, and JavaScript, proceed. If not... It's not too late to turn back!
Selecting or modifying an existing template for personalized recommendations
Sometimes you will want to modify an existing recommendations template. Start in the dialogue editor by editing the object and opening the "Design" tab.Here you can select an existing template, or you can edit a template by clicking its name or the edit icon Mustache :
If the existing designs work fine with your website, great! However, in our experience website designs vary greatly and the standard designs will likely not blend in perfectly with your website.
No worries! Read on to learn how to best create a new template that will blend in perfectly!
Creating a new personalization template
The best way to integrate personalized recommendations in your website is to:
Pick the position on the page where you want the recommendations to appear.
Copy the HTML from that position.
Make a template from the copied HTML.
Have the dialogue appear on the position you picked.
This has several advantages:
No need to cook up your own HTML - reuse what is already there.
No need to add CSS - you're working with HTML originally from the website, so existing styling will automatically play well.
No need to think of responsive design - the dialogue will be just as responsive as the original HTML was.
The example below illustrates how to create a new template from existing HTML.
Start by clicking the[Add Template]button underneath the template selection:
Thiswill take you to the template editor. The template editor showsthe three sourcesthat together produce your content: the HTML template, CSS, and JavaScript. On the bottom right, a preview shows the resulting web pagebased on these three sources.
The previewwill update as you change thesources. You will see randomly chosen content recommendationsemulatingwhat the recommendations wouldlook like in the actual dialogue.
The preview is missing the actual CSS of the page the dialogue will appear on. This means the preview may very well look different from the end result that you will see in the dialogue.
Metadata
You can change the name of the template by editing its name, or click "Show metadata" and edit thedescription of the template and its preview image (for usein the template selection gallery).
HTML template
The HTML template consists of a combination of HTML and tags for the control flow. Here is a very basic example of a recommendations template:
<ul>
{{#recommendations}}
<li>
{{#image}}<img src="{{image}}&width=200&height=100" />{{/image}}
{{name}}
</li>
{{/recommendations}}
</ul>
This template builds a list of recommendation items consisting ofan optional image and a name.
Let's break down this template by its Mustache tags. First there is the loop over all recommendation items using the recommendations Mustache tags:
{{#recommendations}}
...
{{/recommendations}}
Then, for each recommendation item determine if an image URL is available using the image Mustache tags:
{{#image}} ...{{/image}}
When a URL exists for the item, use the image Mustache tag to fill thesrc attribute:
<img src="{{image}}&width=200&height=100" />
It is recommended to add width and height to serve a specific size of image, to minimize bandwidth usage for the visitor. Also display the name of the item:
{{name}}
The table below displays all Mustache tags thatare available for each recommendation item. Note that Mustache tag names are case sensitive.
Tag Name
Description
gated
true if the recommendation item is gated from access to the general public, false otherwise.
Example usage:
{{#gated}}
Gated content
{{/gated}}
{{^gated}}
Free content
{{/gated}}
score
The calculated recommendation score for the item, e.g. 1.0
image
The URL of an image for the recommendation item, if available. E.g.: https://dogfood.blueconic.com/rest/contentStores/315ac9c5-666a-48dc-84ac-741d4f4da3e9/items/www.blueconic.com\%252Fbenefits\%252F/image?etag=1499708703368
name
The name or title of the recommendation item, e.g. BlueConic - Know the Individual. Drive Better Outcomes.
description
The description of the recommendation item, e.g.Use BlueConic to recognize an individual at each interaction, and synchronize their intent across the marketing ecosystem.
ID
The unique identifier for the recommendation item, e.g. www.blueconic.com/pricing/
recommendationId
The BlueConic identifier for the recommendation item, e.g. 8890a595-aa56-454f-a2d0-abb28f7c2ebf
category
The categories for the recommendation item, e.g. customer engagement, customer experience management, marketing management software, user behavior analytics
URL
The URL for the recommendation item, e.g. https://www.blueconic.com/pricing/
isFirstItem
true if the item is the first of the list, false otherwise.
Example usage:
<div class="col-sm-3{{#isFirstItem}} first{{/isFirstItem}}">
isLastItem
true if the item is the last of the list, false otherwise.
Example usage:
<div class="col-sm-3{{#isLastItem}} last{{/isLastItem}}">
index
The index of the item in the list of recommendation items, e.g. 0
creator
The name of the creator of the recommendation item, e.g. BlueConic
Data field ID of any field
Use the Data field ID of any field you added in the content collector connection to retrieve its value.
Pro tip: To best blend in recommendations on a page, find a block of items that looks the way you want, inspect it and copy/paste the HTML of that block into a new template. Then add {{#recommendations}} ... {{/recommendations}}, reduce the number of items to 1, and replace {{name}} and other Mustache tags as needed. Your template will fit right in the page and play well with its CSS!
CSS
The CSS source determines how the list of recommendations will look. This works the same way as regular HTML and CSS, but it's important to remember that the recommendations will be shown on an existing page that has its own HTML and CSS. Chances are the page styling will interfere with your styling of the recommendations orvice versa.
This is why the best practice is to "namespace" the recommendations with a unique class name on the outer element. This allows you to uniquely override page styling with specific recommendation styling, while also making certain page styling is left untouched.
Here is an example of how toapply a namespace "basic-list" to the basic template we showed earlier:
<ul class="basic-list">
{{#recommendations}}
<li>
{{#image}}<img src="{{image}}&width=200&height=100" />{{/image}}
{{name}}
</li>
{{/recommendations}}
</ul>
In the CSS we apply the namespace class to every rule in our source. This will prevent styling from bleeding over into the rest of the page.
ul.basic-list {
...
}
.basic-list li {
...
}
.basic-list img {
...
}
While this namespacing prevents our content recommendation stylesfrom bleeding over into the rest of the page, the reverse is not true. There still may be styling rules on the page that have an unwanted effect on the recommendations.
To deal with this, inspect the culprit in the browser usingthe right mouse button, and determine the rules that set the offending CSS properties.
For example, if the inspector shows thatour ul element inheritsa margin-bottom of 20px from the page:
We can counter thisby adding our own, namespaced version of this rule to our CSS code:
ul.basic-list {
margin-bottom: 0;
}
The same technique would also work with more complex rules; copy the selector from the browser and make it more specificwith your namespace, for example:
/* Overruling selector "body nav.suggestions ul li" */
body nav.suggestions ul.basic-list li {
background-color: #fff;
}
JavaScript
In the JavaScript source you can optionally add JavaScript that should be executed after the recommendation template has been rendered - i.e., the elements created by the template will exist by the time the script runs.
View ArticleBlueConic content and product recommendations provide an unmatched advantage for effective personalization: first-party customer data. Using your own datasets and behavioral data collected during content consumption, the BlueConic customer data platform delivers individualized recommendations at scale.
Creating effective content and product personalization
Our scraping technology ensures that the latest and greatest content and products, with timely in-stock and other updates, are considered in your personalization placements.
product recommendations
Our user-friendly template designer and algorithm selection tool allow marketers to build and test placements against one another from both a design and selection perspective.
Learn more about using BlueConic for personalized content recommendations and .
View ArticleBlueConic offers a range of features to implement personalization and recommendations. In all recommendation implementations, there's an explore-exploit tradeoff. When you implement recommendations, it's best to start with a comprehensive exploration phase to avoid ending up in a “ local maximum ” which is just a mathematical way of saying an artificial peak in performance.
1. Exploration Phase
It's important to try at least a handful of different variants with different algorithms to ensure that the data BlueConic gathers during this period is sufficiently varied.
We usually recommend starting with a number of variants with a single algorithm configured for each variant. Examples of algorithms you might select are “Breaking news,” “Viral news,” “Look-alike articles/products,” and “Recent high CTRs.” This quickly reveals which algorithms work well for that specific customer and provides valuable data to determine the ideal algorithm combination.
Once the recommendation dialogues have racked up a number of clicks, BlueConic can start analyzing the recommendation click data to determine if a specific algorithm combination would have resulted in even more clicks. We will describe this process in more detail later on in this blog post. Once BlueConic finds an optimal algorithm combination through offline analysis, it's important to test that specific combination against the previously best performing variant to ensure it's actually performing well in practice.
Example content algorithms
Example product algorithms
Let us know
See BlueConic recommendation algorithms for details on how BlueConic develops lists of personalized content or products to recommend.
2. Exploitation Phase
During the exploitation phase, use what you learned during the exploration phase to get the maximum amount of value out of the BlueConic recommendations engine. This means turning off all variants except the best performing one.
3. Continuous Improvement Phase
Our most successful BlueConic customers are continuously improving the quality of their recommendations. Once you've figured out the best algorithm combination across all visitors, it's time to start thinking about specific audience segments that would benefit from recommendations specifically tailored to them.
The rest of this post examines methods for evaluating and optimizing algorithm the performance of content and product recommendations.
Kernel Density Estimate
This graph shows the kernel density estimation of the number of recommendations that were clicked versus those that were not clicked for a specific algorithm. This graph shows that if the look-alike score is low (that is, the recommended content is very different from the content on the current page), the probability is a lot higher that the visitor will not click the recommendation. However, once the look-alike score increases, the roles reverse. This means that the look-alike algorithm is probably a great addition to our final algorithm combination.
The next methods are a little more complicated, so indulge us in an analogy first. Let's say you apply for a job in maritime depth estimation, and as a result, you are sent to the middle of a lake in a rowboat to find the deepest point of the lake. After cracking open a beer (you're on a boat, after all) you use a piece of lead on a line to determine the depth on a number of random locations on the lake. When you compare your measurements, you notice that the deepest of your measurements has comparatively little vegetation, more fish, and the water has a darker color. Using this information, you gradually work towards a location with even fewer plants, more fish, and dark blue water. At some point you notice that not all fish like really deep waters, which means the deepest waters do not contain more fish than closer ashore, but still more fish than the shallowest points of the lake. Using this process, you finally end up in a place on the lake with a medium amount of fish, very dark water, and no vegetation at all.
The fish, vegetation, and color of the water in the story are our recommendation algorithms, while the depth of the lake is the quality of our recommendations with that algorithm combination. The quality of our recommendations is measured as the mean reciprocal rank of our recommendations based on the historical data. For all sets of 5 recommendations where a visitor actually clicked one of them, we determine the location of the clicked recommendation within these 5 recommendations. If the clicked article is the first recommendation, the score is 1; if it comes in second, the score is 1/2; and if it comes in fifth, the score is 1/5. We try to maximize the mean of all these scores (or: reciprocal ranks), which is called the mean reciprocal rank. The idea behind this is that the algorithm combination sorts all available articles by the probability that they will be clicked by the visitor, ultimately showing the top 5 articles to the visitor.
BlueConic currently has 11 recommendation algorithms, which can each have 21 different values between 0 and 10, which means there are 350,277,500,542,221 possible combinations. Even if we could evaluate a million algorithm combinations on all historical data every second, it would still take almost a dozen years to try each algorithm combination; that’s why we have to be a bit smarter than just randomly trying algorithm combinations. This is where the method to gradually move to the deepest part of the lake comes in.
Convergence
The convergence graph shows that we're gradually finding deeper and deeper parts of the lake, until we find the deepest part. When an optimizer has found the best possible solution and keeps trying similar algorithm combinations without making any more progress, we say that the optimizer has converged. We usually want to see that the last part of this graph is flat for a while. If the graph was still declining we should still take more measurements, since it looks like spending more time optimizing the algorithm combination will still pay off.
Evaluations
These graphs are basically maps of the bottom of the lake and are based on the random samples we've taken. In reality, the lake is of course multidimensional: that's why it's represented by a number of separate images where the axes are different recommendation algorithms. The dots in these images are all the probes where we used our piece of lead on a string to measure the depth of the lake, i.e. calculated the mean reciprocal rank for a specific algorithm combination. The color indicates the score for that specific algorithm combination, with a lighter color representing a higher mean reciprocal rank.
The histogram in this image shows the number of times we've tried a specific setting of the recommendation algorithm slider.
Objective
Based on our probes, a depth map is generated. The lighter colors represent areas with a higher mean reciprocal rank. In the line charts on the right you can see how the setting of a specific algorithm slider influences the mean reciprocal rank.
Using recommendations is just one of the many powerful ways to put the data you collect in BlueConic to work delivering more effective, more relevant interactions with your customers. if you’d like to learn more.
View ArticleBlueConic offers a variety of content and product recommendation algorithms to help you deliver personalized, one-to-one content and product recommendations based on individual customers' or visitors' behaviors, interests, and preferences.
To activate personalization recommendations, you use toolbar plugins for product recommendations or content recommendations.
Apache Spark API for collaborative filtering
To calculate the optimal items to recommend for personalization, you can choose the strategy that best fits your content and marketing campaign. This article provides notes on how the recommendation algorithms work. To add recommendations to your pages or app, follow the steps for Content recommendations or Product recommendations.
Breaking news / Top products (based on the "RECENT_VIEW" field)
Use the breaking news or top products algorithm to boost the articles or products that are most viewed during a timeframe you define. Algorithm notes:
Independent of profile
Based on statistics of the last X hours (default is 5 hours)
Content items and products are boosted based on the value of the statistics field “view,” which is incremented whenever the article or product page is viewed (independent of recommendations). You can set the algorithm timeframe in the content collector or product collector connection.
Viral news / Viral products ("RECENT_ENTRYPAGE")
Use the viral news or products algorithm to boost the articles or products that are most used as a landing page during the defined time frame.
Independent of profile
Based on statistics of the last X hours
Items are boosted based on the value of the statistics field “entrypage.”You can set the algorithm timeframe in the content or product collector connection.
Recent high CTRs ("RECENT_CTR”)
Use recent high CTR to boost the most clicked-through articles or products from BlueConic recommendations during the defined time frame.
Independent of profile
Based on statistics of the last X hours
Items are boosted based on the value of the statistics field “click” (someone clicks a content item or product in a recommendations dialogue) divided by the value of the field “recommendation_view” (an item is recommended).You can set the algorithm timeframe in the content or product collector connection.
Same category (“SAME_CATEGORY”)
Use same category to boost articles or products of the same category as the page the visitor is currently watching.
Independent of profile
Independent of statistics
Items are boosted based on the values of the “categories” metadata field of the “current item” versus the categories of the other items. If items have multiple categories, the score is higher if they have more categories in common.
Look-alike articles / Look-alike products ("LOOK_ALIKE")
You can use the look-alike articles or products algorithm to boost articles or products that have similar content to the one someone is currently viewing.
Independent of profile
Independent of statistics
Look-alike algorithms use a TF-IDF weighting factor that measures term frequency and significance to determine which items are most similar to the current item.
This determination is based on the words in the product or content item's “name,” “description,” and “text” metadata fields.
Recency ("RECENCY")
Use the recency algorithm to boost the most recently added articles or products.
Independent of profile
Independent of statistics
This personalization algorithm uses the value of your content items' or products' “publicationDate” metadata field to boost items. Newer items score higher than older ones.
Collaborative filtering (“COLLABORATIVE_FILTERING")
Collaborative filtering algorithms make personalized product and content recommendations for individuals based on the behavior of other people who view the same articles or products. Some algorithm notes:
Independent of statistics
Dependent on the items the individual has viewed, put in a shopping cart, or ordered
Weight values: view=1, shopping cart=5, order=25
Operates with a ramp-up time, taking time to account for the interests of other viewers
This results in an affinity between profiles and items, which is used in a collaborative filtering model, as described in the .
Same interest ("INTEREST")
The same interest algorithm boosts articles or products that are similar to those the customer or visitor already viewed, based on the values of the item's “categories” metadata fields.
Independent of statistics
Dependent on the items the customer or visitor has viewed
Operates with a ramp-up time
Seen articles / Seen products ("RECENTLY_VIEWED")
This BlueConic personalization algorithm boosts articles or products the customer or visitor recently viewed.
Independent of statistics
Dependent on the items the customer or visitor has viewed
The items the individual most recently viewed are boosted the most. You can use this algorithm to create a “last viewed articles” or "last viewed products" overview.
Shopping cart-based recommendations
For personalized product recommendations, there are similar algorithms for items the customer recently placed in the shopping cart and items they have recently ordered: "RECENTLY_SHOPPINGCART" and "RECENTLY_BOUGHT", as well as algorithms that boost products most often placed in the cart or most frequently bought, during a certain timeframe ("MOST_CARTED" and "MOST_BOUGHT").
View ArticleA BlueConic segment is a dynamic grouping of your customers or visitors characterized by a defined set of attributes, interests, behaviors, preferences, or demographic, psychographic, or technographic properties.
Known and anonymous users can be segmented with a single filter or a complex set of filters. So you can engage with your users at the right moment with a meaningful and relevant dialogue. Customers and users of your online channels can belong to multiple segments. For example, a single user might be included in the segments "under 35 years old," "interested in football," "referred by social media," and "read December newsletter."
BlueConic's dynamic segmentation
In BlueConic, segmentation is dynamic, which means that the latest updates of profile property values are used to determine if a visitor falls in a specific segment in real time.
Organizing and managing segments
Select Segments from the BlueConic navigation bar to see a display of all existing segments for your BlueConic environment. You can use the search box to narrow the display by keyword, for example, to find segments related to subscribers.
See " Object Navigation " for an in-depth discussion of navigating the display.
Creating a segment
To create a segment, select[Add Segment]at the top of the Segments window. A new segment appears and you can enter a name for the segment.
At the top of the screen you enter a name for the segment and next you can see the number of profiles it currently contains. When you first create a segment, and there are no restrictions in place yet, you see the total number of available profiles.
Note that you can also create a segment using the Segment Overlap Insight.
Editing segment metadata
The top area of the screen shows the segment's metadata. Enter a name for your segment.
You can edit the following metadata:
Favorite: You can mark the segment as one of your favorites. Click the star icon to favorite or unfavorite the segment.
Labels: By adding labels to an object you can easily group related segments and make managing and retrieving objects easier. See labels for more information.
Description: Add a short description of the segment and its purpose.
Edit rights of the segment: Select the domain(s) to which a user must belong to in order to modify this segment. If more than one domain is selected, the user must belong to all domains in order to be able to modify this segment. If no domains are selected, any user can modify this segment. See Domain-based permission for more information.
To save screen space, you can hide or show the metadata by clicking the top separator line with the [-] or [+] icon on it.
You can now further specify your segment by selecting one or more conditions or filters. See Segment Filters.
Defining a Segment
Segments collect customers or visitors together based on the values stored in their profile properties and group properties. To create a new segment, you start by selecting conditions customers have to meet to be part of the segment. These conditions might be another segment, a privacy or consent marketing objective (such as a email opt-in), a profile property, or a group property.
If a matching profile property does not exist, you can create one. (Don't worry about picking the correct property, because it's easy to add or remove profile properties after your initial choice.)
BlueConic displays a list of most used profile properties and the list of all other profile properties. You can also search for a particular profile property by typing in the search box. This automatically filters both lists to theprofile properties that match your search.
Once you have located the profile property that you want, select it to start building the segment.
To flesh out a segment, you can filter for specific profile property values. When you select a profile property, the values you can filter on display on the right side:
In this case, the filter displays a list of values found in profiles, ordered by the number of profiles that contain that specific value. You can even filter by another value if no profile contains it yet. Other types of profiles will display other filter information and allow you to filter on dates or numeric values. Read more on segment filters.
In the example above, we picked "mlb". Note, that as you restrict the values in the segment, its size is being updated at the top of the page.
Let's expand this segment by hovering over the blue area of the chosen profile property.
Two new buttons appear: "+ AND" and "+ OR".
Click on "+ AND" if you want the segment to match visitors that match both your first property filter AND your second property filter. You can also choose to set conditions for Objectives, such as privacy opt-in, email consent, etc.
Click on "+ OR" if you want the segment to match either your first property filter OR your second property filter.
In our case, we want to segment on visitors who like baseball AND are from Boston, so we click "+ AND". A popup appears to select the next profile property we want to filter on:
In this case, we want to use the "City (All)" profile property of visitors, so we select that. As a result the segment overview is updated with the new profile property:
As you can see the target Objectives and the two profile properties "Favorite Sport" and "City (All)" are connected by "AND", meaning the segment combines the consent objectives with two profile property filters by requiring each of them.
Note that upon specifying the value "boston" the value of the segment at the top of the page updates to show the number of profiles in the entire segment, i.e. profiles with the correct consent values combined with Favorite Sport "mlb" and City (All) "boston". Also, the numbers that are being shown in the bars take the entire segment into account; there could very well be over 500,000 visitors with "boston" in their profile, but only 127,630 of them also meet the consent requirement and have "mlb" as favorite sport.
If you want to fold the filter information, click on close icon in the top right of the screen. You now see an overview of the segment definition:
On the left you see the objectives and profile properties with their connection (AND or OR) and the conditions set for each of them.
If you are content with the segment, you can now save the segment.
To expand the segment, hover over an objective or profile property and click "+ AND" or "+ OR". Or, to remove an objective or profile property, hover over it and click the "x" button that appears on the right of the profile property.
If you want to adjust a filter, click on the profile property or the conditions and the filter screen appears again.
Extending existing segments
You can also use the segment definition you just created to extend an existing segment. Select Extend existing segment in the upper right corner and choose existing segments to serve as the basis for the new segment conditions. Only profiles that are members of all the selected segments and meet the objective and profile property conditions are part of the new segment.
For details on filtering based on different conditions and how to configure them, see Segment Filters.
Modifying, copying, or deleting a segment
As with other BlueConic objects, a segment can be saved, copied, or deleted using the save button. See Save, Save As, and Delete for an in-depth discussion.
Exporting segment data
Segment data can be exported in comma-separated value (CSV) format. This makes it possible to examine segment data in external applications. The export file contains a list of all profile IDs that match each segment together with the specified value for each targeted property. The Export function can export up to a maximum of one million profiles. If the segment contains more than one million profiles, only one million profiles will be exported. There is no way to control which records are exported. To access all profiles in a segment larger than one million profiles, you will have to use the BlueConic REST API.
To export segment data, choose the option "Export" from the Save button drop-down menu.
Select where you want to save the file. By default the name of the export file is
"BlueConic_Export_[segment name]_[date (yyyymmdd)]_[time (hhmm)]".
Dates will be exported as UNIX millisecond timestamps in UTC. In Excel, you can convert these to regular Eastern (GMT+5) times with a formula:
=((((A1 / 1000) / 60) / 60) / 24) + DATE(1970, 1, 1) - (5 / 24)
Be sure to format the cells with the formula as date.
Creating an inverse segment
Sometimes it can be helpful to create an inverse segment, which is a new segment containing all the profiles not in the current segment. Select Create inverse from the Save drop-down menu to create a new inverse segment. It is named "Visitors not in segment [current segment name]."
Statistics
In the right-hand sidebar, the "statistics" widget is displayed. It shows the number of profiles in the selected segment over time.
By clicking on the graph in the sidebar widget, a lightbox with a detailed view of the graph is displayed. The X axis of the graph represents the time period. The Y axis represents the number of profiles that belong to the segment. If the line in the graph contains points that stand for individual days or months, you can hover over it to see the statistics for that period of time. For example:
Graph options
You can change the view of the line graph by adjusting the range of values that are shown as well as the time period. You can also export the values shown in the graph in order to inspect them in external applications. See Graph options for complete information on the graph options that are available.
Related items
In the right-hand sidebar, the Number of Profiles, Objectives, and Related items widgets are displayed. You can use Objectives the see which privacy or consent objectives are related to this segment or to add the segment to an objective.
The Related items widget shows the other objects in BlueConic that are directly related to the segment you are managing. Segments can have the following types of related items:
Connections: The BlueConic connections that import or export profiles in this segment.
Dashboards: The dashboards that show insights that measure or report data about this segment.
Dialogues: The BlueConic dialogue interactions that use this segment on the Who-tab.
Dialogue variants, or optimizers: The dialogue optimizers that use this segment on the Who-tab of a BlueConic dialogue.
Profile or group properties: The profile properties and group properties that this segment uses as a condition.
View ArticleAs we look ahead to 2020, we also celebrate the BlueCrew's news and accomplishments in 2019. Our product and engineering teams released AI Workbench as well as dozens of new features, plugins, connections, and enhancements this year. Our marketing team has been busy with webinars, events, BlueConic customer stories, and timely blog posts.
BlueConic customers have quickly come to rely on AI Workbench, with 25\% of BlueConic sites adopting AI Workbench this year. Nearly 10\% of customers are already tracking events and transactions on the BlueConic event timeline.
We look forward to seeing how our customer community continues to adopt new features in their targeted marketing campaigns in 2020. Contact us to learn more or to share how you're using the latest and greatest BlueConic features.
Use AI Workbench to apply AI to your marketing data
Enable consent management
This year, we added AI Workbench to bring efficiency to the way marketing and data science teams work together.
With AI Workbench, you can apply AI marketing models to your BlueConic profile and event data.
New out-of-the-box notebooks let marketing teams use AI marketing models to calculate CLV and RFM without writing any code.
Full API and Python notebook support for data scientists to create and run custom AI models against your BlueConic customer data.
New Insights for displaying results of AI Workbench models, to visualize results for all notebook cells, or a single cell.
Enhanced Timeline feature to track orders and events
With enhancements to track and activateorders, events, and transaction data,you can better understand your customers' buying behaviors and take action in real-time. Enhancementsinclude:
Importing and tracking product orders and transactions
Viewing Timeline events on a profile's timeline
Detecting shopping cart data with the Product Collector
Creating personalization based on shopping cart and order behavior with new product recommendation algorithms based on products carted or bought most often
Importing transactional data via SFTP connections with out-of-the-box Timeline event types
Group profiles by household, company, or account
New this year is a grouping feature in BlueConic for organizing and segmenting profiles by households, companies, accounts, or a custom group you define.
Use SAML-based SSO for BlueConic user logins
Now you can enable your BlueConic users to log in to BlueConic via SAML-based single sign-on providers such as OKTA, OneLogin, Google G Suite, etc.
Send emails with dynamic content updated at open time
Our new open-time email recommendations feature lets you send recommendations via email that update when your customers open their email, taking into account the latest up-to-the-minute actions and preferences.
Learn more about sending Open-Time Email Recommendations with BlueConic and contact your customer success manager for help with setup.
Manage privacy for multiple legislation zones
With support for multiple privacy legislation zones, you can use BlueConic manage customer privacy and consent for GDPR in Europe,CCPA in California, PIPEDA in Canada, SB220 for the state of Nevada, and the potential upcoming NYPA legislation in New York State.
New capabilities for Profile data and Segments
Added Behavioral profile data to the Profile summary page
New default segment, Known visitors
Easier click and conversion tracking in forms
Updates to how BlueConic managesfirst-party data with ITP and alternatives to cookies
The General Settings subscription page shows an expanded set of BlueConic usage metrics to help you track data operations, data storage, and profile counts in greater detail over time.
New features for events, transactions, and order data
The new BlueConic Profile Timeline illustrates events associated with an individual profile, including transactions, email events, and custom events.
Updates to the SFTP Connection make it easier than ever to add events, import orders, and synchronize your customer data with your martech stack via CSV.
New BlueConic Connections in 2019
Our developers created several new connections this year -- including a brand new SendGrid connection, coming this month!
BlueConic to BlueConic connection
Active Campaign connection
Higher Logic connection
LiveRamp connection
SendGrid connectioncoming soon!
New Insights for visualizing your data
The new Profile Recognition Dashboard shows the percentage of your profiles that are known by a unique identifier. Use it to analyze how to increase your customer recognition ratioover time.
The Profile identifiers insight provides important metrics showing how many of your profiles are known by unique identifiers.
New AI Workbench insights to visualize the results of AI marketing models
New marketing metrics tracked and displayed in the Dialogues Table and Variants Table insights, including direct and indirect conversions
Recommendations insight measuring your top products and content items
New Segment Profile Count insight
Top BlueConic webinars of 2019
AI for Marketing: Why It’s Overpromised and Underdelivered, Until Now
The Death of Third-Party Cookies: What It Means for Your Marketing
Data Privacy Laws: Compliance and Consent Management Tips for Marketers
2019 Highlights from the BlueConic Blog
Behavioral Segmentation Examples and Insights
Customer Lifecycle vs. Customer Journey, Explained
CCPA: Understanding the California Consumer Privacy Act
AI Marketing Use Cases for Everyday Marketers
BlueConic Use Case Playbooks
As you plan for 2020, perhaps you're starting to think about new ways to use your CDP and first-party data. To help you get started, check out our BlueConic playbooks with step-by-step instructions for implementing key use cases. If you have any questions, please reach out to your CSM.
Accelerate lead generation campaigns
Reduce ad waste
Prevent and recover funnel abandonment
Use metering to improve conversions
Deliver 1:1 content and product recommendations
Build a single source of customer data truth
View ArticleThe Profile Property has value Insight displays the values of a profile property for all profiles that fall within the selected segment. The values can be shown in a pie chart or a horizontal or vertical bar chart.
For example, this pie chart shows all the visited channels for a segment called "All Visitors." The values add up to more than 100\% because many people visited more than one website.
Hovering over sections of these charts shows the name and profile data underlying that section.
Pie Chart
Chart
At the center of the pie chart is the number of unique profiles. Each slice of the chart depictsa value of the selected profile property in the chosen segment, with the percentage showing the number of occurrences of this value with respect to other values in the same profile property. Hover over the individual slices of the pie chart and click to see the details for the specific value of the profile property.
Legend
To the left of the pie chart is a legend that explains the color mappings. By default only the top six values are displayed. All other properties are aggregatedunder "Other." Click More todisplay more values than the initial six.
Horizontal Bar Chart
X axis
Displays the number of profiles in the chosen segment that contain the value. Hovering over a bar shows the values for this section of the chart.
Yaxis
Displays the profile propertyvalue.
Zoom sliderand search bar
On the side of the bar chart is a zoom slider. When there are many values for the profile property, you can drag the zoom sliders to select a specific segment of values to display.You can also use the Search box to find a specific bar; it will show in a contrasting color.
Vertical Bar Chart
X axis
Displays the profile propertyvalue.Hovering over a bar shows the values for this section of the chart.
Yaxis
Displays the number of profiles in the chosen segment that contain the value.
Zoom slider and search bar
On the bottom of the bar chart is a zoom slider. When there are many values for the profile property, you can drag the zoom sliders to select a specific segment of values to display. You can also use the Search box to find a specific bar; it will show in a contrasting color.
Configuration
You can adjust how the Profile Property has value insight displays, switching back and forth between the pie chart and the vertical and horizontal bar charts. In the top right-hand corner of the insight are a set of tools.
Use the download tool to download a data file showing the values for the current profile property, number of profiles with each value, and the relative percentage of profiles that have a value for this profile property.
Use the link icon to see the associated profile property and segment.
Use the settings icon to configure how the graphs display for this insight.
Use the X icon to delete this insight.
Profile property (required)
Select the profile property that should be inspected to find out how often a value is present in that profile property. Only profiles that are present in the selected segment will be inspected.
Segment
The "Don't use Segment" option displays all userswho have a value for the selected profile property. If the "Use Segment" option is selected and a segment is entered, only profiles that belong to the segment are used to check how often a value is used for the profile property.
Visualization
Select the visualization you prefer: pie chart, horizontal bar chart, or vertical bar chart. For horizontal and vertical bar charts you can choose the color used to display your data.
Ranges
Profile properties with numerical values get an extra option calledRanges. Leave the Divide values in ranges box unchecked if you want to see all values, or select the box to define a table of ranges. You can add labels and minimum and maximum values for numerical ranges.
You can freely rename these ranges or change the numbers. Note that the maximum of one range and the minimum of the next range are kept in sync automatically. To add another range, click Add Range.
View ArticleBlueConic recommends using the Chrome Browser for developing and testing BlueConic applications.
When you open a website within BlueConic (e.g. in the Dialogues editor or in the BlueConic Simulator) you might trigger a Chrome browser security warning against opening HTTP content in an HTTPS browser window. In most cases, BlueConic detects this and instructs you to allow the viewing of mixed content.
How to allow Chrome to display insecure HTTP content
We recommend you use the Chrome browser for developing and testing in BlueConic. Follow these steps to enable Chrome to display HTTP content in BlueConic.
At the top of your Chrome browser window, click the lock icon to the left of the URL.
Select Site settings.
At the bottom of the Settings page, under Permissions, select Allow forInsecure Content.
Return to the browser tab containing BlueConic and click to reload the browser.
Your browser displays a red "Not Secure" alert noting that HTTP content is being displayed within an HTTPS page.
What causes this warning to occur?
BlueConic runs in secure mode (HTTPS) by default.Because BlueConic potentially can deal with sensitive data (such as data from your customers or visitors), the BlueConic server can only be reached via a secure connection, to make sure that all traffic to and from the server is encrypted and secured.
The warning in BlueConic occurs when you try to open a website that does not support HTTPS secure mode and is available only in HTTP mode.
When you try to open a nonsecure (HTTP) element within the HTTPS environment, your browser considers this as a potential security risk, and will not automatically open these http elements, unless you explicitly allow your browser to do so.
To prevent this message from occurring, BlueConic will first try to access the site via HTTPS, but if this is not available, or if some elements on your site are not available through HTTPS, you will get this warning.
What risk do I take, when I allow my browser to continue?
The actual risk is not any different than if you opened this site in a separate tab or in a separate browser outside BlueConic. In those cases you would not get any warningsat all. So there is absolutely no extra security risk when you proceed to load the HTTP-site.
BlueConic only interacts on the page locally via the BlueConic script. Everything that is on the pages that you load can not make any connection back to BlueConic. This means thatthere is no risk that BlueConic data could be accessed by insecure elements on external websites that you are viewing in the inline editor, the visual picker or the simulator.
Do I need to allow this every time?
Changing the browser settings to enable Chrome to display insecure HTTP content on HTTPS pages affects Chrome's display for the current BlueConic user, for the current URL (visible at the top of the Site Settings window in Chrome), on the current device.
View Articleprivacy management What: The BlueConic Salesforce connection allows you to synchronize customer profile data between BlueConic and Salesforce (back and forth) in real time.
About BlueConic: The BlueConic customer data platform harnesses the data required to power the recognition of an individual at each interaction, and then synchronizes their intent across the marketing ecosystem.
Why: Integrating your CRM data into the BlueConic customer data platform provides prime material for segmentation and personalization. BlueConic features a unique data collection engine that captures data at the customer level for known and anonymous users. For known users, or once a user becomes known, having this data in your CRM will arm your call center and other communication platforms with relevant details about your customers' explicit and implicit intents.
About the BlueConic Salesforce Connection
The Salesforce customer relationship management system provides a service that collects sales lead and contact information and stores it in rich visitor profiles. BlueConic is able to synchronize its own information with Salesforce using the BlueConic Salesforce Connection, enriching the available information on both sides. The Salesforce Connection provides matching between BlueConic profiles and Salesforce Leads, Contacts, or Person objects, allows asymmetric synchronization, supports Lead creation, and lets the sales team see live BlueConic information in Salesforce.
The following components are required in order to configure the Salesforce connection in BlueConic:
API Access in Salesforce ( What Salesforce editions have API Access? )
The BlueConic managed package in Salesforce, available from the AppExchange
Setting up the BlueConic Salesforce connection
Setting up and running aconnection between BlueConic and Salesforce consists of several steps:
Create a Salesforce connection
Configure BlueConic API Access to allow Salesforce to connect to BlueConic
Set up Salesforce remote site settings
Install the Salesforce managed package to add BlueConic functionality to Salesforce
Set up your credentials in Salesforce
Configure Salesforce connection settings to authorize BlueConic to connect to Salesforce
Configure the Salesforce page layout
The following sections explain these steps in more detail. See the Synchronization section for notes on how data is exchanged between the two systems.
Create a BlueConic Salesforce connection
Start by creating a Salesforce connection in BlueConic:
In the BlueConic navigation bar, select Connections.
Click [Add connection].
Select "Salesforce Connection" to create a new Salesforce connection.
Enter a title for the connection, e.g. "Salesforce."
Once you have created a Salesforce connection in BlueConic, you can start to configure it.
Configure BlueConic API Access
Salesforce needs to be allowed to connect to BlueConicto instantlysend updates from its side or to retrieve and display information.
Think up and enter a new Consumer key. This key will be used to set upa secureconnection between BlueConic and Salesforce. The key can contain uppercase, lowercase, and underscore characters and numbers, for example: "2019Salesforce" or "My_CRM_system."
Copy and paste your Consumer Key to a temporary note pad, as you will need it to configure Salesforce later.
Click [Generate secret] to generate a private secretkey based on yourconsumer key.
Copy and paste your Consumer secretto a temporary location; you will need it to configure Salesforce later. Do this now, because the secret will be hiddenonce you navigate away fromtheconnection!
Optional: Click [Add IP range] if you want to limit access to the BlueConic API to requesting host(s) with IP addresses in a certain range.
Click [Save] to store your changes.
Observe the browser URL. Copy the connection id from the browser URL and paste it to a temporary location. The id will look like "d5c24bf2-b980-4d28-ba7c-2f118e42d0f2" and consists only of letters, numbers, and dashes (sono "=" or "&").
You can always generate a new secret key. Doing so will invalidate all previously generated keys which will stop an already active connection from working.
Now that you have set up BlueConic API Access, Salesforce will be allowed to connect to BlueConic. Next you set up that part of the connection in Salesforce.
Set up the Salesforce remote site
With the initial setup on the BlueConic side done and the important data copied in your notepad, now you need to inform Salesforce that you are going to work with a remote site.
Open Salesforce.
In the quick search field above the left menu pane, type "Remote Site" and select "Remote Site Settings."
Click "New Remote Site."
Name the remote site, for example "BlueConic."
For remote site address, enter your BlueConic URL (e.g. "https://taylorshop.blueconic.net/").
Make sure the remote site is active.
Save your settings.
Install the Salesforce managed package
Next, install and configure the Salesforce managed package for BlueConic. This will allow Salesforce to send information to BlueConic.
Find the BlueConic app on the AppExchange or click the button below, click "Get It Now," and follow the instructions.
Install the package for all users:
Set up your credentials in Salesforce
After the installation you need to fill out the details that you copied and pasted to your notepad earlier:
Consumer key: Enter the key that you thought up and copied.
Consumer secret: Enter the secret that you generated and copied.
Server: Enter the BlueConic URL (e.g. "https://taylorshop.blueconic.net/").
Connection: Enter the id of the connection in BlueConic (e.g."d5c24bf2-b980-4d28-ba7c-2f118e42d0f2") that you copied.
Click [Save] to finish configuringthe managed package.
Salesforce can now send information to BlueConic, although it can't receive anything from BlueConic yet. We will configure the necessary connection settings in the next step.
Configure the BlueConic Salesforce Connection settings
To be able to send information from BlueConic to Salesforce, BlueConic needs to be authorized. We recommend that you not use your own user but instead use a separate user for authorizing BlueConic. This way your Salesforce reports will not be affected. Using a separate user may require you to adjust assignment rules or other Salesforce settings.
Take the following steps:
Log out of Salesforce.
Click the button [Connect with Salesforce].
A popup opens where you can log in to Salesforce. Log in with the separate user (recommended), or with your own user. After you log in, Salesforce will ask for permissions.
Click "Allow Access."
If you want to limit the information exchange to customers or visitors in a specific BlueConic segment, select a segment other than "All Visitors."
Save the connection.
Your connection should not show an error, which means that BlueConic can now send updatesto Salesforce.
To improve to exchange profile data and prevent timeouts, you should set up Remote Access within Salesforce.
Configure the Salesforce page layout
Technically you are done now;two-way communication between Salesforce and BlueConic is now possible.
However, with a little extra configuration you can give your Sales team advanced access to BlueConic information without having to synchronize all data to Salesforce.
The Live Profile Viewer is an optional object that you can add to a page layout. As the Salesforce page is being loaded, it will request live information from BlueConic and make it available for inspection.
Set up the Live Profile Viewer as follows:
In Salesforce, click"setup" in the top right.
In the left menu select Build > Customize>Leads>Page Layouts.
Click "Edit" for the layout that you want to add the Live Profile Viewer to.
From the "Fields" bar, drag and drop the element "Section" to the "Lead Detail" block.
In the popup:
Enter a name for the section, for example "BlueConic Live Profile viewer."
Select 1-column Layout.
Click [OK].
In the layout bar, scroll the menu in the left down to select "VisualForce pages."
Drag the "LeadProfile" page to the newly created Section.
Save the layout.
Hover over the blue LeadProfile area of the BlueConic Live Profile and click the wrench icon in the top right to modify its settings.
Save the layout.
Repeat this for all layouts and also for Contacts.
Using the Salesforce connection
Now that you have a working connection between BlueConic and Salesforce, it is time to define exactlywhatwill be synchronized between the two systems. You can determine:
What data to collect from Salesforce
What data to deliver to Salesforce
When to create a new Lead in Salesforce
How to match profiles in BlueConic to Leads, Contacts, or Persons in Salesforce
What BlueConic information to show in the Salesforce page layout.
The following sections delve deeper into your options for synchronizing BlueConic and Salesforce.
Collect settings
The collect settings allow you to determine which fields will be collected from Salesforce and how they will be mapped to BlueConic profile properties. You can add variables by clicking the [Add Variable] button.
Collecting variables is optional; if you don't need anything from Salesforce in BlueConic profile properties, it is okay to leave this section empty.
Each variable has the following options:
Salesforce Object Type(s)
Indicate whether the field belongs to a Lead, Contact, Person, or any combination of these in Salesforce.
Salesforce Field Label
Select the field from Salesforce. Note that availability of fields is dependent on the selected object types.
Profile Property
Select the BlueConic profile property into which the Salesforce value should be collected by typing its name or by using advanced search to find it.
Merge Rule
The merge rule setting determines how a value collected from Salesforce will be stored into the BlueConic property. These are the options:
Set: Copy the value from Salesforce exactly to the profile property, overwriting the previous value.
Set if empty: Copy the value from Salesforce exactly to the profile property but only if it is empty. If the profile property already has a value, do nothing.
Add: Add the value from Salesforce to the list of values already in the profile property if it hasn't been added yet, omitting duplicates.
Sum: Numerically add the value from Salesforce to the value in the profile property. If the profile property was empty, it will be regarded as value 0. Only works for profile properties and values that contain integer numbers.
To duplicate a variable click the copy icon, and to delete a variable click the delete icon in the right-hand column.
Deliver settings
Use the deliver settings to determine which BlueConic values will be delivered to Salesforce and to which Salesforce fields. You can add variables by selecting the type "Profile Property," "Segments" (to deliver the list of segment names a profile is part of), or "Permission Level" (to deliver a profile's permission level) and clicking the [Add Variable] button.
Warning
Make sure you always deliver all fields that are marked as "mandatory" in Salesforce! If you leave out mandatory fields, Salesforce will block the connection from creating any new leads because mandatory information is missing.
Delivering variables is optional; if you don't need anything from BlueConic in Salesforce, it is okay to leave this section empty.
Each variable has the following options:
Variable
Select the BlueConic profile property whose value should be delivered to Salesforce by typing its name or by using advanced search to find it. If you added a variable of type "Segments" or "Permission Level" the variable has already been preselected for you.
Salesforce Object Type(s)
Indicate whether the field belongs to a Lead, a Contact, a Person, or any combination of those in Salesforce.
Salesforce Field Label
Select the "Field Name" from Salesforce. Note that availability of fields is dependent on the object types you selected.
Merge Rule
The merge rule setting determines howa value from the BlueConic profile property will be stored into the Salesforce field. These are the options:
Set: Copy the value from the profile property exactly to the field in Salesforce, overwriting the previous value. If the profile property contains a list of values and the Salesforce field is a text field all values will be concatenated into one string with a semicolon as separator (e.g. "value a; value b; value c").
Set if empty: Copy the value from the profile propertyexactly to the field in Salesforce butonly if it is empty. If the profile property already has a value, do nothing.
Add: Add the value from the profile propertyto the list of values already in the field in Salesforceif it hasn't been added yet, omitting duplicates. The Salesforce field should be a Picklist (Multi-Select). Due to constraints in Salesforce, there can only be a maximum of 100 value entries in the list and each value can only be 35 characters long.
Sum: Numerically add the value from Salesforce to the value in the profile property. If the profile property was empty, it will be regarded as value 0. Only works for profile properties that contain numbers.
To duplicate a variable, click the copy icon, and to delete a variable click the delete icon on the right-hand side.
Creating new leads via the Salesforce Connection
In the creation of new leads section, you decide when it is okay for BlueConic to create a new Lead object in Salesforce and subsequently deliver all information.
Select all required profile properties; these will need to have a value in BlueConic before a new Lead is created in Salesforce.
This section is optional; if you don't want BlueConic to create any new Lead objects in Salesforce, do not select any profile properties.
Activate the checkbox if you want to automatically assign leads according to the Salesforce lead assignment rules.
Matching BlueConic profiles to Salesforce leads or subscribers
In this section, you specify the matching criteria for when a profile in BlueConic matches a Lead, Contact, or Person in Salesforce. Do this by adding variables that will match BlueConic profile properties to Salesforce fields.
Each variable has the following options:
Profile Property
Select the BlueConic profile property whose value should be matched to Salesforce by typing its name or by using advanced search to find it.
Salesforce Object Type(s)
Indicate whether the field belongs to a Lead, Contact, Person, or any combination of these in Salesforce.
Salesforce Field Label
Select the field from Salesforce. Note that this is dependent of the selected object types.
To duplicate a variable click the copy icon, and to delete a variable, click the delete icon on the right hand side.
When you add multiple variables, a match is foundif any of the profile properties matches itsSalesforce field. Synchronization only occurs when a single match is found. When multiple matches are found in Salesforce for a BlueConic profile, nothing will be synchronized.
BlueConic data blocks shown in Salesforce
BlueConic data can enrich the Lead, Contact, or Person detail information in Salesforce by displaying live information from BlueConic. See above on how to configure the Salesforce page layout to display liveBlueConic information. Upon opening the details page in Salesforce, the VisualForce component that displays the blocks requests the most recentprofile information for this particular Lead, Contact, or Person from BlueConic and displays the information. The profile information will berefreshed whenever the page is reloaded.
Select the profile properties that you want to be displayed in Salesforce by searching for them.
You can reorder the blocks by clicking the left or right arrows in the blue bar.
In the Salesforce Lead, Contact, or Person details page, you will see something like this:
The "Segments" and "Other Profile Properties" blocks areadded automatically. "Segments" displays a list of all segments a profile is a member of. In the "Other Profile Properties" field, you can search for profile properties and inspecttheir value.
Synchronizing data between the two systems
As soon as you activate and save the Salesforce connection in BlueConic, scheduled runs will start to synchronize the two systems regularly. Due to restrictions on the number of Salesforce API calls, synchronization from BlueConic to Salesforce is not instant (yet within minutes), and data is pooled to make effective use of the connection. Updates from Salesforce to BlueConic are instant.
Usage notes
These notes describe when the connection runs and how data is matched between BlueConic and Salesforce:
Each time a profile is active on one of your websites, the Salesforce Connection will check whetherone of theprofile propertiesthat is configured under "Deliver settings" or "Match BlueConic profiles to Salesforce leads or subscribers" has changed since the last time the customer or visitor was active.
In BlueConic, profiles that changed are flagged by setting the "Salesforce Update Needed" profile property to "yes."
Every 3 minutes, the connection checks for profiles that have been flagged and sends those in batch to Salesforce.
The profile property that has been selected under "'Match BlueConic profiles to Salesforce leads or subscribers'" is used to match Leads, Contacts, or Persons in Salesforce. Optionally, new Leads are created in Salesforce when no match is found. (You can enable this option using the "Assign leads to marketers in your Salesforce environment" checkbox.)
Matching Leads, Contacts, or Persons are now updated according to the mapping configured under "Deliver settings."
Each time a Lead, Contact, or Person that has been created or updated by BlueConic changes in Salesforce, the matching profile in BlueConic is updated by Salesforce according to the mapping configured under "Collect settings."
Log file
If there was aproblem during synchronization it will be mentioned under "Details".When you hover over a run, a "Download log" icon appears on the right. Click the icon to download the log for that run.
Privacy management
Connectionscan be added to Objectives, allowing forof the information that is being picked up. A connection will only process the profiles of customers or visitors who have consented to at least one of the objectives that the connection is linked to.
View ArticleSalesforce ( www.salesforce.com ) is a customer relationship managementsystem that, among other things, provides a service that collects sales lead and contact information and stores it in rich visitor profiles. BlueConic is able to synchronize its own informationwithSalesforce using the Salesforce Connection, enriching the available information on both sides.
In BlueConic, the Salesforce Connection provides matching between BlueConic profiles and Salesforce lead and contacts, allows asymmetric synchronization, supports lead creation, and lets the sales team see live BlueConic information in Salesforce.
The following components are required to configure the connection:
API Access in Salesforce ( What Salesforce editions have API Access? )
The BlueConic managed package in Salesforce, available from the AppExchange
The BlueConic Salesforce connection plugin (v2.0+)
Setting up a Salesforce connection in BlueConic
To set up the connection between BlueConic and Salesforce, foursteps are required:
Create and authenticate the Salesforce connection
Install the Salesforce managed package with Salesforce
Configure the BlueConic connection to Salesforce
Configure the Salesforce page layout
The following sections explain these steps in more detail.
Create and authenticate a Salesforce connection
To be able to make a connection with Salesforce, BlueConic needsthe "Salesforce" plugin:
In BlueConic, open Settings > Plugins.
Click [Add Plugin].
Search for "Salesforce" in the Add/update plugin window.
Click [Add Plugin] for the "Salesforce" plugin.
Close the"Add/Update Plugin" popup.
Now that the plugin is installed, the connection can be created and configured in BlueConic. Let's start with the Salesforce connection and configure the oAuth parameters:
In BlueConic, open Settings > Connections.
Click [Add Connection].
Select "Salesforce" to create a new Salesforce connection.
Think up and enter a new Consumer Key.
This can be a word, phrase or code that you will use to authenticate the secure connection between BlueConic and Salesforce. The key can contain uppercase, lowercase and underscore characters and numbers, for example: "2020Salesforce" or "My_CRM_system".
Copy and paste your Consumer Key to a temporary notepad, because you will need it to configure Salesforce later.
Click [Generate Secret] to generate a private secretkey based on yourconsumer key.
Copy and paste this Consumer Secretto a temporary location, as you will need it to configure Salesforce later.
Do this now, because the secret will be hiddenonce you navigate away fromtheconnection.
Enter a title for the connection, e.g. "Salesforce".
Click [Save] to store your changes.
Copy the BlueConic URL currently inyour browser to your notepad. The URLwill resemble this example:https://yourserver.blueconic.net/blueconic/static/pages/main.html#id=d5c24bf2-b980-4d28-ba7c-2f118e42d0f2&type=connection
You can always generate a new secret key. Doing so will invalidate all previously generated keys which will stop an already active connectionfrom working.
Install the Salesforce managed package
With the initial setup on the BlueConic side done and the important data copied in your notepad, it is now time to inform Salesforce that you are going to work with a remote site.
Open Salesforce, and in the quick search field abovethe left menu pane, enter "Remote Site" and select "Remote Site Settings".
Click "New Remote Site".
Name the remote site, for example "BlueConic".
For remote site address enter the startof the BlueConic URL that you copied to your notepad earlier (the bit thatlooks like "https://taylorshop.blueconic.net/").
Make sure the remote site is active.
Save your settings.
Next, install and configure the Salesforce managed package for BlueConic and enable it for all users. This will allow Salesforce to send information to BlueConic.
OpenSalesforce and click"setup" in the top right.
Install the managed package for BlueConic by using this link: https://appexchange.salesforce.com/listingDetail?listingId=a0N3000000E0LGREA3
After the installation you need to fill out the details thatyou copied and pasted to your notepad earlier:
Consumer Key: Enter the key that you thoughtup and copied.
Consumer Secret: Enter the secret that you generated and copied.
Server: Enter the first part of your BlueConic tenant URL, which you copied earlier, for example: https://taylorshop.blueconic.net/
Connection: Enter the alpha-numeric code you copied earlier, which ends the URL and does not contain special characters other than dashes. connection id bit of the BlueConic URL that you copied. It will look like this: "d5c24bf2-b980-4d28-ba7c-2f118e42d0f2"
Click [Save] to finish configuringthe managed package.
Salesforce can now send informationto BlueConic, although it can't receive anything from BlueConic yet.
Configure the BlueConic connection
To be able so send information from BlueConic to Salesforce, you need to allow remote access to Salesforce by giving BlueConic the ability to act as a user within Salesforce. This provides access to the Salesforce data you are bringing into BlueConic.
We recommend that you not use your own user but instead use a separate user for authorizing BlueConic. This way your Salesforce reports will not be influenced. Using a separate user may require you to adjust assignment rules or other Salesforce settings.
Take the following steps:
Log out of Salesforce.
Open the Salesforce connection in BlueConic.
Click "Grab your Salesforce Access Token" under "Salesforce Connection Settings".
A popup opens where you can log in to Salesforce. Log in with the separate user (recommended), or with your own user. After you log in, Salesforce will ask for permissions.
Click "Allow Access".
An empty page appears for "Remote Access Application Authorization."
Select the entire URL in the popup window and copy it.
Go back to BlueConic and paste the copied URL into the input field next to "Grab your Salesforce Access Token".
Save the connection in BlueConic.
Your connection should now show an instance URL, which means that BlueConic can now send messages to Salesforce. But to exchange profile data reliably, you need to set up remote access within Salesforce. This will allow you to exchange large amounts of data when you implement the connection between BlueConic and Salesforce.
Configure the Salesforce page layout
Technically you are done now;two-way communication between Salesforce and BlueConic is now possible.
However, with a little extra configuration you can give your Sales team advanced access to BlueConic information without having to synchronize all data to Salesforce.
The Live Profile Viewer is an optionalobject that you can add to a page layout. As the Salesforce page is being loaded, it will requestlive information from BlueConic and make it available for inspection.
In Salesforce, set up the Live Profile Viewer as follows:
In Salesforce, click"setup" in the top right.
In the left menu select Build > Customize>Leads>Page Layouts.
Click "Edit" for the layout to which you want to add the Live Profile Viewer.
From the "Fields" bar drag and drop the element "Section" to the "Lead Detail" block.
In the popup:
Enter aname for the section, for example "BlueConic Live Profile viewer".
Select 1-column Layout.
Press [OK].
In the layout bar, scroll the menu in the left down to select "Visualforce pages"
Drag the "LeadProfile" page to the newly created Section.
Save the layout.
Hover over the blue LeadProfile area of the BlueConic Live Profile, and click the wrench icon in the top right to modify its settings.
Save the layout.
Repeat this for all layouts and also for Contacts.
Using the connection
Now that you have a working connection between BlueConic and Salesforce, it is time to define exactlywhatwill be synchronized between the two. You can determine:
What data to collect from Salesforce
What data to deliver to Salesforce
When to create a new lead in Salesforce
How to match profiles inBlueConic toleads or contacts in Salesforce
What BlueConic information to show in the Salesforce page layout.
The following sections delve deeper into the options that are at your disposal for synchronizing BlueConic and Salesforce.
Collect settings
The collect settings allow you to determine which fields will be collected from Salesforce andhow they will be mapped to BlueConic profile properties. You can add variablesby clickingthe [Add Variable] button.
Collecting variables is optional; if you do not need anything from Salesforce in BlueConic profile properties it is okay to leave this section empty.
Each variable has the following options:
Salesforce Object Type(s)
Indicatewhetherthe field belongs to a Lead, aContact or both in Salesforce.
Salesforce Field Label
Enter the "Field Name" (in case of standard fields) or "API Name" (in case of custom fields) of the lead or contact in Salesforce. You can find these in Salesforce by clicking "Setup" and selecting "Build > Customize > Leads > Fields" or"Build > Customize > Contacts> Fields".
Profile Property
Select the BlueConic profile property into which the Salesforce value should be collectedby typing its name or by using advanced search to find it.
Merge Rule
The merge rule setting determineshowa value collected from Salesforce will be stored into the BlueConic property. These are the options:
Set: Copy the value from Salesforce exactly to the profile property, overwriting the previous value.
Set if empty: Copy the value from Salesforce exactly to the profile property but only if it is empty. If the profile property already has a value do nothing.
Add: Add the value from Salesforce to the list of values already in the profile property if it hasn't been added yet, omitting duplicates.
Sum: Numerically add the value from Salesforce to the value in the profile property. If the profile property was empty, it will be regarded as value 0. Only works for profile properties and values that contain integer numbers.
To duplicate a variable click the copy icon, or to delete a variable click the delete icon on the right hand side.
Deliver settings
Use the deliver settings to determine which BlueConic values will be deliveredto Salesforce and to which fields.You can add variablesby selecting the type "Profile Property", "Segments" (to deliver the list of segment names a profile is part of) or "Permission Level" (to deliver the permission level of aprofile) and clickingthe [Add Variable] button.
Warning
Make sure you always deliver allfields that are marked as "mandatory" in Salesforce! If you leave out mandatory fields, Salesforce will block the connection fromcreating any new leads as mandatory information is missing.
Deliveringvariables is optional; if you do not need anything from BlueConicin Salesforceit is okay to leave this section empty.
Each variable has the following options:
Variable
Select the BlueConic profile property whose value should be delivered toSalesforce by typing its name or by using advanced search to find it. If you added a variable of type "Segments" or "Permission Level" the variablehas already been preselected for you.
Salesforce Object Type(s)
Indicatewhetherthe field belongs to a Lead, aContact or both in Salesforce.
Salesforce Field Label
Enter the "Field Name" (in case of standard fields) or "API Name" (in case of custom fields) of the lead or contact in Salesforce. You can find these in Salesforce by clicking "Setup" and selecting "Build > Customize > Leads > Fields" or"Build > Customize > Contacts> Fields".
Merge Rule
The merge rule setting determineshowa value from theBlueConic profile propertywill be stored into the Salesforce field. These are the options:
Set: Copy the value from the profile propertyexactly to the field in Salesforce, overwriting the previous value. If the profile property contains a list of values and the Salesforce field is a text field all values will be concatenated into one string with a semicolon as separator (e.g. "value a; value b; value c").
Set if empty: Copy the value from the profile propertyexactly to the field in Salesforce butonly if it is empty. If the profile property already has a value do nothing.
Add: Add the value from the profile propertyto the list of values already in the field in Salesforceif it hasn't been added yet, omitting duplicates. The Salesforce field should be a Picklist (Multi-Select). Due to constraints in Salesforce there can only be a maximum of 100 value entries in the list and each value can only be 35 characters long.
Sum: Numerically add the value from Salesforce to the value in the profile property. If the profile property was empty, it will be regarded as value 0. Only works for profile properties that contain numbers.
To duplicate a variable click the copy icon, or to delete a variable click the delete icon on the right hand side.
Creation criteria
Under creation criteria you decidewhen it is okay forBlueConicto create a new lead object in Salesforce and deliver all deliverables subsequently.
Select all the profile properties that first will need to have a value in BlueConic before a new lead is created.
This section is optional; if you do not want BlueConic to create any new lead objects in Salesforce, do not select any profile properties.
Matchingcriteria
Under matching criteria you decide when a profile in BlueConic matches a lead or contact in Salesforce. Do this by adding variables that will match BlueConic profile properties to Salesforce fields.
Each variable has the following options:
Profile Property
Select the BlueConic profile property whose value should be matchedtoSalesforce by typing its name or by using advanced search to find it.
Salesforce Object Type(s)
Indicatewhetherthe field belongs to a Lead, aContact or both in Salesforce.
Salesforce Field Label
Enter the "Field Name" (in case of standard fields) or "API Name" (in case of custom fields) of the lead or contact in Salesforce. You can find these in Salesforce by clicking "Setup" and selecting "Build > Customize > Leads > Fields" or"Build > Customize > Contacts> Fields".
To duplicate a variable click the copy icon, or to delete a variable click the delete icon on the right hand side.
BlueConic data blocks
BlueConic dataenrich the lead or contact detail information in Salesforce by displaying live information from BlueConic. Upon opening the details page in Salesforce the VisualForce component that displays the blocks requests the most recentprofile information for this particularlead or contact from BlueConic and displays the information. The profile information will berefreshed whenever the page is reloaded.
Select the profile properties that you want to be displayed in Salesforce by searching for them.
The blocks can be reordered by clicking the left and right arrows in the blue bar.
In the Salesforce lead or contact details page you will see something like this:
The "Segments" and "Other Profile Properties" blocks are automatically added. The former displays a list of all segments a profile is a member of. With the latter you can search for profile properties and inspecttheir value.
Synchronization
As soon as you activate and save the Salesforce connection in BlueConic, scheduled runs will start to synchronize the two systems from time to time. Due to restrictions on the number of Salesforce API callssynchronization is not instant and data is pooled to make effective use of the connection.
Click the "Show History" link to see previous runs.
If there was aproblem during synchronization it will be mentioned under "Details".When you hover over a run a "Download log" icon will appear on the right. Click the icon to download the log for that particular run.
View ArticleThere are many different approaches to privacy compliance for GDPR and CCPA. The example in this guide shows how to use BlueConic for basic GDPR privacy compliance, by blocking the platform from creating profiles for visitors from the EU. You can follow these general steps for CCPA using the privacy management tools and choosing a different legislation zone.
Before you begin
Before using this Playbook, complete the following steps:
Define your marketing objectives -- these are the marketing goals that will require GDPR-protected customer data. You will be adding these objectives to BlueConic to inform the platform about what data to collect for whom. A marketing objective might be “Collect email for personalized email campaigns” or “Optimize web experience.”
Create the necessary Objectives in BlueConic.
Define your audience
When you create your first Objective, BlueConic creates a profile property called “GDPR Privacy Legislation.” BlueConic will then automatically populate profile values of “none” and “gdpr.” Visitors from a GDPR zone will have a value of “gdpr,” other visitors will have a value of “none.” You can use this profile property to build segments of your GDPR zone visitors to display consent dialogues to.
Collect data
For this use case, use the “European visitors: only profile after consent” listener. Once turned on, this listener will only create profiles for visitors from the EU after they have consented to one or more Objective. This listener has additional options that let you block profile creation for returning visitors who already had a profile before 25 May 2018, and to delete existing European profiles when they re-enter one of your channels. You can also specify a segment to be excluded from deletion.
Create a listener
Log in to BlueConic and do the following:
ChooseListeners in the BlueConic navigation bar.
Select the Add Listener button.
Using the search box provided, search for “European visitors.”
Select European visitors: only profile after consent listener.
Next, you will need to configure your listener, as shown below.
Overview of Objectives in BlueConic
Activate data
If you want to make it possible for EU visitors to have a profile after enabling this listener, you need to create a Dialogue in order to retrieve consent from visitors for at least one of your objectives.
To do this, complete the following steps:
ChooseDialogues in the BlueConic navigation bar.
Select the Add dialogue button.
Choose a dialogue type (for example, a lightbox or form). Open the Dialogue.
From the “Who” tab, set “Privacy legislation” to “gdpr” and expand the segment to target visitors who have not consented to Objectives you plan to ask for in the Dialogue.
Click Save.
Design the customer experience for managing consent
Next, you will need to design the experience by which the visitor grants access.
On the "What"tab,Editthe contents of the lightbox. Open theInsert objectmenu and choosePrivacy management components.
Note: If you do not see the Privacy management components option, contact your BlueConic CSM to install the appropriate plugin.
ChooseManage consentin the Privacy management popup window that appears.
In the Objectives tab of this overlay, select the Objectives you're asking customers to consent to.
In the Settings tab, you can apply custom styling, and provide text to interact with the visitor.
When done, close the overlay and click Save.
Note: Setting up privacy compliance in BlueConic for CCPA, the California Consumer Privacy Act, follows similar steps to setting up privacy compliance for GDPR.
Learn more
Privacy management with BlueConic
View ArticleThis article offers guidelines for importing and using customer order data in BlueConic.
Importing order data into BlueConic
Importing order data into BlueConic typically means storing data in profiles properties and creating events on the profile timeline.
Order data model
Best practices for profile properties that hold order data
There are no out-of-box order profile properties. The following list offers a best practice for loading order data into profile properties.
Name
ID
Type
Description
Orderdate/time (all)
orderDateTimeAll
Date time
All order dates
Orderdate/time (firstorder)
firstOrderDateTime
Date time
Date of the first order
Orderdate/time (most recent)
orderDateTime
Date time
Date of the last order
OrderID (most recent)
orderID
Text
For anonymous orders, the Order ID can be used as a unique identifier.
Ordered product categories (most recent order)
orderedProductCategories
Text
Product categories of the most recent order
Ordered product categories (all)
orderedProductCategoriesAll
Text
Product categories for all orders
Timeline
The order event type can be loaded into BlueConic using this URL: https://plugins.blueconic.net/eventtype_order/index.xml.
While the properties of the default type can not be changed, the default order event type can be extended. Please contact the Solutions team for assistance if this is needed.
Property
Type
Description
event_id
TEXT
Event ID generated by BlueConic or the connection
order_id
TEXT
Order ID
order_date
DATE
Date of the order
affiliation
TEXT
The store or affiliation where the transaction occurred
total_revenue
DECIMAL
Total revenue including shipping and tax, discounts, and promotions and coupons
quantity
NUMBER
Total number of products ordered
revenue
DECIMAL
Revenue excluding shipping and tax, including promotions and coupons
shipping
DECIMAL
Shipping cost in absolute currency
tax
DECIMAL
Tax in absolute currency
discount
DECIMAL
Discount in absolute currency
coupon
TEXT
Coupons used
promotion
TEXT
Promotions that are active for this order
currency
TEXT
Currency used for the transaction
tag
TEXT
Tags to be used for filtering and searching
product
ARRAY
All order lines in the order
product.id
TEXT
Internal product ID of product ordered
product.sku
TEXT
Product SKU
product.upc
TEXT
Product UPC
product.category
TEXT
Product Category
product.name
TEXT
Name of the product
product.variant
TEXT
Variant of the product (e.g. white, black, 32 GB, etc.)
product.brand
TEXT
Brand of the product
product.listprice
DECIMAL
List Price of order line (list price * number of items)
product.netprice
DECIMAL
Net price paid for this order line
product.quantity
NUMBER
Number of products ordered
product.coupon
TEXT
Coupon used for this order line
product.promotion
TEXT
Promotion used for this product (e.g. free shipping or 10\% percent off)
product.tag
TEXT
Product tags to be used for filtering and searching
product.shippingcost
DECIMAL
Shipping cost for the productin absolute currency
product.shippingdate
DATE
Expected date of shipment of this order line
product.deliverydate
DATE
Expected date of delivery of this order line
product.position
TEXT
Position of the product (for example which level in store, or place in search or page)
product.url
TEXT
Webpage that gives more information about the product
product.image_url
TEXT
URL that shows an image of the product
Guidelines for importing order data into BlueConic
File requirements
CSV
UTF-8 encoded
RFC 4180
If fields are not enclosed with double quotes, then double quotes may not appear inside the fields.
Each value that can contain a double quote, a delimited character, a carriage return/line feed, or a leading/trailing space has to be enclosed in double quotes.
If double-quotes are used to enclose fields, then a double-quote appearing inside a field must be escaped by preceding it with another double quote.
Order event uniqueness
To avoid creating duplicate order events when importing the same order feed multiple times, it is essential that each order event be assigned a unique identifier. Ideally, each order in the order feed holds a unique order identifier. You can then map that unique order identifier to the order event ID at the import connection. If that is not the case, and you need to for example combine data from multiple columns to create a unique id, a pre-processor plugin needs to be developed. Please contact the Solutions team if that is needed.
Separate order header and order details file
In the ideal situation, a separate order header and order details file are delivered. The order header file holds order details at an aggregate level (total quantity, total revenue, etc.) as well as the PII associated with the order (name, address, email address, customer ID, etc.). The order details file holds a line for each ordered product, including the retail price, paid price, quantity, shipping date, etc.
Example order header file
Order ID
Order Date
Total Revenue
Total Quantity
Email Address
Address
12345
11-04-2018 15:16:17
500.00
3
123 Boston Ave.
54321
11-06-2018 13:18:12
200.00
1
123 Hello World St.
Example order details file
Order ID
Revenue
Product Name
Product Category
Product Brand
12345
100.00
Product A
Tech
Brand A
12345
200.00
Product B
Fashion
Brand B
12345
200.00
Product C
Entertainment
Brand C
56432
600.00
Product D
Tech
Brand D
In the example above, products A, B, and C will be associated with the order header line for [email protected] because they have the Order ID 12345. This will create a single order event that contains all products that were a part of that order. Since product D has a different order ID, this will be associated with a different order that shares the same order ID value.
Single file
In cases where the order data is delivered in a single file, the following should be taken into account
For each ordered product, there has to be a separate line in the CSV file.
Order lines have to be grouped by order ID in the CSV file.
See the best practices for exchanging data with BlueConic via CSV files.
Example single order file
Order ID
Order Date
Revenue
Product Name
Product Category
Product Brand
Quantity
Email Address
Address
12345
11-04-2018 15:16:17
100.00
Product A
Tech
Brand A
1
123 Boston Ave.
12345
11-04-2018 15:16:17
200.00
Product B
Fashion
Brand B
1
123 Boston Ave.
12345
11-04-2018 15:16:17
200.00
Product C
Entertainment
Brand C
1
123 Boston Ave.
A custom pre-processor plugin needs to be created to roll up the order lines into an order. Please contact the Solutions team when this is needed.
Activating order data in BlueConic
Creating customer segments based on order data
Only the data that has been loaded into profile properties can be used for segmentation. Example segments that can be based off of this data (if using best practices profile properties described above) might include:
All profiles that have ordered in the last 6 months
All profiles that didn't order in the last 6 months but did order in the 6 months prior to that
All profiles that ordered products in product category X
Order events that are stored in the profile timeline cannot be used directly for segmentation. They can however be used to train AI Workbench models and to create derivative profile properties such as RFM and CLV values that then can be used for segmentation.
Using order data in AI Workbench
The following models are available out-of-box in the BlueConic AI Workbench, and will leverage order events stored on the profile's timeline.
Please note that for these models to work, the "order_id" and "revenue" properties need to be populated for each order event on the timeline
CLV
Customer lifetime modeling is a way to describe a customers' behavior using a customers order history. Based on the order history, you can extrapolate what you expect customers to spend on you for a given timeframe. This is done by first reviewing the same scores as RFM models do, and then training a model with the behavior that you specific customers exhibit.
You end up with a Customer Lifetime Value, which is "the value the customer is expected to add over the next period." You can set the period as you like, but a year is pretty common. Based on the data, you also get a probability score that the customer has not yet churned, and an expected number of purchases for a specific period. Learn more about the using the CLV notebook in AI Workbench.
RFM
RFM is a way to segment buyers into different groups. For each variable (Recency, Frequency, Monetary value) customers are dividedinto 3 to 5 groups (low frequency, mid frequency, high frequency for example). This results in 3x3x3 to 5x5x5 different variations in scores. The idea is that someone who scores 5,5,5 for R,F,M is your best customer, a 1,1,1 your worst. You can also recognizefrequent low value buyers (for example 5,5,1) or other groups. This is a common tool for retail marketers and gives them a recognizableway to do their segmentation.Learn more about using the RFM notebook in AI Workbench.
Order refunds
An order refund describes a cancellation or return flow.Order refunds have to be imported as separate timeline events in BlueConic.The order refund event type can be loaded into BlueConic using this URL: https://plugins.blueconic.net/eventtype_order_refund/index.xml
Order refund model
Property
Display Name
Type
Description
event_id
Event Identifier
TEXT
Event ID generated by BlueConic
source_order_id
Source Order
TEXT
Source Order ID from the original order
status
Refund Status
TEXT
One of 'order_refund_requested', 'order_returned', 'order_refunded'
refund_id
Refund Identifier
TEXT
Reference ID of a specific refund process
quantity
Quantity
NUMBER
Number of items refunded
total_value
Refund Value
DECIMAL
Total value of refunded order
currency
Currency
TEXT
Currency used for the refund
product
-
All products returned and refunded
product.id
Product ID
TEXT
Internal product ID of product ordered
product.sku
Product SKU
TEXT
Product SKU ( https://en.wikipedia.org/wiki/Stock_keeping_unit )
product.upc
Product UPC
TEXT
Product UPC ( https://en.wikipedia.org/wiki/Universal_Product_Code )
product.category
Product Category
TEXT
Product Category
product.name
Product Name
TEXT
Name of the product
product.variant
Product Variant
TEXT
Variant of the product (eg white, black, 32GB etc)
product.brand
Product Brand
TEXT
Brand of the product
product.netprice
Product Net Price
DECIMAL
Net price paid for this orderline
product.quantity
Product Quantity
NUMBER
Number of products ordered
product.url
Product URL
TEXT
Webpage that gives more information about the product
product.image_url
Product Image URL
TEXT
URL that shows an image of the product
Importing order refunds
A separateimport goal has to be set up to import the order refund events into BlueConic. There are two ways to set this up:
There is a separate order refund feed, preferably consisting of 2 files: a header and an item file. In case of a single file feed, a pre-processor is required to do the 'rollup'.Please contact the Solutions team for assistance if this is needed.
The refunds are part of the regular order feed. In this case a pre-processor plugin is required to separate the regular from the refund orders. This pre-processor is activated at both the regular and the refund import goal.Please contact the Solutions team for assistance if this is needed.
Regardless of the way the refunds are exposed, the feed has to adhere to the"Guidelines for importing order data into BlueConic", as described above.
Using refund order data in AI Workbench
Refund order data is automatically used in CLV and RFM calculations if the 'source_order_id' and 'total_revenue' are filled. The 'source_order_id' property needs to have the same values as the 'order_id' property of the regular order that was refunded.
View ArticleWith BlueConic, you can increase customer acquisition by reaching more of the right audience and converting them with the right message.
Increasing the number of leads a company has provides additional opportunities for sales and new customers, as well as driving prospects further down the sales funnel.
Before you begin
Before you follow the lead generation steps below, you'll need to understand:
Profile properties
Segments
Dialogues
Collect data
Identify the segment of customers you want to target for lead generation. Most likely, this segment includes profiles that are missing key information, such as email address, phone numbers, etc.
If the segment doesn't exist yet, you need to determine if you have enough data to create it.
If you need additional data to populate profiles in a segment, you may need to create a Listener or Connection in order to collect profile data for your segment.
Create the segment by choosing a profile property to form the basis for the segmentation. In this example, we are using email address:
Defining a conversion moment
We don’t need specific information, so we will just create a segment that will include anyone for whom the 'Email address' profile property is empty. This creates a segment for anyone whose profile does not yet contain an email address.
Activate data
Next, you need to target or activate the segment by using a Dialogue, which you can use to capture lead information.
When creating the dialogue, you must identify the “Who” -- which is the segment to deliver this to.
You should choose the segment you created above inStep 4.
Use the“Where” tab of your dialogue to determine where you want the dialogue to appear. Do you want this only on your homepage, on your subpages, or on a specific page? Once you have determined the placement, you can choose the channel and specify the appropriate URL. In BlueConic, a channel refers to a unique website, email interaction, or mobile app.
In the example shown here, we specify that the dialogue should appear only on “sportarticles” subpages.
The “What” tab is where you create the Dialogue itself. You can use the rich text editor, HTML, CSS, and JavaScript to create a multitude of dialogue experiences.
Click Load examples to see dialogue examples you can use to get started with personalization in BlueConic.
Once you have chosen the dialogue style, you can edit it to match your needs by editing the CSS or HTML.
By default, the example will set the value of the form to the profile property email address when the form is submitted. You can change this depending on the values you are retrieving from the form and where you want them stored within BlueConic.
Now you have a lead capture dialogue that will set the email address profile property with the value your customers submit in the form.
Measure your success
There are several ways to measure the success of your lead capture campaign. Use BlueConic dashboards and insights,for example the Dialogues Table insight, to see results:
Increase in leads (for example, the number of leads per month, month, quarter, year)
Increase in lead capture conversion rate
Increase or improvement in segmentation by lead type
Lowered CPA for defined target audiences
Learn more
Segments
Dialogues
Insights and Listeners
View ArticleOne of the most exciting aspects of BlueConic is the built-in capability to deploy personalized content and relevant interactions based on user data and segmentation.
This hands-on (recommended!) training session will take your team through the steps to build and deploy a BlueConic dialogue. Dialogues come in a variety of flavors, from in-line editing to lightboxes, toasters, and slide out interactions to name a few.
We'll focus on the tab-based configuration of Who, Where, When, What, and Why tabs along with the Optimization tab.
Who:In this tab, you'll select the segment(s) you want to target, or configure a new set of filters on the fly. As an option, you may also target all visitors.
A/B testing mode
Where:Define exactly which pages your interaction should be or should not be deployed on.
When:A variety of options will allow you to specify when the interaction should be triggered. Start and end date/times keep users from needing to log in to turn interactions on or off. A frequency cap will ensure the interaction isn't overused. Date- and time-based settings let you adda contextual touch to messages.
What:This is where you create the interaction itself. There is both an HTML editor and a visual editor. Insert images, forms, and data points directly from user profiles.
Why:All dialogues can have success criteria defined, to round out measurement which includes views, clicks, and conversions. Online behaviors or offline behaviors can be used to trigger conversions in this area.
Optimization:At the right side of the dialogue tabs is the optimization tab. It is here that you can set up multiple variants for any dialogue, and configure the variants in, rotation, or automatic optimization. In automatic optimization mode, BlueConic will use a multi-arm bandit algorithm to lean hardesttoward the winning variants -- and lean harder depending on how much the variant is winning by.
View ArticleAbout BlueConic: BlueConic is a Customer Data Platform that harnesses the data required to power the recognition of an individual at each interaction, and then synchronizes their intent across the marketing ecosystem. Learn more about the BlueConic platform.
What:The GoogleAnalytics Connection allows you to enrich the information in an existing GoogleAnalytics implementation. The connection can feedsegment or profile information from BlueConic to GoogleAnalytics using the technique of Custom Link Tracking.
Before you can use the Google Analytics connection, you must create a Google Analytics account and link it to BlueConic. Follow the steps in this section to prepare Google Analytics to work with BlueConic.
Note that there are many ways to display BlueConic data in Google Analytics, including Data Studio. The steps below describe how to use Google custom reports to view BlueConic data.
Prerequisites
A Google Analytics account
Script provided by Google Analytics added to your website with the correct account number
Google Analytics interaction type installed in BlueConic. The Google Analytics interaction type is available at http://plugins.blueconic.net/gainteractiontype/index.xml
A BlueConic dialogue
Configuration steps
Follow the steps below in the order given to prepare your BlueConic website to integrate with Google Analytics.
Create a Google Analytics account.
Click "Custom Reporting" in the toolbar:
Click "New Category":
Create a new category ("BlueConic" for example).
Click "New Custom Report" to create a custom report.
Select "Flat Table" for the type.
Add the dimension "Custom Variable (Key 1)".
Add the metric "Unique Visitors".
Click "Save":
Visit the page(s) on your website on which the Google Analytics interaction is active and performing the action(s) necessary to trigger the interaction.
In Google Analytics, navigate to custom reporting and select the report you created in the steps above.
Click the button next to the date range and select "Today" from the drop-down box:
Google Analytics can take up to a day to post website statistics in your reports. Using your browser's Developer Tools, you can see immediately requests sent by BlueConic to Google Analytics in order to confirm that you have successfully configured the BlueConic Google Analytics integration.
View Article
Working at BlueConic
BlueConic's Competitors
Recently Asked Questions
Recent BlueConic Employee Reviews
- I am OBSESSED with working at BlueConic. The work is exciting and engaging and, more importantly, the people are simply outstanding. They are smart, friendly and bring their best selves to work each day. There is not a day that passes that I don't thank my lucky stars that I found my way here.
- very good! Easy to find other workers who have the same interests as you. Everyone is always willing to help.
- How well they listen to the rest of their teams
- 1-Salary/hourly rate. 2- Flexible hours 3-Paid pension 4-Paid holiday, vacation and sick days
- Pay is fair, days off are generous, benefits are on par with what I would expect with many options.