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
  • Tracking User Conversions by using Pixels
  • Tracking User Conversions by using Datamart Queries

Was this helpful?

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

Conversions tracking

To measure and optimize the performance (i.e., cost per action) of your marketing campaigns, you need to track user conversions driven by your Marketing Campaign.

On the mediarithmics platform, you create a Goal to define a trigger when a user should convert.

There are two ways of configuring a Goal:

  1. Creating a Goal and using the associated Pixel. Each user that sees the Pixel in a page will convert for this goal. This Pixel should be present on the confirmation page or dynamically loaded when the user converts (by using a Tag Manager or by including the 'pixel load' in the website logic)

  2. Writing a rule that will be run on the Datamart data. It will generate a user conversion each time a user matches the rule.

From experience option #1 is the simplest solution to configure and should be used for each 'non-recurrent' User Conversion tracking.

The option #2 offers more flexibility but with the cost of a longer & more complex configuration. It should be used either when the:

  • datamart tracking JS TAGs / Pixels are already present on the website, including the page where the conversion happens

  • Goal to track will be used repeatedly

  • Goal definition requires a complex rule that can't be achieved by displaying a JS TAG / Pixel

Tracking User Conversions by using Pixels

When creating a goal in the navigator (Campaigns tab > Goals sub-tab):

  1. Define the name of the goal.

  2. Select Trigger via Pixel.

  3. Copy/paste the generated HTML code to your technical team so that they can integrate it.

  4. Don't forget to associate the correct attribution model for the attribution of the conversion to your Marketing Campaigns.

  5. Save the goal.

Tracking User Conversions by using Datamart Queries

When creating a goal in the navigator (Campaigns tab > Goals sub-tab) :

  1. Define the name of the goal.

  2. Select Trigger via Query.

  3. Define the query that should be used to tell if a User has converted or not. Please read the documentation about Queries here

  4. Don't forget to associate the correct attribution model for the attribution of the conversion to your Marketing Campaigns

  5. Save the goal.

If you have issues when defining the proper Query to define your Goals, please try Option #1 or reach out to your Account Manager.

PreviousAMP trackingNextEmail views and clicks

Last updated 1 year ago

Was this helpful?