Push notification to NOT REGISTERED (not on Recipient) user | Community
Skip to main content
salvdangelo
salvdangelo
Level 5
June 6, 2019
Solved

Push notification to NOT REGISTERED (not on Recipient) user

  • June 6, 2019
  • 5 replies
  • 6473 views

Hello all,

I have an implementation question for you:

1) How is it possible to send a push notification to a user/device without having him/her on Recipient table?
It would be sufficient to have a different TARGET MAPPING? If so, how should I configure it? Could you give an example?

2) Is it possible to extend App Subscription table with additional information passed by the mobile app (in order to have a minimal personalization in the notification template)

Thank you so much!

Salvatore

PS: exclude transactional push notification as a solution

Jean-Serge Biron

@Vapsy

Amit Kumar​

Adhiyan​

Ananya Kuthiala​

@Garima_Gakhar

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Adhiyan

    Hi Salvatore,

    Usually the storage dimensions are same as in the OOB target mapping .

    You may not need to add any additional fields if not required.

    So I suggest , use the OOB schemas for message and tracking logs but keep the additional fields section empty.

    Regards,
    Adhiyan

    5 replies

    Adhiyan
    Adobe Employee
    AdhiyanAdobe Employee
    Adobe Employee
    June 6, 2019

    Hi Salvatore,

    Yes this is possible by changing the target mapping.

    You should target the nmsAppSubscriptionRcp table directly instead of creating a Join with the recipient table.

    So the new mapping would look like :

    As opposed to the OOB Mapping of :

    For the second point, I think this is possible as I see implementations with extended app subscription fields already present with data being fed into that table.

    Regards,

    Adhiyan

      salvdangelo
      salvdangeloAuthor
      Level 5
      June 6, 2019

      Hello Adhiyan​ ,

      First of all thank you for the response.
      Regarding the target mapping, could you explain me how to configure this section?

      In particolar, if this is exactly the same for OOTB target mapping or you need to use custom tables for Delivery log and Tracking log and which additional filed to put

      Thank you!
      Salvatore

      salvdangelo
      salvdangeloAuthor
      Level 5
      June 7, 2019

      Hello Adhiyan​,

      Any indication on my previous message?

      Thanks in advance,
      Salvatore

      salvdangelo
      salvdangeloAuthor
      Level 5
      June 12, 2019

      Hello Adhiyan, all,

      Could you give me any further indication on the configuration of the "target mapping" ?

      I have problem with "Storage" tab settings.

      Thank you all,
      Salvatore

      Adhiyan
      Adobe Employee
      AdhiyanAdobe EmployeeAccepted solution
      Adobe Employee
      June 12, 2019

      Hi Salvatore,

      Usually the storage dimensions are same as in the OOB target mapping .

      You may not need to add any additional fields if not required.

      So I suggest , use the OOB schemas for message and tracking logs but keep the additional fields section empty.

      Regards,
      Adhiyan

      Terms & ConditionsAccessibility statement

      Loading footer...