Adobe Campaign Classic supports two Apple Push Notification service (APNs) protocols:
- legacy binary protocol, which is the default protocol for all Campaign Classic versions.
- HTTP/2 protocol, which is already available, and will be the new default protocol starting Campaign Classic 21.1 release.
If you send push notifications with the legacy Apple binary protocol, you need to update to the HTTP/2-based APNs provider API.
Steps to update to HTTP/2 protocol are detailed below.
Check your Campaign Classic build number on all your instances: Marketing server, Execution server, Mid-sourcing server.
If the build number is inferior strictly to 8766, your Campaign version does not support HTTP/2 protocol and needs to be upgraded to a newer version. Learn how to upgrade.
If the build number is 8766 or later, your Campaign version supports HTTP/2 protocol. You need to update your configuration to switch to HTTP/2 protocol.
- As a hosted or hybrid customer, you need to reach out to Adobe Customer Care team to plan this upgrade.
- As an on-premise customer, you need to update your configuration as described in this article.
This procedure applies to Campaign Classic on-premise deployments only, for environments between 8766 build and Campaign 21.1 release.
To migrate to HTTP/2 protocol, update the External account used to perform your iOs deliveries of all your instances (Marketing, Execution, Mid-sourcing), as described below:
Open the External account used to perform iOS deliveries. To identify this external account, make sure the channel parameter is set to iOS channel and the Enabled option is checked, as below: