Troubleshooting push identifier sync
This troubleshooting guide requires Adobe Experience Platform Assurance. For more information about access and how to set up Assurance, see the documentation.
When implementing push messaging via the Adobe Experience Platform Mobile SDK, you can validate the client-side implementation by verifying that you completed the following steps:
- Pass the device's push token to the SDK.
- Verify push token sync with the Experience Cloud Identity service.
- Ensure user opt-in for push in Adobe Analytics.
- Confirm user ID is correctly set (and is the same as Steps 2 and 3, above).
Pass the push identifier to the SDK
The setPushIdentifier
API sets the device token for push notifications in the SDK. This results in a few network calls made to the requisite Adobe servers to associate the user with the push token.
If SDK privacy status isoptedout, the push identifier will not be set.
setPushIdentifier
Swift
Syntax
Copied to your clipboardVoid setPushIdentifier(deviceToken: Data?)
Example
Copied to your clipboard// pass the deviceToken that the APNS has assigned to the device.
Objective-C
Syntax
Copied to your clipboard+ (void) setPushIdentifier: (nullable NSData*) deviceToken;
Example
Copied to your clipboard// pass the deviceToken that the APNS has assigned to the device
Java
Syntax
Copied to your clipboardpublic static void setPushIdentifier(final String pushIdentifier);
Example
Copied to your clipboard// retrieve the token from either GCM or FCM, and pass it to the SDK
Swift
Syntax
Copied to your clipboardVoid setPushIdentifier(deviceToken: Data?)
Example
Copied to your clipboard// pass the deviceToken that the APNS has assigned to the device.
Objective-C
Syntax
Copied to your clipboard+ (void) setPushIdentifier: (nullable NSData*) deviceToken;
Example
Copied to your clipboard// pass the deviceToken that the APNS has assigned to the device
Verify push token sync with the Experience Cloud Identity service
Launch your app with the device connected to an Adobe Experience Platform Assurance session.
In the list of events, verify that you have an event with type SetPushIdentifier
. In the details panel on the right, verify the value of the push token for this device. The value in pushIdentifier
is the same value that is sent to the Adobe servers.
Ensure user opt-in for push in Adobe Analytics
Launch your app with the device connected to an Adobe Experience Platform Assurance session.
In the resulting list of events, verify that you have an event with type AnalyticsForIdentityRequest
. In the details panel on the right, you can see that there is a value that was sent to Analytics that opts this user in to receive push notifications.
Confirm that the user ID is correctly set
Launch your app with the device connected to an Adobe Experience Platform Assurance session.
In the list of events, verify that you have an event with type UPDATED_IDENTITY_RESPONSE
. In the details panel on the right, confirm that the following values are correct:
- The value for
pushidentifier
should match the value that was sent in step 2 above. - The value for mid should match the value for mid that is sent to Analytics. If you are using a custom visitor identifier, this payload should also contain a vid variable with a value that matches the value that was used to identify this user.
After completing these steps, your app is correctly configured and is ready to send push messages via the SDK and Adobe.