Skip to product information
1 of 1

How to obtain and save date of birth and gender information when registering as a member with Shopify [Organizing requirements and design]

How to obtain and save date of birth and gender information when registering as a member with Shopify [Organizing requirements and design]

View full details

This time, I will briefly summarize what I thought about when organizing the requirements and design for how to obtain the date of birth and gender at the time of member registration with Shopify and how to save each as customer information.

Please let me know if you think it would be better to do something like this!

I will summarize the implementation using Liquid and ShopifyFlow at a later date.

First, share the final product

Here are the input items added to the member registration page.

Here is how the input contents are reflected in the customer information.

In customer notes, birth year, birth month, and gender

Birth month and birth year in metafield

tag to gender

This request

This time's request remains the same, but it says something like ``I want to be able to obtain date of birth and gender.''

The reasons for wanting to obtain date of birth and gender are as follows.

  • I want to distribute birthday coupons.
  • I also want to be able to separate segments by age and gender.

Reasons for choosing each implementation method

In response to this request, I think there are roughly the following points:

  • Whether the year, month, and day are all required when obtaining the date of birth.
  • how to get date of birth
  • Is it better to store the retrieved date of birth and gender in a meta field or in a customer tag?

Regarding the above three points, I will briefly summarize ``why and what kind of implementation was done''.

Whether the year, month, and day are all required when obtaining the date of birth.

The conclusion is as follows,
Only the birth year and birth month are retrieved, but the birthday is not retrieved.

There are two reasons
The first point is that if you only need the year and month, you can send birthday coupons (or more accurately, birth month coupons) and segment by age group.
The second reason is because I thought it would be easier to enter as few input items as possible.

how to get date of birth

The conclusion is
Information is now obtained from a drop-down list where you can select the year and month of birth.

There are two reasons
The first reason is that I think it will be easier to process later (processing with ShopifyFlow) if you obtain the birth year and birth month data separately.
The second point is that the typical calendar-like display makes it difficult to select the date of birth.

A typical calendar-like display

Is it better to store the retrieved date of birth and gender in a meta field or in a customer tag?

First, I decided to store the birth year and birth month in a meta field.

The reason is that we thought it would be easier to use when creating segments if the year and month data types were stored as numbers (between ~ and ~, greater than ~, etc.)

Next, for gender I decided to store it in the customer tag

Regarding the reason for storing the gender in the tag, I thought, ``If I keep it as a tag, I might be able to use it in some apps in the future.'' (For example, if the gender is tagged as ``male,'' (Set settings like 〇〇 in some app)

summary

  • First of all, don't accept the request at face value, and sort out what you want in the end.
  • Find the best combination to achieve your requirements
    • In this case, things like ``How do I use date of birth and gender?'' ``What data format do I save the information in for that purpose?'' ``How do I acquire the information for that purpose?''
  • While meeting the requirements, be careful not to become too egotistical on the store side or to cause unnecessary stress on the customer side.

By the way

At first, I thought it would be easy since I only needed to get the date of birth and gender.

However, when I actually researched and thought about it, I realized that there are so many different ways to do it, and to be honest, it can be quite confusing.

I learned a lot, not only about the solution itself, but also the process of reaching that choice, so I decided to output it again.

Also, "organize your requests and choose the one that is considered the best from among many methods."
Personally, I think it was a big accomplishment for me to realize that maybe I like this process.