Track Conversions with the Sociable Pixel

Client-side pixel: <script src="https://app.sociable.how/pixel.js" defer></script>

Use the Sociable pixel to track page views tied to conversations. When a visitor arrives from a Sociable link, the pixel stores the tracking id (sblid) in a first‑party cookie and sends a page_view event for each URL visited (including SPA navigations). Conversions are classified server‑side using templates you configure in Sociable.

Please feel free to reach out to our team at contact@sociable.how for assistance or if your case requires a custom solution.

How to use

Add the pixel to your site (ideally in <head>):

<script src="https://app.sociable.how/pixel.js" defer></script>

That’s it. Links generated by Sociable include ?sblid=... automatically. The pixel will:

Store sblid in a first‑party cookie for 48 hours
Send page_view events to https://app.sociable.how/api/pixel/track
Track client‑side route changes (SPAs)

Notes:

The pixel manages the sblid cookie automatically; no custom code needed.
Classification of conversions is template‑based and happens on the server.

Sample Flows:

Debugging (optional)

Turn on verbose logs:

<script>window.__SBL_PIXEL_DEBUG = true;</script>
<script src="https://app.sociable.how/pixel.js" defer></script>

Verify:

Cookie sblid exists after arriving from a Sociable link
Network shows POSTs to /api/pixel/track

Privacy

First‑party cookie: sblid, 48h TTL
Respect your site’s consent model as needed

The legacy server‑to‑server conversion webhook has been deprecated in favor of the pixel‑based approach.

Please do not hesitate to reach out to contact@sociable.how for support regarding this process.