Docs
Go to Conductrics.com →
  1. Agent Concepts

Targeting with Conductrics

Using built-in and custom visitor data for targeting, filtering, reporting, and predictions.

Conductrics provides a rich set of targeting values, which you can combine with your own "first party" data for targeting purposes.

What are Targeting Values used for?

You can use targeting values for:

  • Include/Exclude Conditions, such as only allowing certain visitors to "enter" a test.

  • Explicit Targeting Rules, such as always showing a "B" variation to certain visitors, etc.

  • Predictive Targeting, where Conductrics automatically matches visitors to variations based on trends from prior visitors.

  • Reporting, if you just want to be able to view/split/compare conversion rates, etc., for different types of visitors.

Custom, Computed, and Built-In Targeting

With Conductrics, you can use/enable any of the following for targeting rules or automatic targeting, or just for reporting purposes:

  • Built-In Targeting as detailed below, including:

    • Date / Time, such as weekend/weekday, day/night, timezone, etc.

    • Geo, such as country, continent, etc.

    • Device / Browser / User Agent, such as mobile device type, operating system, etc.

    • Random Groupings, for random allocations into various groups

    • Visit Related, such as whether this is a first visit, time since last visit, etc.

    • Agent Related, such as whether the visitor was assigned to a particular variation in the past, etc.

  • Custom Visitor Traits, passed via our APIs or "Preboot"

  • Custom Inputs, passed via our APIs or "Preboot"

  • Values from Client-Side Cookies

  • Values from your Data Layer

  • Values from your Google Cloud-Hosted Data

  • Values "looked up" via a URL/hook that you provide (Conductrics will set this up for you).

  • Values looked up via Demandbase (contact Conductrics for other similar integrations).

📘

Supported on Client and Server

With the exception of the Data Layer integration, all forms of targeting data (summarized above) are available in the same manner whether using Conductrics on the client or server.

Computed Visitor Traits
You can also create "computed" visitor traits, created in our admin based on the other values listed in this doc. This is analogous to creating a "segment" in other systems. Set up computed visitor traits in the Conductrics admin, under Settings > Visitor Data.

Some examples of such computed visitor traits that you could create:

  1. Number of times visitor has watched a video;

  2. Visitors who have visited the "Providers" section of your site or app, and who have visited more than twice in the past 30 days;

  3. "Bins" of past purchases, such as "less than $50", "$50 - $200", "more than $200", and so on.

  4. Registered users who prefer Sports and who visit often.

And so on. In nearly all cases you can freely intermix your first-party data, the Conductrics built-in visitor data, and any additional data that's available from third parties.

🚧

About Personally Identifiable Information (PII)

Conductrics is not meant as a datastore for personally identifiable information. Please do not provide PII to Conductrics. Exceptions can be made if you are hosting Conductrics on-premise. Please contact Conductrics with any questions.

Built-In Targeting

DATE / TIME

  • Current Date/Time

  • Weekday / Weekend

  • Day Part (morrning, afternoon, evening, night)

  • Day of Week

  • Hour of Day

  • Timezone (as number of hours offset from UTC)

GEO

  • Continent

  • Country

  • Domestic vs International (based on list of "home countries" specified in Conductrics admin)

  • Region/State

  • City Name

RANDOM GROUPING

  • Random 1-100 - Can use this to include/exclude (allow 10% of visitors into an optimization, etc), or to build "segments" used internally to "claim" certain visitors by different departments (Team A gets to test on this 20%, Team B on second 20%, etc).

DEVICE / BROWSER / USER AGENT

  • Is/Not Mobile

  • Browser Name (Safari vs Firefox vs Chrome, etc)

  • Device Type (Tablet vs Desktop, etc)

  • Operating System (Mac vs Windows, etc)

  • Modern or Old (whether supports modern HTML5 features)

Note: The above Browser/User Agent related items are provided on the client-side implicitly, and are also supported on the server side if you supply theua parameter to the REST API (or Node.js) - see the Runtime API Reference.

URL and URL PARAMETERS

  • Current URL (full) - The complete URL of the current page, including query parameters, etc. Corresponds to document.location.href in client-side script.

  • Current URL's Path - The path portion of the current page URL, such as /shop or /news/world, etc. Corresponds to document.location.pathname in client-side script.

  • Current URL's Hostname - The hostname portion of the current page URL, such as www.example.com. Corresponds to document.location.hostname in client-side script.

  • Current URL's Port - The port portion of the current page URL, typically 443 or 80. Corresponds to document.location.port in client-side script.

  • Current URL's Hash - The hash portion of the current page URL, if present, such as #description. Corresponds to document.location.hash in client-side script.

  • Current URL's Protocol - The protocol portion of the current page URL, such as http: or https:. Corresponds to document.location.protocol in client-side script.

  • query string parameters - Any "custom" query string parameters can be accessed for use in conditions, or "passed through" as visitor traits.

  • utm_campaign, utm_source, utm_medium, utm_term, utm_content - These conventional query-string parameters are predefined in dropdowns as a convenience.

  • Referring URL - Use to base conditions on the URL prior to the current one (if available). Corresponds to document.referrer in client-side script.

Note: The above URL-related items are provided on the client-side implicitly, and are also supported on the server side if you supply theurl parameter to the REST API (or Node.js) - see the Runtime API Reference.

VISIT RELATED

  • First Visit - Whether this is the first "visit" for a given visitor. Synonymous with a "visit count" of zero.

  • Visit Count - The number of "visits" for the current visitor. Incremented each time the visitor is encountered after a period of inactivity (1 hour by default; adjustable).

  • Hours Since Prior Visit

  • Days Since Prior Visit

  • Section-Specific Visit Count

  • Views in Current Visit

  • Views Total

  • Section-Specific Hours Since Prior Visit

AGENT RELATED

The following can also be used to build various "advanced" conditions around potentially "conflicting" optimizations or tests.

  • Whether the visitor has been "assigned" to a specific agent

  • Which variation was selected for a specific agent

  • Whether this is the first "view" for a specific agent

  • Whether the visitor has reached a particular "goal" (conversion) for a specific agent

Updated about 1 year ago