Inserting other personalisation fields while creating a landing page

Hi thanks both for your reply, I didn't realise changing the Properties on the flow would change the fields the App could look at.

To answer your question Florent, yes, all fields would be related to the recipient. So when they click on the link, they're taken to a web page that displays their information to print out. Here's a screen grab from the Page element. The fields with "%%" around them are the fields I'd like personalised.

I've managed to find the membership no, first name and last name now but to attach a coupon... I'm finding that difficult.

Also wanted to know if I can add my own dates based off the rec DOB? i.e. the coupon would be vaild until 2 days after their birthday...

Hi Kevin,

AC classic (v6/v7) webApp are absolutely not stuck to nms:recipient schema.

You can define in the webApp properties the default schema used by your webApp in the Storage Document list.

Then the form of a webApp activity (standard, it means v6/v7, or webApp v5 compatibility page) will rely on this schema by default.

The difference is that a default webApp page activity is stuck to the schema defined in the properties, while the webApp page compatibility v5 is not, and is able to manage more powerful objects and schemas queries but is far less convenient for css styling/responsive design.

Regards.
J-Serge

Hi Kevin,

I assume that for landing pages (which are intended to be used by recipients), only recipient related information can be accessed in that context.

Are there many data that you want to add and that is not related to recipients?

Florent