Skip to main content
Solved

Using additional-fields[profile]=subscriptions does not return accurate information when importing a profie using the API.

  • September 30, 2024
  • 2 replies
  • 47 views

Forum|alt.badge.img

We need to check the subscription status when importing profile updates, so we’re using the additional-field[profile]=subscriptions parameter. This is returning the subscriptions object but the information is not accurate. On a profile that is subscribed to both email and sms, this is what is returned:

"subscriptions": {
    "email": {
        "marketing": {
            "can_receive_email_marketing": true,
            "consent": "NEVER_SUBSCRIBED",
            "consent_timestamp": null,
            "last_updated": null,
            "method": null,
            "method_detail": null,
            "custom_method_detail": null,
            "double_optin": null,
            "suppression": [],
            "list_suppressions": []
        }
    },
    "sms": {
        "marketing": null
    },
    "mobile_push": {
        "marketing": null
    }
}

If I use the API to get the profile by the ID, the correct information is returned.

Best answer by chloe.strange

@mattcoz

I see you had a ticket open with the success engineering team - sharing here for the rest of the community:

The team has rolled out a fix for /profile-imports endpoint. and we should now be accurately returning the subscriptions object as an additional field param when that profile is created/updated.

Hope that helped! 

~Chloe

View original
Did this topic or the replies in the thread help you find an answer to your question?

2 replies

Forum|alt.badge.img
  • Author
  • Contributor I
  • 2 replies
  • October 1, 2024

Ok, so I switched to using the bulk profile update instead, and it’s just returning null.

"subscriptions":null

 


chloe.strange
Community Manager
Forum|alt.badge.img+41
  • Community Manager
  • 426 replies
  • Answer
  • November 21, 2024

@mattcoz

I see you had a ticket open with the success engineering team - sharing here for the rest of the community:

The team has rolled out a fix for /profile-imports endpoint. and we should now be accurately returning the subscriptions object as an additional field param when that profile is created/updated.

Hope that helped! 

~Chloe