Fanplayr 360 Generated Attributes

When Events are consumed by Fanplayr 360 the system will attempt to automatically generate some attributes. Example are from $countryCode from an IP address or $browser from a UserAgent.

If you provide these attributes in your event they will override these generated attributes. In general you should stay away from adding these to your tracking calls.

These attributes will be pre-populated in the Data Dictionary.

Generated Attributes

From IP address

These attributes are generated from IP address that is either automatically tracked by the JavaScript API, or supplied by the context for Custom API.

• $device.city - The city of the event source determined its IP address.

• $device.continent - The continent of the event source determined its IP address.

• $device.country - The country of the event source determined its IP address.

• $device.countryCode - The two-letter country code (ISO 3166-1) of the event source determined its IP address.

• $device.longitude - Longitude coordinate of the event source determined by its IP address.

• $device.latitude - Latitude coordinate of the event source determined by its IP address.

• $device.ipAddress - The IP address the event was generated from.

• $device.postalCode - The postal code of the event source determined its IP address.

• $device.region - The region or state of the event source determined its IP address.

• $device.regionCode - The region or state code of the event source determined its IP address. For example "CA" for California.

From User Agent

These attributes are generated from the User Agent string which is automatically tracked in the JavaScript API, or manually supplied in the context for Custom API.

The User-Agent header may also be manually supplied in mobile app integrations.

• $device.userAgent - Browser user agent string.

• $device.browser - Browser name that generated the event.

• $device.browserMajorVersion - Browser major version number.

• $device.browserMinorVersion - Browser minor version number.

• $device.os - Operating system name.

• $device.osMajorVersion - Operating system major version number.

• $device.osMinorVersion - Operating system minor version number.

• $device.type - The type of device ie "Laptop", "Desktop" and "Phone".

• $device.family - The model of device ie "iPhone", "Mac", "iPad", "Other".

From the URL

These attributes come from the context.page.url property sent through with events. The JavaScript API will do it automatically, but it must be provided for the Custom API.

• $session.domain - The domain name the event was tracked from.

• $utm.term - The ad terms associated with the UTM campaign.

• $utm.source - UTM campaign traffic source.

• $utm.medium - UTM campaign traffic medium.

• $utm.id - Unique UTM campaign identifier.

• $utm.content - Identifies the call-to-action that bought in traffic for the UTM campaign.

• $utm.campaign - UTM campaign name.

Other

These comes from multiple sources.

• $eventName - Name of the event.

• $eventTime - The date and time the event occurred.

• $timezone - The timezone of the event.

• $session.id - Unique identifier to differentiate browsing sessions.

• $userId - The primary unique identifier associated with the user.

• $source - The source of the event. This is generated from the key you provide, which you can get in your integration.