An update campaign defines which device or devices receive a firmware update and the firmware image that is installed.
Defining campaigns: manifests and filters
Devices that receive a manifest may reject the update if it does not match the compatibility fields or rules defined in the manifest. This is to avoid firmware created for a specific model or for use by a particular vendor being updated on an incompatible or inappropriate device.
Tip: You may want to use the manifest tool to update a single device, or to upload the firmware and manifest to speed up the development cycle. See the manifest tool tutorial for details.
There are two campaign strategies: continuous and one-shot.
Continuous campaigns are suitable when you need to apply the same update to a changing pool of devices over a period of time. The campaign updates any known devices first, but stays open so new devices receive the update once they register.
One-shot campaigns are suitable for applying an update to a static group of devices. This could be a test group, a set of devices in a region, or a field trial.
See the guide to network traffic for an example calculation of messages between the device and service during an update.