Subscriber Application to Recipient Linking

[Neelam1991]

Hi All,

Hope you are doing great.

We are planning to migrate from v7 to v8. Currently, our v7 setup is a hybrid model, and there are significant duplications among recipients, which is causing issues with billing based on unique profiles. Additionally, this client has three different apps, and each app's user ID is stored in the User ID field of the Subscriber Application table. As a result, when a single user installs all three apps on the same device, three different entries are created with distinct User IDs but the same Device ID. This duplication is again causing problems with billing. In v8, we plan to use Customer ID as the unique key for Recipient table. And we would like to map the User Id with the CustID field. Is there a way to link the Subscriber Application with the Recipient schema in v8 to mitigate this redundancy issue ?

Please advice.

Regard's,

Neelam

[_Manoj_Kumar_]

Hello @Neelam1991 

Could you provide more information on why there are three apps? The active profile is only taken into account when an actual email or push notification is sent to a record; otherwise, it won’t be considered.

To address this, you can implement a de-duplication process to ensure a single profile is consistently selected when sending communications.

[Neelam1991]

Hi @_Manoj_Kumar_ ,

The client is a mutual fund company, and they have three different apps, each serving a specific purpose. One app is for distributor login, another for investor login, and the third is a savings-related app. The distributor app is exclusively for distributors and requires a unique distributor ID for login. For the other two apps, users can register through one of three options: email ID, PAN, or mobile number. Consequently, a single customer may have three entries if they register on all the apps.

Each time a user registers through an app using one of the three key values, an entry is created with a combination of UserID, MobileAppId, and Token. If the user re-registers, a new entry is generated (UserID + MobileAppId) along with a new token.

How do we link Subscriber application with Recipient to keep customer User ID in Recipient and to keep CustID in SubApp achema ?

How does billing process work for Recipient and Subsciber application ?