Depending on the event type, Hightouch will allow you to map your columns to different fields in mParticle. For the most common event type custom_event , Hightouch requires setting a static event name and custom event type.
If you would like to set these dynamically based on column, you can statically set a random event name and custom event type and map columns to those fields in the next section.
Hightouch also expects a timestamp of standard ISO 8601 format. Hightouch will automatically convert this to the unix time that mParticle expects.
Hightouch allows you to pass data to the default properties and the custom event properties of an mParticle event. The properties you can map to are based on the event type that you selected. Keep in mind that for some fields, such as product_action of the commerce_event, a JSON object is expected.
Our team is relentlessly focused on your success. We're ready to jump on a call to help unblock you.
Connection issues with your data warehouse?
Confusing API responses from destination systems?
Unsupported destination objects or modes?
Help with complex SQL queries?
If you see something that's missing from our app, let us know and we'll work with you to build it!
We want to hear your suggestions for new sources, destinations, and other features that would help you activate your data.