Tracking and pixels
Give one release its own pixel, so a single campaign reports on its own instead of blending into everything else you run.
If you are running ads to a release, you want that release measured on its own. A smart link makes that easy: each link page can carry its own Meta pixel, separate from the one that covers the rest of your website.
Set it and the ad platform sees who landed on that release page and who tapped through to a streaming service, without a single other page on your site muddying the numbers.
Setting a pixel for one release
- Go to My Website then Smart Links.
- Click Edit on the link you want to measure.
- In the Release section, find Meta Pixel ID for this page.
- Paste your Pixel ID.
- Click Save.
That is the whole setup. The pixel is a public ID, which is why it is safe to sit here on the link form.
What if you leave it blank?
The page uses your site-wide pixel instead, along with the rest of your website. That is the right answer for most links. Set a per-release pixel only when you actually want that release reported separately.
Replacing a pixel later
Open the link, paste the new Pixel ID over the old one, and save.
On a link that already has one, the field shows Leave blank to keep the current one. Saving with the field empty changes nothing, so you can edit a title or reorder services without accidentally wiping your tracking setup.
The server-side token
A pixel ID on its own works, but the ad platform sees more, and sees it more reliably, when there is also a server-side connection. That needs an access token, which is a secret, so it does not live on the link form.
Set it on the Tracking page instead:
- Go to My Website then Tracking.
- Find the per-page tracking section.
- Enter the page path for the release, which is
/l/followed by your link's address. A link atsummer-nightsis/l/summer-nights. - Paste the same Pixel ID and the access token for it.
- Optionally add a test event code while you are checking the setup.
- Click Add page.
See Tracking for the full walkthrough of that screen.
Keep your token private
Anyone holding your access token can send made-up results to your pixel. TribeNest stores it and never shows it back to you. If you think it has leaked, regenerate it with your ad platform and paste the new one in.
Turning tracking off for a release
The per-page tracking list on the Tracking page is where a per-release setup is switched off or removed. Each entry has a switch to turn it off and a bin icon to delete it.
Turn it off when a campaign finishes but you might run it again. Delete it when you are done, and the page goes back to your site-wide pixel.
What gets measured
Once a pixel is running on a link page, two things reach your ad platform:
- A page view, every time a fan opens the release page.
- A tap on a streaming button, recorded as a lead, along with which service the fan chose.
Each one is sent with an identifier that stops the same tap being counted twice when both the browser and the server report it. Your campaign gets one clean number rather than an inflated one.
Fans who decline tracking
Your link page shows a cookie notice, and the pixel only fires for fans who accept marketing cookies. A fan who declines is not tracked, and there is nothing you have to configure to make that true.
The footer of every link page also carries a way for a fan to change their mind about cookies later.
Your own numbers are separate
None of this is needed to see how a link is doing. TribeNest counts views, visitors, and clicks by service on every smart link with no setup at all, and those numbers are yours regardless of whether you run ads.
See Smart link analytics.
The two work as a pair. Your own numbers tell you what happened. The pixel tells your ad platform, so it can go and find more people like the ones who tapped.
Older links
The smart links you made on the previous builder have their own tracking dialog inside their editor, and it works differently. See Legacy smart links.