Pixel
Fire the Meta pixel with the segment's technical name, so Meta can build a website Custom Audience from it.
The Meta Pixel connector sends online data to Meta technologies, including Facebook and Instagram, from the visitor's browser. Nothing is stored on mediarithmics' servers.
Type
Client-side (pixel)
Category
Identifiers sent
None
Authentication
None - the pixel is created in Meta Business Manager
Description
How it works
The mediarithmics JavaScript tag loads the Meta tag on your website with a key/value indicating that the user is in a given segment. You then create a Meta Custom Audience of type Website and use Meta's query builder on pixel events to select every user carrying that property.
Because it runs in the browser, your Meta audience only starts growing from the moment the mediarithmics–Meta pixel synchronisation is set up.
What you can do with this connector
Retarget a visitor who looked at a product on your site without buying it, on Facebook and Instagram.
Reach visitors who are not logged in, which the Custom Audiences route cannot do.
Which identifiers are sent
None. The connector triggers the Meta pixel to send a custom event; mediarithmics sends no IDs.
Meta is reached by several connectors and they behave differently - the comparison is on the Meta page.
Connector setup
Prerequisites
The mediarithmics tag installed on the site, calling
syncFeeds- the call that enables client-side feeds. See Web tracking.A Meta pixel created in Meta Business Manager, and its pixel ID - found in the Events Manager tab.
Set up the Meta - Pixel connector
Create the pixel in Meta Business Manager and note its ID.
Check the technical name of your segment.
Text characters only, no numbers. Fix it before activating, not after.
Select the Meta Pixel connector and fill in its configuration.
Name
The name displayed in the mediarithmics platform.
Pixel id
The ID of the pixel you created in Meta Business Manager.
Create the CDP-based audience in Meta.
Creating and activating the feed on a segment is covered in Send your first-party data to a destination.
Create a CDP-based audience in Meta
In Meta Business Manager:
Go to Audience › Create Audience › Custom Audience.
Choose the Website source.
Select the Events name corresponding to the pixel name, for example
MicsSegments.Set the Audience retention, for example 30 days.
Refine the URL or parameter section: select Custom data in the first dropdown, enter
technical_name, select contains, and enterTrue.Click Create audience.
Good to know
This is a client-side connector, so it carries the client-side constraints: volumes ramp up as users visit your site, a segment exit cannot be signalled to Meta, and nothing is sent when the tag is blocked or consent is refused. See Client-side caveats.
FAQ
My key/value shows in Meta but the audience stays empty. Why?
Almost always because the segment's technical name is numeric. Meta accepts the parameter but never populates the segment. Use a text-only technical name.
My audience is not growing after I created it in Meta. What should I check?
The True value in the audience definition - it is case-sensitive and must carry an uppercase T.
Can I rename the technical name after activating?
You can, but the link to platforms already activated may break, and Meta will still hold the previous name. Duplicate the segment instead.
Partner documentation
Meta documents its own platform at https://developers.facebook.com/docs/marketing-api/audiences/. Use it for anything that happens on the partner side of this connector: account setup, the fields the partner expects, and its own limits.
Last updated
Was this helpful?