The sole focus is access and delete requests to satisfy privacy management regulations described here:https://experienceleague.adobe.com/docs/marketo/using/product-docs/core-market...
Adobe Privacy Service integration pertains to privacy service regulations described here:https://experienceleague.adobe.com/docs/marketo/using/product-docs/core-marketo-concepts/mi...
No, there is no difference, and that is by design. The driving force behind integrating the Adobe family of products with Adobe Privacy Service is to provide a consistent "one stop...
The payload must be sent as application/x-www-form-urlencoded (not JSON).For example: POST /rest/asset/v1/landingPage/{id}/content/{contentId}.json?type=RichText&value=<![CDATA[<di...
You could specify the custom field name in the fields parameter. If the custom field has no value, you will get null back in the result[] array in response body. Not a filter per s...
You may need to change your video titles, replace colons ":" with dashes "-". Here is a video from Wistia that describes that process:Soapbox - Important (but small) change to Wist...
You will need to create two requests.http://developers.marketo.com/rest-api/bulk-extract/bulk-lead-extract/#filters "Only the first-set filter will be honored per export job."
The issue was that the example request body was incorrect. You need to specify name="content" (instead of name="text"). Also need to specify filename="name_of_file". Something like...