Customer Metafields let you store custom data on Shopify profiles, beyond what Shopify natively supports, such as the email, name, and address. This integration will allow you to store data from the quiz, the customer's answers, and results pages into their profiles.

First, if you see a banner like this on your Octane AI dashboard:

Make sure to click Update permission. This ensures that Octane AI has all the necessary permissions to populate the Customer Metafields in your Shopify store.

If you do not see this banner, this means all the necessary permissions are already accepted, so you can skip to the next step.

Open your quiz in the editor, go to the Connect tab, then under Integrations, go to Shopify:

Now, check the option Synchronize quiz answers to customer metafields:

On the Shopify integration settings, where you enabled the Customer Metafields, on the right, you will see the Metafields Definitions Preview. This is how the Customer Metafields will look in Shopify:

You may have noticed that they look very similar to the Custom Properties, also in the Connect tab. This is because the Customer Metafields are generated directly from the Custom Properties:

You can customize the Customer Metafields by customizing the Custom Properties. You can review our guide on the Custom Properties here.

Each field type maps to a specific Shopify metafield data type as follows:

The Image Analyzer question type does not currently support Custom Properties or Customer Metafields.

A conflict occurs whenever two quiz fields are mapped to the same Custom Property name but expect different Shopify metafield data types.

Conflicts arise when two fields share the same Custom Property name but map to different data types. Some examples of combinations that will cause a conflict:

This is checked across all your quizzes. If you have Metafields enabled for multiple quizzes, a conflict can occur between fields in different quizzes, too.

If you try to save your quiz with a conflict inside the same quiz, you will get an error like this:

If you try to save your quiz with a conflict with another quiz, you will get an error like this. In this case, you will also see a link to the other quiz where the conflict originates:

If two fields share the same Custom Property name and map to the same Shopify metafield data type, there is no conflict. In this case, the most recent response always overwrites the previous value. For example:

In general, the latest response value is always the one that gets saved.

Both single-select and multiple-choice questions map to list.single_line_text_field. This is intentional: since a Shopify metafield definition's data type cannot be changed after creation, mapping to a list in both cases means you can toggle the Allow multiple answers to be selected option on a question later without needing to change the Custom Property name or losing existing data on customer profiles.

For the Customer Metafields to be added to the Shopify customer profiles, some conditions need to be met:

The quiz needs to be submitted on the live, published version of the quiz. Submissions made in the preview mode will not sync the Customer Metafields.

The customer needs to be logged in to your store when taking the quiz or make a purchase on your store on the same browser session that they took the quiz. If the customer is not logged in and makes an order on a different browser session, in incognito mode, or on another device, their Customer Metafields will not be synced.

To check your Customer Metafields, go to Customers on Shopify and access the profile of a customer who has completed the quiz. If the Customer Metafields synced successfully according to the conditions explained previously, you will find the Metafields section in the profile, with your Customer Metafields:

There are two ways to stop syncing a Custom Property to customer metafields:

This also stops the Custom Property from syncing to any of your other integrations.

Octane AI receives a notification when this happens and automatically disables the sync for that property. Note that this cannot currently be self-reversed. To re-enable it, you will need to contact our support team or rename the Custom Property so it gets recreated under a new key.