Send your first-party data to a destination
Choose the kind of feed, create it on a segment, follow it to Live, then edit, duplicate, resend, or stop it.
Your goal
Push the users of one of your segments to a partner platform, and keep that stream under control afterwards.
A feed synchronises an audience segment from mediarithmics to an external partner, by sending the identifiers of the users belonging to that segment. It is the concrete delivery instance at the bottom of the activation hierarchy, built on a preset, and it adds only what is specific to one data stream: the source audience, optional filters, and the schedule. A feed is either server-side or client-side, and both kinds can be used on any segment type.
Expected outcome
A feed attached to the segment, visible on the segment page and in the Detailed list tab, moving through its statuses to Live and then sending only differences.
Prerequisites
An Authenticated destination for the partner.
A preset on that destination, carrying the identifiers you want to send.
A segment that is populated - persisted and computed, if it is a Query segment.
Choose server-side or client-side
A feed is one of these kinds, depending on the route the identifiers take to the partner. When you select a preset, the Connector type filter shows one kind or the other.
Route
The users' identifiers are sent directly from mediarithmics' servers to your partner's servers.
Segments are shared with your partners from the user's browser, when users visit the sites where you installed the mediarithmics JavaScript tag.
Reaching full volume
Initial loading synchronises all users from the segment, then only differences are sent.
A user can only be synchronised while visiting your sites, so the volume ramps up.
Users leaving the segment
Delete operations are sent.
No exit signal.
Statuses
From Initial to Live, then Closed.
Active or Paused.
The statuses are detailed in Follow the feed to Live.
How a client-side feed works
The last two steps are refreshed:
Every time a new identifier is captured on the site, for example at login.
Every time a new tab or window is opened on the site.
Every 24 hours within an open tab that has not been closed, based on the
lastFeedRefreshDatevalue held in local storage.
Client-side caveats
Client-side mechanisms
For some partners a partner pixel or JavaScript API is integrated directly; for others the platform relies on the browser's local storage.
Pixel
A piece of code placed on your pages. The call to the ad server transmits the audience IDs the user belongs to, which lets you track ad conversions and build remarketing audiences from visitors to your site or to specific pages.
Browser local storage
The segments a user belongs to are written to the browser's local storage, where any supported partner can read them.
The connectors using each mechanism, and the partners that read from local storage, are listed in the Connectors section.
Create the feed
Feeds are created from the segment page, with the New feed button.
Select a preset
The list shows only presets linked to an Authenticated destination. Narrow it with:
Connector type - server-side or client-side.
Search bar - by connector name or preset name.
Identifiers - by the identifier types configured on the preset.
Each preset card shows the connector name, the parent destination's authentication status, the configured identifiers, and how many feeds already use that preset.
Select the preset matching your activation goal. The feed inherits all of its configuration.
The feed appears in the Detailed list tab and on the segment page.
What the feed inherits, and what it does not
Inherited from the preset
Partner account identifiers.
Audience type, TTL, and other partner-side options.
Field mappings.
Identifiers.
Visible on the feed, read-only there. To change any of them, update the preset - changes propagate to every feed using it.
Follow the feed to Live
Once created, a feed moves through statuses that depend on its kind.
Initial
The feed has been added on a segment but has not been activated. No information has been sent to the activation platform.
Creation
The segment is being created on the activation platform.
Connection
Connecting to the segment on the destination, and checking the identifier can be sent to the partner.
Starting
Sending upserts as users enter the segment.
Initial loading
All users from the segment are being synchronised with the activation platform.
Live
Initial loading has finished. Differential updates keep the segment synchronised - see below.
Closed
The feed is closed. No more updates will be synchronised.
Active
Data is being sent to your partner's platform, through the user's browser.
Paused
No data is being sent.
What a Live feed sends
Once Live, the feed no longer resends the whole segment. It sends differences:
Upsert operations for users entering the segment, and for users already in the segment who gain additional identifiers used in the sync.
Delete operations for users leaving the segment, users deleted from the datamart, and users who updated their user choice in a way that makes it incompatible with being in the segment - where you chose to use a processing activity when defining that segment. See Enforce compliance on your audience.
Reading the feed card on a segment
The segment page lists the feeds hooked to it. Each card shows:
The feed name.
The feed type - the connector it uses.
The feed status - for example "Sending updates when users enter or leave".
The number of identifiers, or users, pushed and removed through the feed in the last 24 hours, where applicable.
Manage a running feed
A feed is reached either from Navigator > Feeds, Detailed list tab, or from the segment page by opening the feed menu and selecting Configuration or Stats.
Edit
Change the feed name and the properties specific to this feed. A client-side feed can only be edited while it is not active - stop it first if it is live or syncing.
Duplicate
Adds another feed on the segment reusing an existing feed's configuration. The configuration is copied and remains editable.
Resend all users
Available when the feed is LIVE. Reboots the connection with the destination partner, then resends every user in the segment.
Delete
The feed must be stopped first. Deletion is permanent - if you may need the stream again, archive rather than delete. You can also delete the destination audience, when the connector supports it. See Delete a feed.
A feed session is initiated whenever a feed is activated. A new session is also created if a feed is paused and then reactivated. Sessions are not visible in the interface - they matter because they are the unit the initial loading belongs to: reactivating a paused feed starts a new session, not a continuation of the old one.
Delete a feed
Deleting a feed stops its synchronisation. By default, the destination audience - the audience the feed created or manages on the destination platform - stays on that platform: it is no longer updated, but it is not removed.
When the feed's connector supports it, the confirmation dialog, What do you want to delete?, offers these choices:
Delete feed only
The mediarithmics feed only. The audience remains untouched on the destination platform, but is no longer updated.
Delete feed and destination audience
The mediarithmics feed, and the audience on the destination platform.
When the connector does not support it, only the feed can be deleted. Deleting the destination audience requires the same rights as deleting the feed.
The platform deletes the destination audience first, then the feed:
The destination audience cannot be deleted
The feed is not deleted, and an error message is displayed.
The destination audience no longer exists on the destination platform
Treated as deleted: the feed is deleted.
The destination audience is deleted, but the feed deletion fails
The feed remains, and an error message is displayed. The feed no longer synchronises, so the destination audience is not recreated.
Verification
The feed reaches Live after initial loading. The server-side statuses are listed in Follow the feed to Live.
Upserts appear in the feed's stats, and the percentage of users for which compatible identifiers could be sent is acceptable. See Track a feed.
The audience is visible at the partner. For a client-side feed, expect a ramp-up rather than an immediate figure.
Troubleshooting
You cannot create the feed - no preset in the list
The destination is not Authenticated, or no preset exists on it. See Keep the connection healthy.
The feed is created but sends nothing
The segment is not persisted or not yet computed.
Far fewer users at the partner than in the segment
Identifier coverage. See The numbers that matter.
You want to change the identifiers sent
Not editable on the feed. Update the preset.
Users you removed from the segment are still targeted at the partner
Expected on a client-side feed - there is no exit signal. Use an exclusion segment in the partner's campaign configuration.
Related pages
Last updated
Was this helpful?