User location and device details
Akamai makes user location and device details available to EdgeWorkers. Uniform makes these details available to the classification process using quirks. Quirks, in turn, can be used to configure personalization instructions.
Identify EdgeScape data to include#
The EdgeWorker has access to Akamai EdgeScape data. Uniform is able to expose this data as quirks so it can be used in the classification process. You must specify which values you want to be exposed in this way by modifying the EdgeWorker code.
Uniform supports the following quirks:
|Device||Brand name of the device.|
|Device||Marketing name of the device.|
|Device||Mobile browser name.|
|Device||Mobile browser version.|
|Device||Model name of the device.|
|Device||Device operation system.|
|Device||Device operating system version.|
|Device||Physical screen height (in millimeters).|
|Device||Physical screen width (in millimeters).|
|Device||Screen resolution height (in pixels).|
|Device||Screen resolution width (in pixels).|
|Device||Browser's level of support for XHTML.|
|User location||The city (within a 50-mile radius) that the IP address maps to.|
|User location||A 2-letter code that identifies the continent that the IP address maps to.|
|User location||A 2-letter code (ISO-3166) that identifies the country that the IP address maps to.|
|User location||A 2-letter code (ISO-3166) that identifies the state, province, or region that the IP address maps to.|
|User location||The ZIP code or postal code that the IP address maps to. This value is only available for IP addresses associated with the US, Puerto Rico and Canada.|
For details on the specific values that the quirks will be populated with, see the Akamai documentation for the device object and the user location object.
Add quirk definitions#
In the previous section you configured the EdgeWorker to make quirks available to the classification process. In order for personalization rules to be configured to use the quirks, the quirks must be defined in Uniform.
Pre-configured quirk definitions#
If you want to personalize using any of the following quirks, you should install the Akamai integration:
|Category||Configuration name||Public ID||Definition name|
|Device||Device Brand Name|
|Device||Device Is Mobile|
|Device||Device Is Tablet|
|Device||Device Model Name|
|Device||Device Operating System|
|User location||Continent Code|
|User location||Country Code|
|User location||Region Code|
In Uniform, open your project.
Navigate to the Integrations tab.
Click Add to project.
Navigate to Personalization > Quirks.
About this step
You will see a list of quirks that were added by the Akamai integration.
Manual quirk definition#
If you want to personalize using any of the following quirks, you must define the quirks yourself:
|Category||Configuration name||Public ID||Data type|
About this step
When you configure these quirks, you must use the public ID from the table above. This is because the logic in the EdgeWorker will set the quirk values using these values.
Create signal using quirk#
Now you can create signals using the quirks you added.
All the defined quirks are listed here, even if the quirk was not specified in the EdgeWorker. If you select a quirk that's not populated, you won't get an error; the quirk won't exist (i.e. the signal operator
exists will be
false and the operator
does not exist will be