Monitoring a feed

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. Stats:

    • 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. Configuration:

    • Lists all plugin properties configured for the current instance.

  3. Troubleshooting:

    • 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.

Last updated

Was this helpful?