蜜豆视频

Profile attributes

Profile attributes in 蜜豆视频 Target are parameters that are specific to a visitor. These attributes are stored in the visitor鈥檚 profile to provide information about the visitor that can be used in your activities.

A user profile contains demographic and behavioral information of a web page visitor. This information can include age, gender, products purchased, last time of visit, and so on. Target uses this this information to personalize the content it serves to that visitor.

As a visitor browses your website, or when the visitor returns for another session, the saved profile attributes in the profile can be used to target content or log information for segment filtering.

To set up profile attributes:

Profile script attributes concept_8C07AEAB0A144FECA8B4FEB091AED4D2

Define a profile script attribute with its associated JavaScript code snippet.

You can use profile scripts to capture visitor attributes across multiple visits. Profile scripts are code snippets defined within Target using a form of server-side JavaScript. For example, you might use a profile script to capture how frequently a visitor visits your site, and when that visitor last visited.

Profile scripts are not the same as profile parameters. Profile parameters capture information about visitors using the mbox code implementation of Target.

Create profile scripts section_CB02F8B97CAF407DA84F7591A7504810

Profile scripts are available under the Audiences tab in the Target interface.

To add a profile script, click the Profile Scripts tab, Create Script, then write your script.

Or

To copy an existing profile script, from the Profile Scripts list, click the ellipsis icon for the desired script, then click Duplicate.

You can then edit the audience to create a similar audience.

Profile scripts run profile attribute 鈥渃atchers鈥� on each location request. When a location request is received, Target determines which activity should run and displays content that is appropriate to that activity and that experience. Target also tracks the success of the activity and runs any relevant profile scripts. This process lets you track information about the visit, such as the visitor鈥檚 location, time of day, number of times that visitor has been to the site, if they鈥檝e purchased before, and so on. This information is then added to the visitor鈥檚 profile so you can better track that visitor鈥檚 activity on your site.

Profile script attributes have the user. tag inserted before the attribute name. For example:

if (mbox.name == 'Track_Interest') {
    if (profile.get('model') == "A5" &&; profile.get('subcat') == "KS6") {
        return (user.get('A5KS6') || 0) + 1;
    }
}

Keep the following information in mind:

Viewing profile script information cards section_18EA3B919A8E49BBB09AA9215E1E3F17

You can view profile script information pop-up cards similar to offer information cards. These profile script information cards let you view the list of activities that reference the selected profile script, along with other useful metadata.

For example, the following profile script information card is accessed by clicking the Info icon for the desired profile script from the list (Audiences > Profile Scripts).

The Script Info tab contains the following information: Name, Description, and script code.

Click View full details to see the audiences and activities that reference the selected profile script.

Target disables profile scripts in certain situations section_C0FCB702E60D4576AD1174D39FBBE1A7

Target automatically disables profile scripts in certain situations, such as if they take too long to execute or have too many instructions.

When a profile script is disabled, a yellow alert icon displays next to the profile script in the Target UI, as illustrated below:

On hover, details on the error display, as illustrated below:

Typical reasons for the system to disable profile scripts include the following:

Best practices best

The following guidelines are meant to help write simplified profile scripts that are as error-failing-free as possible by writing code that fails gracefully so the scripts are processed without forcing a system-script-halt. These guidelines are a result of best practices that have been proven to run efficiently. These guidelines are to be applied alongside principles and recommendations drawn by the Rhino development community.

Debug profile scripts section_E9F933DE47EC4B4E9AF2463B181CE2DA

The following methods can be used to debug profile scripts:

Profile script FAQ section_1389497BB6D84FC38958AE43AAA6E712

Is it possible to use profile scripts to capture information from a page that resides in a data layer?

Profile scripts are unable to read the page directly because they are executed server side. The data must be passed in through an mbox request or through other methods of getting data into Target. After the data is in Target, profile scripts can read the data as an mbox parameter or profile parameter.

JavaScript reference for script profile parameters

Simple Javascript knowledge is required to effectively use script profile
parameters. This section serves as a quick reference to make you productive with this functionality in just a few minutes.

Script Profile Parameters are found under the mboxes/profiles tab. You can write Javascript programs that return any Javascript type (string, integer, array, and so forth).

Script profile parameter examples examples

Name: user.recency

var dayInMillis = 3600 * 24 * 1000;
if (mbox.name == 'orderThankyouPage') {
    user.setLocal('lastPurchaseTime', new Date().getTime());
}
var lastPurchaseTime = user.getLocal('lastPurchaseTime');
if (lastPurchaseTime) {
    return ((new Date()).getTime() - lastPurchaseTime) / dayInMillis;
}

Creates a variable for day as measured in milliseconds. If the mbox name is orderThankyouPage, set a local (invisible) user profile attribute named lastPurchaseTime to show the value of the current date and time. The value of last purchase time is read, and if defined, Target returns the time that has passed since the last purchase time, divided by the number of milliseconds in a day (which results in the number of days since the last purchase).

Name: user.frequency

var frequency = user.get('frequency') || 0;
if (mbox.name == 'orderThankyouPage') {
    return frequency + 1;
}

Creates a variable called frequency, initializing it to either the previous value or 0, if there was no previous value. If the mbox name is orderThankyouPage, the incremented value is returned.

Name: user.monetaryValue

var monetaryValue = user.get('monetaryValue') || 0;
if (mbox.name == 'orderThankyouPage') {
    return monetaryValue + parseInt(mbox.param('orderTotal'));
}

Creates a variable called monetaryValue, looking up the current value for a given visitor (or set to 0 if there was no previous value). If the mbox name is orderThankyouPage, new monetary value is returned by adding the previous one and the value of the orderTotal parameter passed to the mbox.

Name: adobeQA

if (page.param("adobeQA"))
     return page.param("adobeQA");
else if (page.param("adobeqa"))
     return page.param("adobeqa");
else if (mbox.param("adobeQA"))
     return mbox.param("adobeQA");

Creates a variable called adobeQA to track a user for Activity QA.

Objects and methods objects

The following objects and methods can be referenced by script profile parameters:

Common operators

All standard JavaScript operators are present and usable. JavaScript operators can be used on strings and numbers (and other data types). A quick briefing:

Training video: Profile Scripts

This video includes information about using and creating profile scripts.