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
  • Server-side feeds
  • Client-side feeds
  • Key concepts

Was this helpful?

Export as PDF
  1. Advanced usages
  2. Audience segmentation

Audience segment feed

PreviousAudience segment metricsNextBuilding new feeds

Last updated 1 year ago

Was this helpful?

An audience feed is a acting like a connector that allows mediarithmics customers to push their segments to a third-party platform.

It is generic: once a connector to a partner has been created, every customer can use it. Each audience feed has a specific set of options to adapt to each customer.

Server-side feeds

It sends segments to partners in batches with the following process:

Initialization phase

  1. In the navigator, a user activates the feed on a specific segment with specific options.

  2. The feed tries to create the segment in the partner's architecture. On success, feed is marked as PUBLISHED.

  3. It then tries to add a user to the partner's segment. On success, feed is marked as ACTIVE.

  4. It goes into INITIAL LOADING state, sending the whole segment to the partner. On success, feed is marked as LIVE.

Live phase

Differential segment updates are sent to the partner to maintain the segment synchronized:

  • Upsert operations for users entering the segment, or if existing users in the segment gain additional identifiers used in the sync.

  • Delete operations for users leaving the segment, being deleted from the datamart or updating their user choice in a way that makes it incompatible with being in the segment (if you chose to use a processing activity when defining your segment).

For more details on how to manage consent in segments and feeds, have a look at the s section.

Client-side feeds

Client-side feeds send segments to partners by showing a pixel to your users if they are in the segment. It is either active or paused.

Key concepts

It has:

  • Plugin definition

    • group_id: com.mediarithmics.audience.externalfeed

    • artifact_id: [[partner]]-connector

  • Plugin versions with

    • Deployed code

    • An external service referencing partner’s API

    • Configuration files for things like credentials, tokens, technical configurations

A feed is an instance of an audience feed. It is specific to a segment in an organisation. It has:

  • Feed ID

  • Instance properties specified by users in the UI when adding a feed to a segment.

A feed session is initiated whenever an external feed is activated. A new session will also be created if a feed is paused and then reactivated. This session is not visible in the UI.

A feed preset is a template allowing users to easily create feed instances with pre-configured properties. You can, for example, create a Facebook feed preset containing your key for your organisation, and you won't have to remember it every time you set up a new feed.

An audience external feed is a mediarithmics specific to a partner, but shared across customers. In the UI, it is called Server-side plugin: go to a specific segment, click Add a feed, and you will see a feed type called server-side. It is marketed as connectors or server-to-server connectors.

plugin
User choice
plugin