Compass initializes Contact profiles records at the moment they are collected from the guest WiFi and the other touchpoints, and later it continuously updates the profiles with dynamically computed behavioral metrics.
To get the most out of Cloud4Wi, when using an external system to act on the data (CRM, marketing automation, etc..) you should make sure to synch all the relevant contact profile fields.
In case you need to initialize these fields in your external system (e.g. a CRM), you can find below the list of available attributes.
Note: the name of the fields does not reflect the actual field name in Cloud4Wi API or webhooks; you can define your naming convention and then map the fields during the integration.
| Name | Type | Description and notes |
| c4wContacid | varchar | c4w contact identified |
| title | varchar | |
| firstName | varchar | as filled in forms |
| lastName | varchar | as filled in forms |
| gender | varchar | male, female, other |
| birthDate | date | 07-23-1982 (mm-dd-yyyy) |
| age | number (int) | 36 |
| country | varchar | as filled in forms |
| zipCode | varchar | as filled in forms |
| created | date | 2021-07-01T15:09:43Z (UTC) |
| modified | date | 2021-07-01T15:09:43Z (UTC) |
| varchar | ||
| emailVerified | boolean | true, false |
| phone | varchar | E.g. +14156233285 |
| phoneVerified | boolean | true, false |
| signupMethod | varchar | Eg. passthrough, Facebook |
| externalIdentityId | varchar | (ex. Facebook user id) |
| username | varchar | wifi account username |
| locked | boolean | true, false | WiFi service enabled or disabled |
| locationCid | varchar | id of signup location |
| system | varchar | Source signup, e.g. "splashportal" |
| locationName | varchar | name of signup location |
| personalId | varchar | as filled in forms |
| lastLogin | date | E.g. 2021-07-01T17:09:47.000Z (in UTC) |
| logins | number | number of WiFi logins |
If you have custom fields, they will available for export and API integration using the name given during the setup of the field in the dashboard.
Behavioral metrics
Contacts who provided the proper consent for profiling, also have the following attributes (behavioral metrics). More info and description of the metrics can be found in this article.
The following attributes can be retrieved via APIs using the following endpoints:
- /v2/customers/organizations/{cid}
- /v2/customers/{cid}
| Attribute | API name |
Type | Description and notes |
| Avg. Monthly Visits | frequencyMonthlyVisit | number (float) | E.g 1.86 |
| Favorite Location | compassTopLocation | varchar | id of the most visited location |
| Visits to Favorite Location | compassTopLocationCount | number (int) | total visits to the most visited location |
| Frequency Buckets | topFrequencyBuckets | varchar | Daily, Weekly, Bi-weekly, Monthly, Seasonal, Yearly, Occasional |
| Last Visit Location | lastVisitVenue | varchar | id of the last visited location |
| Favorite Day of week | prefVisitWDay | number (int) | 1 to 7 (1=mon to 7=sun) |
| Last Visit Date | lastVisitDateUtc | date | date of the last visit (UTC) |
| Last Visit Date | lastVisitDateBusiness | date | date of the last visit (local time zone) |
| Avg. Visit Duration | avgVisitLength | number (float) | E.g 106.7 - aver visit duration in minutes |
| Total Visited Locations | countVisitedLocations | number (int) | total locations visited |
| Favorite Time of day | prefVisitTimebucket | varchar | morning, afternoon, evening, night |
| Favorite Hour of day | prefVisitTimeHour | number (int) | favorite hour if visit (0 - 24) |
| Total Visits | countTotalVisits | number (int) | count of total visits |
| Attraction Rate | conversionRate | number (float) | 0-1 ratio between seen/visits |
| Avg. Days Between Visits | avgDaysBetweenVisits | number (float) | Eg. 1.7 - average number of days between visits |