Developer
User guidesDeveloper websiteHelp centerLog in
  • Welcome!
  • Organisations structure
    • Datamart
    • Users and roles
  • User points
    • User identifiers
      • Networks IDs
        • Device-based Network IDs
          • Custom Device ID integration
          • ID5
          • First ID
        • User-based Network IDs
          • Custom User ID integration
          • UTIQ martechpass
      • Accounts
      • Emails
      • Device identifiers
    • User activities and events
    • Compartments
    • User profiles
    • User segments
    • Hyper point & Quarantine
  • Data model
    • Defining your schema
    • Computed fields
      • Concepts
      • Setup
      • Development
      • Examples
  • Data ingestion
    • Real time user tracking
      • Website tracking
      • Mobile apps tracking
      • Ads exposure tracking
      • AMP tracking
      • Conversions tracking
      • Email views and clicks
      • Tracking API
      • Event rules
      • Activity analyzers
    • Bulk processing
      • Imports
        • User activities import
        • User profiles import
        • User choices import
        • Segments import
      • Deletions
        • User identifiers deletion
        • Device points deletion
        • User points deletion
      • User identifiers association
      • Integration batch
    • Activities analytics
    • Data warehouse
      • Preliminary setup
        • BigQuery
      • Create data warehouse
  • Querying your data
    • OTQL queries
    • OTQL examples
    • GraphQL queries
    • UserPoint API
    • User activities
    • Activities analytics queries
      • API Quickstart
      • Dimensions and metrics
      • Use cases
    • Funnel API
  • Alerting
    • Alert configurations
  • Data visualisation
    • Quickstart
    • Dashboards
    • Sections and cards
    • Charts
    • Datasets and data sources
      • Using a data file data source
    • Transformations
    • Filters
    • Cookbook
    • Reference
  • Advanced usages
    • Audience segmentation
      • Audience features
      • Segment builders
      • Audience segment metrics
      • Audience segment feed
        • Building new feeds
        • Monitoring a feed
        • Curated Audiences (SDA)
      • Edge segments
      • Cohort-based Lookalike
    • Contextual targeting
      • Setup
      • Activation
        • Google Ad Manager
        • Xandr (through prebid.js)
      • API documentation
    • Exporting your data
      • Query Exports
      • Datamart replication
    • Data privacy compliance
      • User choices
      • Cleaning rules
      • Exercise of user rights
      • Cookies
    • Campaigns
    • Automations
      • Email routers
      • Email renderers
      • Opt-in provider
      • Custom action plugins
      • Usage limits for automations
    • Plugins
      • Concepts
      • Creation & Deployment
      • Coding your plugin
      • Manage existing plugins
      • Layouts
      • Presets
      • Monitoring
      • Throttling
      • Batching (for external feeds)
    • Platform monitoring
      • Resources usage
        • Dimensions and metrics
      • Collection volumes
        • Dimensions and metrics
      • Events ingestion monitoring
        • Dimensions and metrics
    • Data Clean Room
      • Bunker
      • Clean room
  • Resources
    • Tutorial: Data Ingestion
      • Your first events
        • Add the mediarithmics tag
          • Getting the tag
          • Adding the tag
        • Send events using the tag
          • Adding event properties
          • Finding the UserEvent type in your schema
          • Matching your schema
          • Standard events
      • Your first bulk imports
        • API basics
          • Authentication
          • Your first API call
        • Send documents using the API
          • Requirements
          • Sending documents
    • Using our API
      • Authentication
    • Tools & libraries
      • mics CLI
      • JS Tag
      • Plugin SDK
    • Data cubes
      • Creating a report
      • Reference
Powered by GitBook
On this page
  • Pixel Touch for Email Opening
  • Click Tracking for Emails

Was this helpful?

Export as PDF
  1. Data ingestion
  2. Real time user tracking

Email views and clicks

You can track read and click actions in emails sent to your customers.

  • To track the opening of the emails, you have to include a pixel

  • To track the clicks on the links included in your emails, you have to replace each of your links with a Click Tracking URL

For each event, the datamart will identify the users reading/clicking the email by:

  • Recommended option: using the user's Email Hash, included by you in the pixel/tracking URL

  • Reading their cookies if possible:

    • It is always working when the users are clicking (e.g. Click Tracking URL)

    • It is sometimes possible when the users are opening the emails, depending on their email client (e.g. Pixel)

Activities tracked through this method will be of EMAIL $type and NO_SESSION $session_status. See User activity object for more information.

Pixel Touch for Email Opening

Calls to those URLs generate events.

https://events.mediarithmics.com/v1/touches/pixel?  
  $ev=$email_view&  
  $dat_token=<DATAMART_TOKEN>&  
  $email_hash=78b04074e616166938cf672f70f41b4d&  
  Any Custom Properties ...

or if your are using the $uids field (see Passing user identifiers in pixel-based tracking)

https://events.mediarithmics.com/v1/touches/pixel?  
  $ev=$email_view&  
  $dat_token=<DATAMART_TOKEN>&  
  $uids=jso-[{"$tpe":"EM","$eh":"78b04074e616166938cf672f70f41b4d"}]&
  Any Custom Properties ...

or if you are using a custom domain:

https://analytics.custom-domain.com/v1/touches/pixel? 
    $ev=$email_view& 
    $dat_token=<DATAMART_TOKEN>& 
    $email_hash=78b04074e616166938cf672f70f41b4d& 
    Any Custom Properties ...

It is possible to set custom properties

Field
Type
Description

$ev

String

The event name. $email_view for email opening tracking

$dat_token

String

The id of the audience datamart in the mediarithmics platform.

$cuid

String (Optional)

The user account id.

$email

String (Optional)

The user email.

$email_hash

String (Optional)

The user email hash.

$cb

String (Optional)

The cache buster parameter. It should contain a random string.

$uids

JSON as string (Optional)

any custom property name

Any Type

Any custom property

Click Tracking for Emails

Calls to those URLs generate click events

https://events.mediarithmics.com/v1/touches/click?
    $ev=$email_click&
    $dat_token=<DATAMART_TOKEN>&
    $email_hash=78b04074e616166938cf672f70f41b4d&
    Any Custom Properties &
    $redirect=<CLICK_URL>

It is also possible to set custom properties.

The $redirect parameter is used to define the destination of the url redirection. The URL put in the $redirect parameter should be URL Encoded (RFC 3986).

Field
Type
Description

$ev

String

The event name. $email_click for email opening tracking

$dat_token

String

The id of the audience datamart in the mediarithmics platform.

$redirect

String

The redirect url. This string should url encoded. (RFC 3986). Warning: this parameters must be placed at the end of the URL. Any parameters that will be placed after the $redirect parameters will not be saved.

$cuid

String (Optional)

The user account id.

$email

String (Optional)

The user email.

$email_hash

String (Optional)

The user email hash.

$cb

String (Optional)

The cache buster parameter. It should contain a random string.

$uids

JSON as string (Optional)

any custom property name

Any Type (Optional)

Any custom property.

PreviousConversions trackingNextTracking API

Last updated 1 year ago

Was this helpful?

The list of of the user.

The list of of the user.

user identifiers
user identifiers