cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Custom Key in Landing Pages

Former Member
561

Hello Experts,

I am working on landing pages and we intend to use the landing pages not only as a url within email's unsubscribe link but also as a regular page to manage marketing permission for end customer. We have kept email address as shareable, now other than unsubscribe link we want end users to login to our page and update there marketing permissions, we do have a custom primary key which identifies each customer uniquely but the issue we face is that when we use just the two fields of email address and Z_primary key, the landing page throws a technical error as it does not understand the key and its mapping which has been done. so to give you an example, what we have is like below.

CUS_Name- A1, Email- abc@xyz.com Z_Key - 123

CUS_Name- A1, Email- abc@xyz.com Z_Key- 456

I have designed landing page with just three fields Name Email & Z_KEY, since the email and names match the only key left is Z_Key but when we test it fails with a technical error and the permissions are not updated as I assume the system is not taking the key into the account to identify the customer. Has anyone tried this scenario or the custom fields are not supported for identification?

Thanks

Vineet

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi All,

I found a BADI CUAN_CP_DETERMINE_CONTACT which can be used to influence the contact determination based on the Landing page data so with a slight customization I am able to achieve the functionality I am looking for, however my question still remains open regarding the custom fields, does the standard Landing page integration not support the custom fields during the contact look up when the fields are part of the CUAND_CE_IC_ROOT table structure. I believe this should be done as part of standard so that all the fields extended in contact root are also used in look up for contact determination as it does not make sense for me to expose these fields in the Landing Page and then not consider them to influence the contact determination. Probably an enhancement feature for next releases?

As of now my problem has been solved. 🙂

Thanks

Vineet

Answers (2)

Answers (2)

JanMatthes
Product and Topic Expert
Product and Topic Expert
0 Kudos

arne.mantheyCould you please help?

Former Member
0 Kudos

jan.matthes, kunalkumar.bansal, theodor.lungstras any idea on how to get around the problem.


Thanks

Vineet

JanMatthes
Product and Topic Expert
Product and Topic Expert
0 Kudos

arne.manthey: Could you please take over and answer?

KunalBansal
SAP Champion
SAP Champion
0 Kudos

Hi Vineet,

As discussed over call, please send the detailed use case to me via email and I will discuss further.

Thank you.

Best Regards,

Kunal

Former Member
0 Kudos

arne.manthey kunalkumar.bansal ,


This is what we want to achieve, Identification of customer based on Primary key as email is shared and name could be same, but the system is not taking into account the custom key even when it is exposed and made available for use in Landing pages.


Thanks

Vineet