Push Messaging

This troubleshooting guide requires Project Griffon. For more information about access and how to set up Project Griffon, 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:
1.
​Pass the device's push token to the SDK.
2.
​Verify push token sync with the Experience Cloud Identity service.
3.
​Ensure user opt in for push in Adobe Analytics.
4.
​Confirm user ID is correctly set (and is same from 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
Android
iOS
React Native
Java
Syntax
1
public static void setPushIdentifier(final String pushIdentifier);
Copied!
Example
1
// retrieve the token from either GCM or FCM, and pass it to the SDK
2
MobileCore.setPushIdentifier(token);
Copied!
Objective C
Syntax
1
+ (void) setPushIdentifier: (nullable NSData*) deviceToken;
Copied!
Example
1
// pass the deviceToken that the APNS has assigned to the device
2
[ACPCore setPushIdentifier:deviceToken];
Copied!
Swift
Syntax
1
Void setPushIdentifier(deviceToken: Data?)
Copied!
Example
1
// pass the deviceToken that the APNS has assigned to the device
2
ACPCore.setPushIdentifier(deviceToken)
Copied!
Javascript
Example
1
ACPCore.setPushIdentifier("pushIdentifier");
Copied!
Verify push token sync with the Experience Cloud Identity service
Launch your app with the device connected to a Project Griffon 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 a Project Griffon 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 a Project Griffon 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.

Resources - Previous

Troubleshooting Guides

Campaign Push Notifications

Last modified 1mo ago

Export as PDF

Copy link

Contents

Pass the Push Identifier to the SDK

setPushIdentifier

Verify push token sync with the Experience Cloud Identity service

Ensure user opt-in for push in Adobe Analytics

Confirm that the user ID is correctly set