|
PropertyNL PropertyNL
|
July 24, 2018 at 8:05 am
Why is our Mailchimp integration skipping the Address field?
It is set up correctly inside of the events backend, but in Mailchimp on every contact that comes via the API, there is no address.
|
|
PropertyNL PropertyNL
|
July 24, 2018 at 8:07 am
For example this event.
http://propertyeu.staging.wpengine.com/wp-admin/admin.php?page=espresso_events&action=edit&post=22654&edit_nonce=d69445ac5d
Support member Tony has access to our staging website’s backend already.
|
|
PropertyNL PropertyNL
|
July 24, 2018 at 8:12 am
Also, might have to do with this: in the backend of an event, the first 3 fields are pre-filled, but starting from Address, we have to fill these in ourselves everytime.
Is this issue connected?
|
|
Tony
|
July 24, 2018 at 8:51 am
Support member Tony has access to our staging website’s backend already.
We do not keep login details for longer than required to fix the issue we requested the login details, so I do not have access to your site any longer and you can remove the account you created should you wish.
Also, might have to do with this: in the backend of an event, the first 3 fields are pre-filled, but starting from Address, we have to fill these in ourselves everytime.
That’s expected, but when you select the correct field the address info is sent to MailChimp?
|
|
PropertyNL PropertyNL
|
August 9, 2018 at 3:46 am
That’s expected, but when you select the correct field the address info is sent to MailChimp?
Yes, they are being sent to Mailchimp in fact, except for the Address field.
In Mailchimp, the address field is present but empty for everyone.
|
|
Tony
|
August 9, 2018 at 6:07 am
If you view the EE contact for one of these registrations, does it show the Address 1 field?
You can view this in Event Espresso -> Registrations -> {registration} -> View contact – http://take.ms/a5fk1
Then look in the details there, is Address 1 set on the registration?
|
|
PropertyNL PropertyNL
|
August 17, 2018 at 5:09 am
They do have an address in EE, yes.
|
|
PropertyNL PropertyNL
|
August 17, 2018 at 5:09 am
|
|
Tony
|
August 21, 2018 at 4:31 am
Hmm, it’s most likely the same problem from your last thread.
I’ll take a look if you can send login details over using this form:
https://eventespresso.com/send-login-details/
|
|
PropertyNL PropertyNL
|
August 21, 2018 at 7:43 am
All right info sent. Looking forward to hearing about cause of the problem.
|
|
PropertyNL PropertyNL
|
August 30, 2018 at 12:42 am
Is there still a problem with logging in or is it hard to find the cause of this bug?
|
|
Tony
|
August 30, 2018 at 5:15 am
Hi there,
Apologies for the delay, the login credentials work fine.
However, going through the MailChimp code and then outputting the details EE is sending to MailChimp shows the address field IS being sent to MailChimp, see here – http://take.ms/v7W9P
That’s a log of the list subscribe call made on your site which shows the value is there.
In your merge vars on MailChimp, is the address field set to type address or text? If its set to ‘Address’ that will likely be the problem.
I did some digging and it looks like MailChimp expect merge vars of type address to be in a specific format, I haven’t been able to find any documentation on MailChimp’s end but I did find this:
https://gist.github.com/strangerstudios/d473abb787ada311bd777e6ae0f587e6
Which would lead to MailChimp expecting an array of fields for ‘address’ types.
If I create a merge field on one of my lists and set the type to address, then send that merge var the same value as an address merge var with a type of text, I get a value in the text field, not the address field – http://take.ms/T8a36
(That’s from the same request just using the same value)
I’ll do a little more testing to confirm this, but I think if you change the address field to use a text field it will work as expected. The annoying part is MailChimp don’t let you change a merge field type after it has been created so you’ll likely need a new merge var, then update the events to use that var in place of the other…. however test that on a single event first to confirm it works with a text field.
|
|
Tony
|
September 5, 2018 at 2:38 am
Hi there,
I’m just wondering if you have had a chance to work through the above and if it did indeed fix the problem with your subscriptions?
|
|
PropertyNL PropertyNL
|
September 7, 2018 at 3:53 am
All right well I get the problem.
Now isn’t it the EE Add-on’s job to handle this? The Address merge tag as an address type field is standard in Mailchimp. It always expects an array.
In EE: city, zip, country and address are all system questions.
In Mailchimp, address is a default field, expecting the above named values in an array by default.
For now I think the best thing to do then is adding a text field called Address.
I will do that and test.
|
|
Tony
|
September 7, 2018 at 4:32 am
Now isn’t it the EE Add-on’s job to handle this? The Address merge tag as an address type field is standard in Mailchimp. It always expects an array.
Maybe so, but as mentioned, this is the first I’ve seen of this and I couldn’t find any documentation from MailChimp regarding the Address merge field.
Do you have any links to MailChimp documentation that show it always expects an array? I couldn’t find any.
If there’s documentation that states this I can create a ticket for our developers to investigate further and see what we can do.
In EE: city, zip, country and address are all system questions.
That they are but that doesn’t prevent you from using them as single text fields, right now EE doesn’t collect them as an array and it doesn’t store them as an array. The MailChimp add-on could build the address fields into an array, however, it’s also going to query MailChimp to confirm if the field set is type address and I’m pretty sure we don’t want to do that on every field (MC rate limit API requests).
|
