Newletter Subsciption Interaction location ID with API_MKT_CONTACT_SRV

[pankaj_1383]

Hi All,

Request your help on the below issue related to missing location ID in the Mkt permissions/subscription interactions with the API API_MKT_CONTACT_SRV;v003.

As per the help documentation, it is not possible to import the subscription/permission interactions via the interactions API. https://help.sap.com/viewer/e68e4c8c856d429b85c2a7370c3553ae/2020.YMKT/en-US/6322d15482854566a72f6c9... . So, these are being created via the permissions and subscriptions entities for the API_MKT_CONTACT_SRV.

We are passing the below information in the Marketing location entity, but the location ID is not updated in the Interactions table for interactions: MKT_PERM_OPTIN & NEWSLETTER_SUBSCR.

Below the sample payload for the Mkt location entity, part of batch request:

Subscription:

^{PUT MarketingSubscriptions(ContactID='abc@abc.com',ContactOrigin='Z_WEBSHOP',ContactSubscriptionID='abc@abc.com',ContactSubscriptionOrigin='EMAIL',CommunicationMedium='EMAIL',SubscriptionTopic='1') HTTP/1.1}

^{Accept: application/json}

^{Sap-Cuan-RequestTimestamp: '2021-05-26T13:13:18'}

^{Sap-Cuan-SourceSystemType: EXT}

^{Sap-Cuan-SourceSystemId: EXT}

^{sap-cuan-referenceid: REQ1}

^{

^{"SubscriptionUTCDateTime" : "2021-05-26T13:13:18",}

^{"SubscriptionSignUpExists" : "Y",}

^{"SubscriptionSourceCommMedium" : "WEB",}

^{"IsConfirmationRequired" : false}

^}

Marketing Location Entity:

PUT MarketingLocations(ContactID='abc@abc.com',ContactOrigin='Z_WEBSHOP,MarketingLocationOrigin='SAP_RETAIL_STORE',MarketingLocationExternalID='ST1') HTTP/1.1

Accept: application/json

Sap-Cuan-RequestTimestamp: '2021-05-26T13:13:18'

Sap-Cuan-SourceSystemType: EXT

Sap-Cuan-SourceSystemId: EXT

sap-cuan-referenceid: REQ1

Content-Type: application/json

{

"MarketingLocationOrigin" : "SAP_RETAIL_STORE",

"MarketingLocationExternalID" : "ST1"

}

Regards,

Pankaj

[pankaj_1383]

Hi Christian,

Thank you for your feedback.

We have our segmentation for contacts subscribed in Retail store, and on ecommerce site. This is based on the marketing location of the Newsletter subscription interactions. In the earlier release (1709 SP01), we were using the CUAN IMPORT API for posting the subscription interactions at the time of contact onboarding.

However, after the upgrade, we migrated to API_MKT_CONTACT_SRV API for onboarding from ecommerce site. It does not update the contact marketing location for the for interactions: MKT_PERM_OPTIN & NEWSLETTER_SUBSCR

Since the new Interaction API does not allow posting of subscription/interactions either, the process is broken.

Could you please share pointers for any alternatives in this case?

BR Pankaj

[former_member737455]

Hi Pankaj

The import of the MarketingLocation will be done on contact basis not on interaction basis.
I am afraid, it is not possible to add a MarketingLocation ID to permission interactions.

Can you explain your use case - maybe there are other alternatives ready for you.

BR Christian