Skip to main content

I am using the ACF custom field name “accessibility_expiry” in map to a MailerLite field. It is a date field, but when the Zap takes place it does not have the correct date that is in the User field in Wordpress, but shows the date the Zap was sent over. Is there something I am missing that I should be putting in the Map Field to bring the exact date as shown in Wordpress?

Hi there @matchrecall,

Welcome to the Community! 🎉

Before we dig deeper into this, would you mind sharing a detailed screenshot of how your Zap is configured? Also, please share a screenshot of the “Action” section of the action step that shows all of its fields. Like so:

46dd6c0979e3d815d621b8da43084ef1.png
(view larger)

Please don't include personal information in the screenshot, or be sure blur out any personal information.

Thanks!


Hi @matchrecall 👋

Did you manage to get this sorted? 

If so, would you be up for sharing some details on what the solution was? We’d really appreciate it as this would be so helpful to others in the Community here that are having similar issues! 🙂

If not, can you check the run details in the Zap history and confirm whether the value that comes over from WordPress in that accessibility_expiry field definitely contains the correct date? If it does, perhaps there’s an issue with the timezone settings or formatting of the date that is causing the wrong date to be added to MailerLite - see our Zap dates or times are incorrect guide for details. Do you think that could be the case here?

Looking forward to hearing from you on this!


Unfortunately, I could not figure out and had the developer of my Wordpress site figure it out and fix. I’m not sure what he did. Sorry 


Hi @matchrecall,

 

We are glad that the issue is already fixed. If you do have further questions, please don’t hesitate so ask us here in the Community.

 

Cheers.


Reply