Category filter
Configuration profile to disable personalised advertising on Mac
Apple uses contextual information to serve ads that may be more relevant to the user on their devices. If an organization doesn’t want its device contextual data being shared with Apple, they can disable the Personalised Ads setting on their Macs. A custom configuration profile can be used to disable the Personalised Ads on Macs remotely. This help document provides a step-by-step guide for IT admins on how to deploy a custom configuration profile to disable the personalised advertising on Macs with the help of Hexnode’s Deploy Custom Configuration feature.
The sample configuration profile provided below is created using various profile creator applications.
- This configuration profile can be used on devices running macOS 10.14 and above.
- Personalised Ads are not available in versions earlier than macOS 10.14, and if we apply the configuration profile to these devices, no changes occur.
Disable personalised advertising on Mac
Use the following configuration profile to disable Personalised Ads setting on Macs.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 |
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>PayloadContent</key> <array> <dict> <key>PayloadDisplayName</key> <string>Disable Personalised Ads</string> <key>PayloadIdentifier</key> <string>com.apple.AdLib.1351BBA0-6092-4125-B930-6AC1C8BCB081</string> <key>PayloadType</key> <string>com.apple.AdLib</string> <key>PayloadUUID</key> <string>1351BBA0-6092-4125-B930-6AC1C8BCB081</string> <key>PayloadVersion</key> <integer>1</integer> <key>allowApplePersonalizedAdvertising</key> <false/> </dict> </array> <key>PayloadDisplayName</key> <string>Personalised Ads For Mac</string> <key>PayloadIdentifier</key> <string>MacBook-Air-2.198D15E0-F42E-4D15-B8CC-88E05AFF4B05</string> <key>PayloadOrganization</key> <string>Hexnode</string> <key>PayloadType</key> <string>Configuration</string> <key>PayloadUUID</key> <string>198D15E0-F42E-4D15-B8CC-88E05AFF4B05</string> <key>PayloadVersion</key> <integer>1</integer> </dict> </plist> |
In the above configuration profile, the
false: disables the Personalised Ads.true: enables the Personalised Ads.
What happens at the device end?
Once the configuration profile has been successfully deployed, the user will be unable to re-enable Personalised Ads. The option will remain accessible to the user, but it will not change even if attempted.
- To create and customize configuration profiles, you can use tools like Apple Configurator, Profile Manager or manually create them using text editors.
- Use non-encrypted .mobileconfig, .xml, or plist files to deploy profiles across devices.
- Ensure that you do not associate conflicting configurations with the devices.
- Use wildcards to fetch key values from the portal.
- It is recommended to manually validate the configuration profile on a system before executing it in bulk.
- Hexnode will not be responsible for any damage/loss to the system on the behavior of the configuration profile.
