Each CoolaData tracker automatically enriches the events that you send by adding more properties (these are also called common properties).

CoolaData supports various web and mobile platforms. Here’s a table that lists the common properties that are automatically enriched by CoolaData’s trackers into each event.

In the table below, a + sign in the tracker column indicates that this property is automatically enriched by that tracker.

Property Description JS iOS Android AS Unity
app_id The app ID/bundle ID in the Play/Apple Stores. For example, com.mycompany.myapp. + +
app_version The version of the app. For example, 2.3.1. + +
browser_name The name of the user’s browser. For example, Chrome or Safari. + + +
browser_version The version of the user’s browser. For example, 10 or 11. + + +
carrier The wireless carrier of the device owner. For example, Orange or Vodafone. + +
connectivity_state The connectivity state of the device. For example, Mobile, WiFi or Offline. + + +
customer_user_id The user ID of the hosting app. This is the cookie. See CoolaData User IDs for more information. + + + + +
device_brand The market brand of the device. For example, iPhone 4 or Samsung Galaxy S III. + + + + +
device_manufacturer The device manufacturer. For example, Samsung or Apple. + + +
device_model The device model name. For example, iPad 4 or GT‑I9300. + + + + +
device_name The user-defined name of the device. Note – On Android, this property is not supported and always contains the string “”. +
device_os The operating system of the device. For example, Android or iOS. + + + + +
device_os_version The operating system version of the device. For example, 4.1. + + + + +
device_screen_size The width and the height of the device screen. For example, 300×400. + + + +
device_type The type of device. For example, Desktop, Mobile or Tablet. + + + +
device_unique_ identifier A unique device identifier.

In iOS, returns UIDevice identifierForVendor.

In Android, returns the device IMEI.

+
event_time_ts The timestamp of the event represented in the UTC time standard.

This is the timestamp when the event was sent by your app using the CoolaData tracker. This timestamp is determined by the timeclock of the device that sent the event.

According to how CoolaData has configured your system, instead of the timestamp of the device that sent the event, CoolaData can automatically assign the timestamp of the CoolaData server to the event.

To activate this feature, contact your CoolaData success representative.

+ + + + +
install_referrer The Install Referrer is used to track the installation source of the app. PLEASE DESCRIBE. ASK EFI GGG

Someone will get back to me he sent an email

+
ip_city The city of the event sender, extracted from the IP. + + +
ip_country The country of the event sender, extracted from the IP. + + +
ip_latitude The latitude location of the event sender, extracted from the IP. + + +
ip_longitude The longitude location of the event sender, extracted from the IP. + + +
ip_region The region of the event sender, extracted from the IP. + + +
location_altitude The altitude, which is available only if the user permitted access to the location, and altitude information is supported by the device. +
location_latitude The latitude location, which is only available if the user has permitted location access. +
location_longitude The longitude location, which is only available if the user has permitted location access. +
referring_domain The domain from which a user came to visit your page. +
referring_url The URL from which a user came to visit your page. +
session_duration The duration of the session, in milliseconds. Based on a CoolaData session. The customer’s session ID is not relevant. + + + + +
session_id A unique ID assigned to a specific user for the duration of that user’s visit, which is also known as a session. See CoolaData Session for more information. + + + + +
session_screen_scale The current screen resolution, in this format: {SCREEN_WIDTH, SCREEN_HEIGHT}. +
time_in_app The time, in seconds, from the CoolaData tracker initialization (usually from application load time, if the CoolaData tracker is initialized when the application loads). +
timezone_offset The device time zone offset from UTC time, in hours. For example, -2.5. + + +
tracker_type CoolaData tracker type. For example, JavaScript, Android or iOS and so on. + + + +
tracker_version CoolaData tracker version. For example, 2.1.0. + + + +
traffic_source A combination of the page URL and the page referrer. Used to infer from where the traffic originated before coming to the website. +
user_id CoolaData internal user ID. Always use this property when applicable.

See CoolaData User IDs for more information.

+ + + +
user_local_time The user local time calculated based on the UTC time + the time zone offset. + + +
utm_campaign Campaign Name taken from the URL – Use utm_campaign for keyword analysis in order to identify a specific product promotion or strategic campaign. For example, spring_sale.

https://www.upwork.com/ppc/landing/utm_campaign=spring_sale

+ +
utm_content Campaign Content taken from the URL – Used for A/B testing and content of targeted ads in order to differentiate between ads and/or links that point to the same URL. For example, logolink or textlink.

https://www.upwork.com/ppc/landing/utm_content=logolink

+ +
utm_medium Campaign Medium taken from the URL – Used to identify a medium, such as email or cost-per-click. For example, capacity. https://www.upwork.com/ppc/landing/utm_content=capacity + +
utm_source Campaign Source taken from the URL – Used to identify a search engine, newsletter name or other source. For example, Google.

https://www.upwork.com/ppc/landing/utm_source=Google

+ +
utm_term Campaign Term taken from the URL – Used for a paid search to specify the keywords for this ad. For example, running + shoes failed to appear. + +
Print Friendly