Overview
Mapp Engage automatically collects basic tracking data for landing pages – including:
Page impressions
Click interactions
Device information
Conversions (if conversion tracking is enabled)
These metrics are not shown directly in the UI, but can be exported as raw tracking data. For details on how conversions are tracked, see: Create a Tracking Pixel.
To retrieve the full tracking export:
Go to Data Management > Exports
Select the export type Tracking Export
Follow the steps outlined here: Create an Export for Tracking Data
Note
These exports provide event-level records in CSV format. They are not intended for direct analysis inside Engage and typically require external tools to process.
Why Use an External Tracking Tool?
For detailed insights (e.g. conversion funnels, behavioral patterns, cross-channel attribution), we recommend integrating a dedicated analytics platform.
Our preferred solution is Mapp Intelligence, which enables:
Seamless tracking across emails, websites, and apps
Consistent user identification across systems (via hashed email or contact ID)
Advanced segmentation and campaign analysis
GDPR-compliant handling of personal data – all within the Mapp Cloud
Other analytics platforms, such as Google Analytics, Adobe Analytics, or Matomo, can also be integrated. However, using third-party tools involves sharing data externally, while Mapp Intelligence keeps data in your own environment, giving you full control over your first-party data.
How to Integrate an External Tracking Pixel
Step 1: Retrieve the Tracking Code
Get the tracking pixel or JavaScript snippet from your analytics provider.
If you’re using Mapp Intelligence, see the Smart Pixel documentation for guidance.
Step 2: Embed the Pixel in Your Landing Page
Go to Content > Landing Pages
Select your landing page and go to Step 2 – Build & Design Landing Page
Add a Custom HTML block
Paste the full tracking code
The pixel can be placed in the header, footer, or inline – depending on your tracking logic.
Optional: Add User Matching or Variables
If your analytics tool supports user identification, you can pass contact-specific values using Engage variables.
Example:
<script>
var contactId = "%%user_id%%";
</script>This is just one example — you can also use other attributes, such as a hashed email or a segment name.
When using third-party platforms, this means sharing data with external vendors. By contrast, Mapp Intelligence enables user matching within the Mapp Cloud, reducing privacy risk and ensuring first-party data control.
Personal identifiers should be encrypted or hashed before transmission. Mapp Intelligence can automatically hash email addresses if needed.
More info: