Skip to Content
0
May 11, 2021 at 06:19 PM

Problem with setting Permission for Email (API_MKT_CONTACT_SRV_0003)

165 Views Last edit May 11, 2021 at 06:41 PM 3 rev

Hello community,

we are using an external system for our customer registration (and administration) process. In this process the customers have the option to subscribe to our newsletter. As marketing tool we use the SAP Marketing Cloud. The external system is transmitting all customers to the Marketing Cloud, which subscribe to the newsletter.

Therefore we use the Contact API (version 3) of the Marketing Cloud (link). We use the endpoints for ContactOriginData (to create the contact), MarketingPermissions and MarketingSubscriptions. The connection is direct, without any middelware.

The creation of contacts and the setting of the newsletter subscription works well. But we can't set the permissions. In the contact view -> Permission Marketing tab, there is no opt in for the permission (Email). And the really strange thing on this behaviour is, the contact has an interaction of type "Opt In for Marketing Permission" (see screenshots & example request below).

We also have a second external system (SAP Commerce) which is transmitting contact data to the same SAP Marketing Cloud instance. In this case we use the SAP Cloud Platform Integration as middleware. There we also transmit permissions for Email. And this works fine, the opt ins are set and also there are interactions of type Opt In for Marketing Permission.

We compared the transmitted data, but it's same (same fields are filled, same endpoints).

Does anyone had similar problems or knows a possible reason of this behaviour?

I would be grateful for any help.

Best Regards

Torsten

-----

Further informations:

Example request from the external system:

--changeset_695af0de-aa06-4fa7-a2d7-0abfebcde309
Content-Type: application/http
Content-Transfer-Encoding: binary

PUT ContactOriginData(ContactID='123456789',ContactOrigin='CUSTOM_ORIGIN')
HTTP/1.1
Content-Type: application/json
Accept: application/json
{
"OriginDataLastChgUTCDateTime":"2021-04-16T07:24:56.040721",
"EmailAddress":"example@test.com",
"IsConsumer":true,
"GenderCode":"1",
"BirthDate":"1980-05-11T00:00:00",
"FullName":"Example Test",
"FirstName":"Example",
"LastName":"Test",
"StreetName":"AnyStreet 1",
"ContactPostalCode":"12345",
"CityName":"AnyCity",
"PhoneNumber":"+4912 456789",
"Industry":"PRIV"
}

--changeset_695af0de-aa06-4fa7-a2d7-0abfebcde309
Content-Type: application/http
Content-Transfer-Encoding: binary

PUT MarketingSubscriptions(ContactID='123456789',ContactOrigin='CUSTOM_ORIGIN',ContactSubscriptionID='example@test.com',ContactSubscriptionOrigin='EMAIL',CommunicationMedium='EMAIL',SubscriptionTopic='000000001')
HTTP/1.1
Content-Type: application/json
Accept: application/json
{
"SubscriptionUTCDateTime":"2021-05-11T10:06:22.864",
"SubscriptionSignUpExists":"Y",
"SubscriptionTopicName":"Custom Newsletter",
"IsConfirmationRequired":false,
"SubscriptionNoteText":"Subscription on Registration"
}

--changeset_695af0de-aa06-4fa7-a2d7-0abfebcde309
Content-Type: application/http
Content-Transfer-Encoding: binary

PUT MarketingPermissions(ContactID='123456789',ContactOrigin='CUSTOM_ORIGIN',ContactPermissionID='example@test.com',ContactPermissionOrigin='EMAIL',MarketingArea='CUSTOM_MKT_AREA',CommunicationMedium='EMAIL') HTTP/1.1
Content-Type: application/json
Accept: application/json 
{
"CommunicationMedium": "EMAIL", 
"ContactID": "123456789", 
"ContactOrigin": "CUSTOM_ORIGIN", 
"ContactPermissionID": "example@test.com", 
"ContactPermissionOrigin": "EMAIL", 
"MarketingArea": "CUSTOM_MKT_AREA", 
"PermissionUTCDateTime": "2021-05-11T10:06:22.864", 
"PermissionGranted": "Y", 
"PermissionNoteText": "Permission on Registration"
}

Contact Overview: interactions:

a

Opt in interaction details:

Permission Marketing tab:

Attachments