Personalization tags can differ for accounts

  • 1
  • Problem
  • Updated 6 years ago
  • Acknowledged
  • (Edited)
Merged

This conversation has been merged. Please reference the main conversation: Personalization tags are different for older and newer accounts

Hello!

I'm attempting to connect to the myemma api with coldFusion. I was able to use the api example provided in PHP to generate and send my own JSON request. This sort of works - I can add a new email address to my list, but I can't get the first and last name fields to go in.

The odd thing is that the JSON I'm generating is identical to the JSON generated by the PHP example in the api documentation. Here's a sample of what my coldfusion request is generating:

{"group_ids":[groupid],"fields":{"first_name":"first","last_name":"last"},"email":"exampleemail@domain.com"}

Sending this as an http post will result in the email being added to the list I want, but not the first and last name. Any help would be greatly appreciated. Thank you!
Photo of Great Lakes

Great Lakes

  • 4 Posts
  • 0 Reply Likes

Posted 6 years ago

  • 1
Photo of Ben Vance

Ben Vance, Alum

  • 328 Posts
  • 14 Reply Likes
Hi! Thanks for posting your question. The Emma support team doesn't offer one-to-one assistance for writing or troubleshooting API code, but we do have some extensive documentation available here:

http://api.myemma.com/

I do want to note one issue that we're aware of that could be interfering here. Some of our accounts are currently set to use name fields like this:

first_name
last_name

while some older accounts are set like this:

name_first
name_last

They should work interchangeably, but we're chasing a bug right now that makes them not. I would try reversing those field names in your API calls to see if that helps. Beyond that, I'm afraid we won't be able to offer more assistance.
Photo of Great Lakes

Great Lakes

  • 4 Posts
  • 0 Reply Likes
Hello Ben,

Thank you for your reply. After changing the name variables to name_first and name_last it worked just fine. That was it!

I took another look at your API documentation and didn't see anything about this issue. You may want to update your instructions to include it - just a mention, since its a known bug.

Thanks again!
Photo of Ben Vance

Ben Vance, Alum

  • 328 Posts
  • 14 Reply Likes
Glad this worked out for you! If we can help with anything else, let us know.