metadata programming example

Every customer is unique, so we want to give businesses the ability to tailor their customers’ experiences on an individual product level. With our metadata queueing system, you can personalize your customers’ experiences very quickly, and at scale.


Let’s say that you want to display the name of the original buyer on your product’s authentication page. You can easily do this without having to create a new page for each customer by assiging custom metadata to the tag.

Configure your page

You must start by configuring a page to represent your product. For this example, we’ll just modify the Invisible T-Shirt page that was created in the Quickstart.

Displaying the Metadata

The metadata can be displayed by adding a custom handlebars variable to your page’s description. The metadata is stored as a key value pair (JSON object), so you can access the key on the secure page like {{ tag.metadata.yourKeyNameHere }}. For this example, we will be using the key owner.

Update your page details with the below HTML/handlebars code:

<h2>Owned By:</h2>
<p>{{ tag.metadata.owner }}</p>
Metadata queue setup

Nothing is displayed as the owner in the page editor because we have no way of knowing what information will be passed through the metadata until it is defined on the tag itself.

Queue metadata for your tags

In an ideal system, your POS would call the “create metadata queue” API endpoint for the corresponding page or URL group, and populate the queue items automatically. However, for this example we will add them manually.

You can do this by clicking on the “use queue” toggle button and clicking the “Create metadata Queue item” button. Now we can type in the key owner and give it a value. We can create multiple queue items to specify different owners. Make sure to click SAVE when you’re finished editing the values.

Metadata queue setup

Program tags with your metadata

The queue must be enabled, and you must have a queue item selected in order to program tags to queue items. Once you program a tag, the programmer will remove the item from the queue and select the next available queue item for programming. It will continue to select the available queue items until all have been programmed.

If a tag is deprogrammed, the queue item will be placed back into the queue


Now you should be able to read the tag and see their owners.

Verifying metadata in the programmer

You can also read the tag in the programmer to confirm that the metadata was assigned correctly

Read nfc tag metadata

API Disclaimer

Whenever you verify a tag using the Verify Authenticity API endpoint, it will return a metadata attribute with the data you specified. Please note that our rules state that storing of personal information within a tag’s metadata is not allowed. This excludes unique identifiers to records within your own servers.