ACS Shared Audiences - VisitorID for push notifications

Description

The customer has the following scenario: he would like to integration VisitorID shared audiences (as he doesn’t have AAM so no DeclaredID).
The scenario is the following:

• The customer doesn’t use emails just Push notifications
• The customer is exporting audiences from people core service with VisitorID

Resolution

Question –

The customer has the following scenario: he would like to integration VisitorID shared audiences (as he doesn’t have AAM so no DeclaredID).

The scenario is the following:

• The customer doesn’t use emails just Push notifications
• The customer is exporting audiences from people core service with VisitorID

According to the online documentation, the visitor ID is set if a customer clicks the email but in our case we have PUSH NOTIFICATIONS

Do the ACS VisitorID Shared Audience reconcile against push notification ECID?

How can I reconcile a customer with VisitorID without using Emails but just push notifications?

Also, Do the ACS VisitorID Shared Audience reconcile against push notification ECID? I cannot look into the OOB workflow code.

Probably I can do a custom workflow to read the audiences via S3 and then reconcile againt ECID in appSubscriptionRcp, but I would like to get your opinion.

Any Idea? How can I reconcile VisitorID shared audiences with push notifications? The customer won’t use the email channel.

SOLUTION –

It seems there is no way to do reconciliation of ECID from app subscription, as we do for email.

I believe the only option is to consider ECID as a declared ID. Store ID in your profile and create an AMC connection to use this field for reconciliation.

We’ve done a POC for Mediacorp in Singapore for the same and it works.

It doesn’t matter if your customer doesn’t have AAM. You can still use declared ID