How to fill custom fields

  • Resolved mikesale

    (@mikesale)


    5 years, 7 months ago

    Love the new feature to add custom fields but I have a question relating to the current instructions:

    Example: customfield=value,custom=value2. Separate them with comman but DO NOT use spaces.

    1. What does “customfield” map to?
    2. What does “value” map to?

    I have a custom field in Moosend with the following attributes:
    Tag: #recipient:Started Email Sequence#
    Field ID: 8c1c3614-9013-4700-89aa-edd457d139d7

    I have a hidden field in the elementor form with field ID:
    Automation_seq_healthcheck
    It has a default value of “initialzed”

    Can you confirm that the new “Custom Fields” should be set as follows:
    Automation_seq_healthcheck=8c1c3614-9013-4700-89aa-edd457d139d7

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Jose Sotelo

    (@josesotelocohen)

    Hello @mikesale

    You need to add the Field Name, not the Tag.

    So it would be: Started Email Sequence=initialized. Here, Started Email Sequence is the customfield in the example, and initialized is the value.

    So, Started Email Sequence=initialized is customfield=value.

    I didn’t test it with a Field Name with spaces, so I don’t know if it will work with “Started Email Sequence”, or if you will need to change it to StartedEmailSequence until I find a solution.

    For all the other fields you have to use the Field Name too:

    Name: name. (This one is the ID of the Elementor Form Field ID, which is name by default)
    Email: email. (This one is the ID of the Elementor Form Field ID, which is email by default)
    Custom Fields: StartedEmailSequence=initialized,anotherCustomField=yes,etc.

    I will add more screenshots and examples for this to make it clearer.

    Regarding the hidden field, it won’t be sent to Moosend because it isn’t mapped in the integration, what’s the use case?

    • This reply was modified 5 years, 7 months ago by Jose Sotelo.
    Thread Starter mikesale

    (@mikesale)

    One use case is that I can pass in the value to a hidden fields that helps determine source, intent or other attribute of the subscriber as well as set it with a default value if none is set. One example is to have hidden fields for UTM values.

    Another even more common use case to pull custom field values from the form, Phone number, business name, budget size, purchasing authority, etc… right now, from what I can tell, the only thing someone filling out the form can set into custom values in Moosend is name and email. Everything else must be essentially constants set at the time of form design. Please correct me if I’m wrong.

    Plugin Author Jose Sotelo

    (@josesotelocohen)

    Hello @mikesale,

    Just released a new version that should allow you to handle this.

    Please, try it out and let me know.

    Cheers!

    Thread Starter mikesale

    (@mikesale)

    Thank you! I will get a chance to check this out this week.

    Will previously setup forms break on update?

    Plugin Author Jose Sotelo

    (@josesotelocohen)

    @mikesale No, they shouldn’t break as the only required field is email, so not having any custom fields won’t cause any errors.

    Plugin Author Jose Sotelo

    (@josesotelocohen)

    @mikesale if you were using the previous static custom fields then it won’t work, you will have to adapt them to the new dynamic fields.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘How to fill custom fields’ is closed to new replies.