Profile and variable glossary
This page lists profiles, variables, and parameters that are useful in profile scripts.
Built-In Profiles section_2B694370003C4F8E8E29E0B2F6E52045
user.activeCampaigns
user.header
profiles are built-in from mbox request header dataYou can get this in several ways, for example whatismyip.com. The IP address is not the NAT address (internal address), starting with 10., 192.168., or 172.
Note: user.header(‘x-cluster-client-ip’) has been deprecated.
user.setLocal
.Visitor device is a tablet.
NOTE: This profile replaces the deprecated legacy Browser is iPad audience category. See Browser for more information.
Visitor device is a mobile phone.
NOTE: This profile replaces the deprecated legacy Browser is iPhone audience category. See Browser for more information.
profile.parameter
or user.parameter
.URL Variables section_8F25958273164EBAA6DC659302993FD3
landing
referrer
page
landing.url
referrer.url
page.url
landing.domain
referrer.domain
page.domain
landing.protocol
referrer.protocol
page.protocol
landing.param
referrer.param
page.param
landing.query
referrer.query
page.query
Geo and Mobile Carrier Profiles section_08441DA42E7346918FBB345818854997
profile.geolocation.country
profile.geolocation.state
profile.geolocation.city
profile.geolocation.zip
profile.geolocation.dma
profile.geolocation.domainName
profile.geolocation.ispName
profile.geolocation.connectionSpeed
profile.geolocation.mobileCarrier
profile.geolocation.latitude
profile.geolocation.longitude
Mbox Variables section_C42F0D33BD8044BE812FA0B7905CC0ED
mbox.name
Parameters automatically passed with every request:
- mbox.param(‘browserHeight’)
- mbox.param(‘browserTimeOffset’)
- mbox.param(‘browserWidth’)
- mbox.param(‘colorDepth’)
- mbox.param(‘mboxXDomain’)
- mbox.param(‘mboxTime’)
- mbox.param(‘screenHeight’)
- mbox.param(‘screenWidth’)
Parameters passed with order mboxes:
- mbox.param(‘orderId’)
- mbox.param(‘orderTotal’)
- mbox.param(‘productPurchasedId’)
Note: Using mboxOverride parameters should be used only while testing the activity and not in production. The use of any mboxOverride parameters can cause reporting discrepancies when using Analytics for Target (A4T). You should use Activity QA mode while testing to ensure that your activity works as expected before pushing the activity into your live environment.
Customer Attributes section_62B4821EB6564FF4A14159A837AD4EDB
Customer attributes can be referenced in profile scripts, formatted as crs.get('<Datasource Name>.<Attribute name>')
.
These attributes are also available as tokens in profile scripts and directly in offers without first requiring a profile script. The token should be in the form: ${crs.datasourceName.attributeName}
. Note that spaces in the datasourceName
should be stripped from any API call.