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
  • Accessing the feed
  • Feed details overview
  • Stats: high-level overview of the feed
  • Server-side feeds
  • Client-side feed
  • Configuration: plugin properties setup
  • Troubleshooting: technical details
  • General information
  • Metrics for server-side feeds
  • Metrics for Client-Side Feeds

Was this helpful?

Export as PDF
  1. Advanced usages
  2. Audience segmentation
  3. Audience segment feed

Monitoring a feed

PreviousBuilding new feedsNextCurated Audiences (SDA)

Last updated 4 months ago

Was this helpful?

Accessing the feed

  1. Go to the Segment: Navigate to the segment where your feed is configured.

  2. Open Feed Options: Click the menu button and choose either Stats or Edit.

Feed details overview

The feed details are divided into three sections to enhance understanding:

  1. :

    • Provides a high-level summary of the feed.

    • Shows the status of the feed instance.

    • Displays the identifiers sent to the partner for addition or deletion.

  2. :

    • Lists all plugin properties configured for the current instance.

  3. :

    • Offers an in-depth view of processing steps, aiding in the investigation of anomalies.

Stats: high-level overview of the feed

The Stats tab is tailored for non-technical users to easily assess feed activity. It shows whether the feed is successfully transmitting identifiers to the destination platform.

Server-side feeds

Feed lifecycle

  1. Creation:

    • Waiting for Activation: The feed card is created on the segment but remains inactive.

    • Feed Activated: The feed creates the segment on the destination platform (triggers the onExternalSegmentCreation function).

  2. Connection:

    • The feed tests the connection with the destination platform (triggers the onExternalSegmentConnection function).

  3. Starting:

    • The feed begins transmitting identifiers to the destination platform.

  4. Initial Loading:

    • Processes all users in the segment and sends their identifiers to the destination.

  5. Live:

    • Continues to send new identifiers and requests deletion of those no longer present in the segment.

Sending metrics

  • Successful Identifier Transactions: number of upserts or deletions of identifiers successfully sent during the selected period.

  • Identifier Coverage: percentage of user points without any identifiers sent to the destination platform.

  • Daily Graph: visual representation of upserts or deletions sent daily.

Client-side feed

Client-side feeds have simpler functionality but use a similar interface.

Feed lifecycle

  • PAUSED: the feed card is created but not activated.

  • ACTIVE: the feed is activated on the segment and the feed is downloaded by the browser.

Sending metrics

  • Daily Downloads: number of times the feed was downloaded by the browser during the selected period.

Configuration: plugin properties setup

The Configuration tab displays the plugin properties for the feed instance:

  • Plugin properties layout is determined during the creation of the plugin version.

  • These values can only be modified when the feed is not activated. Once activated, the configuration becomes read-only.

Troubleshooting: technical details

The Troubleshooting tab is designed for technical users, providing detailed insights into:

  • Successful and failed operations (e.g., upserts and deletions).

  • Errors and processing steps for investigating anomalies.

General information

  • Server-Side and Client-Side feeds:

    • Resource details, plugin information, and plugin version information.

  • Server-Side Feeds only:

    • Instance details and initial loading logs.

Metrics for server-side feeds

Standard Metrics:

  1. API Calls to the Audience Feed Plugin:

    • Displays response status for /user_segment_update calls.

  2. Identifiers Sent to the Destination Platform:

    • Shows processed identifiers and their statuses for non-batching cases.

Actions and Statuses:

  • Push: Adding a user point to the segment or an identifier to a user point.

  • Remove: Removing a user point from the segment or an identifier from a user point.

  • Statuses:

    • PROCESSED: Successful with no destination platform response (e.g., batch/file delivery).

    • SUCCEEDED: Successful with a positive response from the destination platform.

    • FAILED: Error occurred within the plugin or at the destination platform.

    • NO_ELIGIBLE_IDENTIFIERS: No eligible identifiers to send.

Batching Metrics:

  • API Calls to the Audience Feed Plugin (/batch_update route):

    • Number and status of batches created.

  • Records Sent to the Destination Platform:

    • Rows sent per batch (may contain multiple identifiers).

File Delivery Metrics:

  • Files Sent by File Delivery Service:

    • Number of files sent and response statuses.

  • Records Sent to the Destination Platform:

    • Rows sent per file (may represent multiple identifiers).

Metrics for Client-Side Feeds

  • Displays a daily graph of browser downloads, as shown in the Stats tab.

Stats
Configuration
Troubleshooting