Events and dataLayer fields
Reference for web developers. Which events the configurator pushes to the dataLayer through the tracking script, and which fields each event carries.
The configurator sends its events with postMessage to the page it sits in. The tracking script (mp-tracking.js) pushes them to window.dataLayer and also dispatches a meetpiloot event on document, with the original message in detail.
Events
| Event | When |
|---|---|
meetpiloot_configurator_started | The visitor opens the configurator. |
meetpiloot_product_selected | The visitor chooses a product and, where relevant, a type (conservatory, carport and so on). |
meetpiloot_step_completed | The visitor completes a step, with the step number and name. |
meetpiloot_option_selected | The visitor chooses an option in a step. |
meetpiloot_lead_submitted | The visitor sends the enquiry. This is the conversion, with a value and transaction ID. |
Fields
Each event contains the fields below, as far as they are known for that event. Use them in GTM as dataLayer variables.
| Field | Type | Example |
|---|---|---|
mp_product_type | text | veranda, lamellen |
mp_veranda_subtype | text | tuinkamer, serre, carport |
mp_step | number | 3 |
mp_step_name | text | color, placement |
mp_total_steps | number | 12 |
mp_selected_option | text | Anthracite |
mp_session_id | text | uuid |
mp_lead_id | text | uuid, only with lead_submitted |
mp_company_slug | text | smith-verandas |
mp_value | number | 8086, only with lead_submitted |
mp_currency | text | EUR |
mp_transaction_id | text | uuid, for deduplication across platforms |
mp_event_id | text | mp-<lead ID>-Lead, only on lead_submitted: use it as the Meta Pixel eventID. meetpiloot sends the same ID server-side, so Meta counts the lead once |
mp_em_sha256, mp_ph_sha256 | text | SHA-256 of email and phone, for enhanced conversions |
mp_gclid, mp_gbraid, mp_wbraid | text | Google Ads click IDs |
mp_msclkid | text | Microsoft Ads click ID |
mp_fbclid | text | Meta click ID |
mp_ttclid | text | TikTok click ID |
mp_utm_source to mp_utm_content | text | the five UTM parameters |
mp_timestamp | number | time in milliseconds |
Every lead arrives once as meetpiloot_lead_submitted, even when the visitor submits twice or reloads the page. Use mp_transaction_id as the transaction_id in GA4 and as the order ID in Google Ads, so a lead is never counted twice there either.
Fields without a value are empty or missing. Click IDs and UTM parameters come from the address of your own page, even if the visitor first landed on a different page of your site: the script keeps them for the whole session.
Read next
Stuck?
Email us or open a ticket from your dashboard. We reply within 1 to 2 working days.