The mParticle destination in Hightouch allows users to send events and user attributes via the mParticle Bulk Events API from the warehouse to mParticle.

Sync types

• Object (user) sync: The user sync relies on the event API, but sends user attributes without an event.
• Event sync: The event sync sends an event through the event API associated with a certain user via their user identifier. It can be optionally configured to also send user attributes. We currently support commerce_event and custom_event

Testing

All example queries will be written in PostgreSQL, but there are equivalent functions in most data warehouse SQL variants (BigQuery, Snowflake).

Single row testing

Hightouch is working on a feature to test single rows of a query result while editing the sync configuration. This is still in progress, and is planned to release by the end of July.

In the meantime, we recommend Hightouch customers use the following two strategies to generate testing SQL queries.

Limit rows

Limiting rows in their data table to avoid large amounts of erroneous data being sent to mParticle

SELECT * FROM users LIMIT 10;

Here, we are limiting the number of users to be sent. The Hightouch sync will send these users' attributes to mParticle via the events API.

Generate rows with SQL

Hightouch users can generate rows with specified columns using SQL in order to understand how to best model their data to fit Hightouch requirements.

SELECT 1 as eventId, 
			 '[email protected]' as email, 
			 101 as customerId,
			 CURRENT_TIMESTAMP as ts, 
			 'Friend' as referredBy;

In the SQL above, we are generating an event, which can be mapped to a mParticle custom event.

In this example, with reference to the mParticle JSON reference, the columns will be mapped to the fields in the mParticle request JSON, with the rest of the fields being hard coded in the Hightouch UI.

• eventId → events[0].data.source_message_id