Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

A field mismatch issue is where the value we are trying to send to your MA tool is not being accepted, for example, our Yearly Revenue field is trying to send a range ($50M - $100M) to a drop-down select field in your MA tool that does not contain the value.

...

  • Confirm your MA tool fields Revenue / Employee / Countries / State / Industries contain our normalized values: Normalization for Revenue / Employee / Industries / Countries / States

  • Confirm your MA Tool UTM fields contain the values that are being sent, for example, if your MA UTM Campaign field is a drop-down select field it should contain the value that we are trying to send either Dynamically or Custom. – we recommend if possible for the field type to just be single-line text which will allow any value to be entered.

  • Double-check case sensitivity for example If your MA tool field is a dropdown select field and contains the value “metadata” but our platform is trying to send the value “Metadata” it will fail due to the case sensitivity and they should match exactly both the field label & system value.

  • If the error still occurs please reach out to support@metadata.io

...