How to avoid manually adding metadata for each new member separately? Answered
Hi there! I had a quick question...is there a way to make sure that metadata fields are the same for each member when they are created. Right now, it looks like I have to add metadata separately for each member.
Actually one more question. So if the member data that I want have hidden is like a number that needs to be updated every time that user completes a task. For example, they "checked-in" 3 times, would that be better to have this as a metadata or a hidden custom field when using Zapier to update that data?
Thanks so much!
Comments
2 comments
Hey Kelley Cambry, you could update the members automatically with relevant metadata by setting up a workflow in Make / Zapier where you listen to new members created and update the member accordingly. In case you want to do it right from the site, you could consider having the value as a custom field which you could set as hidden input fields if it fits your use-case.
Is this field just for the internal purpose and you won't need to update it from the site ever like via the user / via code?
You could actually use metadata / custom field for this. But the difference lies in the way we can update / modify each one. With custom fields you have more flexibility to let the value be updated via user / via custom code on site if your use-case demands for it, or you could also keep it hidden in pre-built UI and keep it only editable via admins if you want.
With metadata, we don't have both options, its a bit straightforward, it is a read-only field that you can display to users and the only way to edit / modify it would be via Make / Zapier / Memberstack dashboard etc., and not via custom code in site / users can't edit it.
So in case you don't plan to have a lot of custom fields, you could opt for having it as custom field since it could give you both the possibility down the line. But if you do have a lot of custom fields and having this particular field editable via front-end is not something you plan on, you can have it as metadata and it would just do the trick for you. Hope this helps.
No that helps! Right now, I'm leaning toward the metadata. 😃
Please sign in to leave a comment.