Skip to main content

List of Product IDs custom fields

Chris Axe
  • Updated
Availability: List of product IDs fields are part of a controlled rollout and need to be enabled per account. Contact your Customer Success Representative to find out if this is available to you.

The custom field type List of product IDs lets you store a list of product identifiers against a contact, for example their wishlist.

You can then use this field to populate product blocks using custom fields in an email or any other use case that may have.

To create a Product ID custom field, navigate to your Settings > Custom fields and select List of Product IDs:

Note: You can update this field via API or CSV upload. You can't edit it in the single customer view, and you can't use it to segment contacts. This field type is available for contacts only, not orders.

How identifiers resolve at send time

Each value in the list can be a product ID or a SKU. When the email is sent, Ometria tries each identifier in turn:

  1. Match by product ID first.
  2. If there's no match, try the same value as a SKU. If exactly one product matches, that product is used.
  3. If the identifier still doesn't match, or matches more than one product, that entry is skipped.

Identifiers that don't resolve to a product available in the recipient's home store are also skipped. The product block fills any empty slots from your fallback list. See Product selector block.

Up to 12 products are shown per block.

Sending via the API

Send the value as a string containing the IDs in square brackets, separated by commas:

[
    {
        "@type": "contact",
        "id": "list_of_product_ids_example",
        "timestamp": "2026-05-13T10:00:00+00",
        "email": "david@example.com",
        "@merge": true,
        "properties": {
            "wishlist": "[10190951940385,10190951940386,10190951940387]"
        }
    }
]

The custom field ID (here, wishlist) is the ID you set when creating the custom field in Ometria.

Sending via CSV

You can also import values via CSV upload. The value uses the same square-bracket format as the API.

Be aware: Because the field value contains commas, your CSV file must use a non-comma delimiter (for example, a semicolon or pipe). A comma-delimited CSV won't parse correctly.
 

Limitations

You cannot use these custom fields in filters for Segmentation, nor do they show as columns within the segment explorer table.

See also

Related articles

Comments

0 comments

Please sign in to leave a comment.