Support

Adding a Meta pixel and the Conversions API to your Link

Once you've got a Pixel ID from Meta's Events Manager, adding it to your SubmitHub Link takes about a minute.

Adding your pixel

1. Open your Link in the Links dashboard and go to the Pixel tab.
2. Paste your Pixel ID into the field provided.
3. Save.

That's the basic setup. From here on, every page load and click on your Link is reported to Meta.

What events we fire

We send two events to Meta by default:

• PageView: fired when someone loads your Link.
• ViewContent: fired when someone clicks one of your buttons (the cover image, a destination link, or the main call-to-action).

If you're running a conversion campaign, use ViewContent as the event you're optimizing for.

Why customize event names?

This is an advanced option most users should ignore. The defaults work for everyone, including artists running multiple ads or campaigns at once (one ad, ten ads, same setup, same events). Custom event names are there for the rare power user who knows exactly why they want a different event name (e.g., they're stitching SubmitHub Link data into a broader pixel setup with their own naming convention). If you're not sure why you'd use it, you don't need it.

Conversions API (recommended)

The Conversions API lets us fire pixel events from our servers instead of only relying on the visitor's browser. More reliable tracking, less affected by ad blockers or browser tracking protections, and better attribution in Meta.

1. In Events Manager, click on the pixel you're using for your SubmitHub Link.
2. Go to the Settings tab and scroll down to the Conversions API section.
3. Click Generate access token and copy the token.
4. Back in your Link settings (Pixel tab), paste the token into the Conversions API field below your Pixel ID.

With CAPI active, events get fired two ways so they're more likely to reach Meta even when browser tracking is blocked.