Metorik Docs
3rd Party Compatibility

WooCommerce: Using Advanced Custom Fields (ACF) with Metorik

Yes, Metorik supports fields created with the Advanced Custom Fields (ACF) plugin for WooCommerce. ACF fields are stored as WooCommerce custom meta fields, and Metorik processes them the same way it handles any custom field data.

What you can do with ACF fields

Once your ACF fields are attached to orders, customers, products, or subscriptions, you can use them across Metorik:

  • Segment — Filter orders, customers, products, or subscriptions by ACF field values. Access these filters at the bottom of the filter select on any data page.

  • Export — Include ACF fields in CSV exports. Click Export from any table, enable Customize export columns, and add the fields you need.

  • Report — Break down reports by ACF field values to see distributions across your data.

  • View on single pages — ACF fields appear in the Custom Fields section on individual order, customer, product, and subscription pages.

  • Use in Engage — Reference ACF fields as variables in Metorik Engage email automations.

For detailed instructions on segmentation, exports, and reporting with custom fields, see the Custom Fields article.

Why some ACF fields don't appear immediately

Metorik refreshes its list of available custom fields every few hours. If you've recently created an ACF field and it's not showing in segment or export selects, it may appear after the next refresh. You can also contact Metorik support to request an immediate refresh.

Favorite fields for quicker access

By default, Metorik shows the top 150 custom fields in segment and export selects. If an ACF field isn't surfacing, you can add it as a favorite:

  1. Go to Settings → Stores → Custom Fields.

  2. Add the ACF field key to the favorites list.

Favorited fields appear at the top of custom field selects and get priority display on single-item pages.

ACF fields added through code

If you're programmatically adding or updating ACF field values (for example, via a custom plugin or external script), you must update the object's last modified date so Metorik recognizes the change. Without this, Metorik may not re-index the field.

For more details on this behavior, see the related documentation on externally-updated data.

Working with ACF date fields

If you're using ACF date fields for segmentation or filtering, the stored values must use the YYYY-MM-DD format (for example, 2024-03-15). Optionally, you can include time as HH:MM:SS. Date values should be stored in UTC.

If the field name contains the word "date" (for example, delivery_date), Metorik Engage will automatically format it as a human-readable date in emails.

Limitations

  • Subscription fields — You can view ACF fields on subscription pages, but you cannot edit or add new subscription custom fields from within Metorik due to WooCommerce Subscriptions API limitations.

  • Hidden fields — Custom field keys starting with an underscore (_) are considered protected and cannot be edited from Metorik.

  • Field volume — If a single order, customer, product, or subscription has more than 1,000 custom fields, Metorik will not store the custom fields for that record. This is rare, but if you encounter it, contact support to discuss increasing the limit.

Need help?

If an ACF field isn't appearing as expected or you're unsure how to set it up, contact Metorik support. The team can refresh your custom field list or help troubleshoot sync behavior.

Was this helpful?