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
      • Quickstart
      • 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
  • How it works
  • Prerequisites

Was this helpful?

Export as PDF
  1. Advanced usages
  2. Audience segmentation

Edge segments

PreviousCurated Audiences (SDA)NextCohort-based Lookalike

Last updated 16 days ago

Was this helpful?

You can compute segments browser-side using our Edge technology and share them to Google Ad Manager.

The Google Ad Manager then delegates the computing to the . The tag:

  1. Collects and stores navigation data in the local storage. When an event is , it will not only be pushed to but also to the local storage.

  2. Computes segments' enter and leave events, browser-side, and sends them to the server through a pixel. This replaces the normal process of computing the segment regularly server-side.

  3. Triggers integration with Google Ad Manager when a user enters or leaves a segment, and on-page load.

This gives you the ability to react instantly to user navigation and trigger campaigns as the user is browsing your site.

Edge segments still exist server-side.

  • Segment statistics are calculated periodically by running a query counting the users marked as in the segment.

  • User points are added or removed from a segment only when the JS Tag triggers the action through the pixel. Only users who navigated your site with the Edge feature activated will be in the segment.

Edge segments are only integrated with Google Ad Manager at the moment. App Nexus integration is possible.

How it works

You declare a new Edge segment by going to > Audience > Segments > New Segment and selecting the Edge type. This segment will be associated with a query.

From this point, the mediarithmics, JS Tag will handle additional operations during .

It will leverage the local storage of the user's browser. Three fields are created:

  • {customname}_mics_up contains a browser-side user point with the timeline of events the user is triggering.

  • mics_sgmts contains the IDs of the segments the user is in. It allows targeting with Google Ad Manager.

  • _mediarithmics contains the user's latest visit date.

The mediarithmics JS Tag will also add two important files:

  • segment.js grabs the queries corresponding to the different Edge segments set up in the platform

  • evaluator.min.js evaluates the local storage against segment queries to decide if a user enters or leaves a segment

When the tag pushes an event, the evaluator checks if the user should enter or leave an Edge segment. It then sends a pixel to the server and triggers integration to Google Ad Manager accordingly.

Prerequisites

  1. The feature should be activated on channels by your Account manager. They will enable analytics to ensure a cookie is deposited, and configure a key that will be used by Google Ad Manager for your channel.

Fields marked with the @EdgeAvailability directive should have the same value in the browser and in the server to avoid consistency issues between Edge segments and any server-side computation.

should be set up on your site, and events should be triggered.

Your should be defined by leveraging to make fields available in queries when building Edge segments.

As best practice, you should not have any transformation during the (for example, through ) for those fields. Note that such transformations will not be made on the browser side and you will finally have different values in the browser and in the server.

Don't hesitate to validate your schema with our team

👍
Real-time web apps tracking
mediarithmics JS tag
the mediarithmics navigator
web tracking
schema
activity analyzers
processing pipeline
the activity processing pipeline,
pushed by the tag
the @EdgeAvailability directive