AJO to SFMC Custom Action integration | Community
Skip to main content
I
iamsuchith
Level 2
January 31, 2024
Solved

AJO to SFMC Custom Action integration

  • January 31, 2024
  • 3 replies
  • 1901 views

Hello,

  We got stuck with creating custom action to SFMC and would appreciate any suggestions from this group.

 

 1) We followed the steps to configure Custom Action from this article by @anuhya-tad .Expect that we are sending the audience to SFMC's Data extension.

 2) Custom  Action Configuration :

               (i) We were able to successfully test the authentication.

               (ii) Endpoint Configuration : Provided SFMC's Endpoint along with Data extension / Method : POST

               (ii) Payloads: ( Are these action parameters defined in the article?)   What format should this be ? We gave the below , is that correct?

3) Journey : Created JOurney with Read Audience and the SFMC Custom Action.. Are we missing anything there? Should we do source to target mapping  anywhere?

 

Please suggest? -- Thanks for all the help!

 

 

{
"items": [
{
"subscriberKey": "Peter@Ajoski.com"
"FirstName": "Peter",
"LastName": "Ajoski",
"EmailAddress": "Peter@Ajoski.com",
}
]
}

 

https://medium.com/@anuhyareddy.y/ajo-jo-sending-email-delivery-via-3rd-party-marketing-automation-tool-sfmc-bef8cc7d7e10

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SatheeskannaK

@iamsuchith, I wanted to call out that when you're posting the data into the SFMC data extension it will be an individual payload for each profile from AJO. You can't stringify the bulk of the AJO profile payload and send it to SFMC. Otherwise, once you configure the custom action in administration steps given are correct. When you pull the custom action in a journey after the read audience map the attributes to the payload defined in the custom action. 

You can use this payload to drop it in the custom action when you setup,

{
"items": [
{
"subscriberKey": {
"toBeMapped": true,
"dataType": "string",
"label": "Subscriber Key"
},
"FistName": {
"toBeMapped": true,
"dataType": "string",
"label": "First Name"
},
"LastName": {
"toBeMapped": true,
"dataType": "string",
"label": "Last Name"
},
"Email Address": {
"toBeMapped": true,
"dataType": "string",
"label": "Email Address"
}
}
]
}

3 replies

Mohan_Dugganab
Adobe Employee
Mohan_DugganabAdobe Employee
Adobe Employee
January 31, 2024

If the intent is to send an object for every profile, the payload would be as follows. It then allows you to map these parameters from the respective source attribute in the journey canvas.

 

{
"items": {
"subscriberKey": {
"toBeMapped": true,
"dataType": "string",
"label": "subscriberKey"
},
"FirstName": {
"toBeMapped": true,
"dataType": "string",
"label": "FirstName"
},
"LastName": {
"toBeMapped": true,
"dataType": "string",
"label": "LastName"
},
"EmailAddress": {
"toBeMapped": true,
"dataType": "string",
"label": "EmailAddress"
}
}
}

 

Do refer to the following documentation on the limitations and best practices 

 

https://experienceleague.adobe.com/docs/journey-optimizer/using/configuration/configure-journeys/action-journeys/about-custom-action-configuration.html?lang=en

 

 

    SatheeskannaK
    Community Advisor
    SatheeskannaKCommunity AdvisorAccepted solution
    Community Advisor
    January 31, 2024

    @iamsuchith, I wanted to call out that when you're posting the data into the SFMC data extension it will be an individual payload for each profile from AJO. You can't stringify the bulk of the AJO profile payload and send it to SFMC. Otherwise, once you configure the custom action in administration steps given are correct. When you pull the custom action in a journey after the read audience map the attributes to the payload defined in the custom action. 

    You can use this payload to drop it in the custom action when you setup,

    {
    "items": [
    {
    "subscriberKey": {
    "toBeMapped": true,
    "dataType": "string",
    "label": "Subscriber Key"
    },
    "FistName": {
    "toBeMapped": true,
    "dataType": "string",
    "label": "First Name"
    },
    "LastName": {
    "toBeMapped": true,
    "dataType": "string",
    "label": "Last Name"
    },
    "Email Address": {
    "toBeMapped": true,
    "dataType": "string",
    "label": "Email Address"
    }
    }
    ]
    }
    Thanks, Sathees
      I
      iamsuchithAuthor
      Level 2
      February 5, 2024

      @mohan_dugganab @satheeskannak  Thanks so much for both of your comments. Payload from both of you enabled the mapping parameters to shown in custom action but we have used Saathees's payload. 

       

      We were able to map the fields and activated the journey but we are not seeing the records getting loaded into  SFMC's data extension. Is there a way we can debug within the journey and see where the problem is? 

       

      fyi.. the authentication to SFMC is successful though. Appreciate if you have any suggestions.  

      SatheeskannaK
      Community Advisor
      SatheeskannaKCommunity Advisor
      Community Advisor
      February 5, 2024

      @iamsuchith, I would suggest posting the same/part payload to a public mock API (ex. https://www.mockaroo.com/) to test out whether it's posting data. If the data getting posted to the public mock API then it's a problem with the SFMC data extension setup. Another way is to test by sending the payload from Postman to the SFMC data extension to find out if that works.

      Note: Remember to remove the testing data from the public mock API.

      Thanks, Sathees
        Terms & ConditionsAccessibility statement

        Loading footer...