Discussions

"Metadata is useful for storing additional, structured information on an object. For example, you could store your user's corresponding unique identifier from your system on a Hook0 Customer object. By default, metadata isn't used by Hook0—for example, it's not used when forwarding events to subscriptions —but metadata is supported by the Search API. Your users won't see metadata unless you show it to them."

If the metadata is stored on an object, then loading is required, and that would again depend on internet bandwidth and many factors.Can we use another way to handle this like

Example: If you need to use an IP address or a unique identifier for a specific transaction, you could generate and use this metadata temporarily during the transaction and then discard it once the process is complete.

This would help with metadata generation in real-time and also remove security risks that would come from storing additional, structured information on an object.

It would be great getting a reply from and clear my understanding.

Thanks