Extending the app subscription schema to personalize push notifications

Learn how to extend the app subscription schema to be able to store personalization values Campaign receives from a mobile app.

We would like to personalize the push notifications we send to our subscribers. For this, we will be using information that the mobile app provides us with. For example, the user’s first name which the user enters during registration.
As you can see Laurie have my Android app and I’ve made sure the mobile app channel’s installed on my instance. But before I can start configuring the push notifications, I need to add the additional fields that I want to use for personalization to the database.
I will do this by extending the app subscription schema.
So on the Explorer tab, navigate to administration, configuration and data schemas.
Now I will search for the app subscription RCP table.
That is this one.
Now what I want to do is add two additional attributes to the schema.
So I will click on the new button.
Select create a schema extension and then click next.
Then I need to select the schema.
It’s this one, the app subscription. I click on it, and then on next.
Now let’s add the two new attributes.
Click on insert attribute, and then select type string. I will keep the naming of the attributes neutral. That way we have the flexibility to use them for any parameters.
I will label the first one additional parameter one and add the name, add param one.
And now let me copy and paste this one to create the second custom attribute.
And I’ll just rename it to add param two and additional parameter two. Once it has saved, I will need to apply these changes to the database. To do this, go to tools, advanced and update database structure, click on next.
And again, and here you can review the changes so you can see we’ll be adding the two additional columns to the NMS app subscription RCP table. Now that looks fine so I can click on Next and then Start.
Once this is done, I need to reconnect to make sure that there are no cache issues.
And now let’s take a look. We can see yup, they’re there two new attributes, they’re currently still empty but I can now use them to store the additional information that we collect when the user registers for the service on the mobile app, as an example product interests or any other information that is passed over from the mobile app to Adobe campaign. And now I can go ahead and configure my Android service and create an Android mobile application campaign. -

Next step

Step 2: Configure an Android™ service and create an Android™ mobile application in Campaign