Every SMLLR Integration Explained: Pixels, Audience Sync, API & Automation

SMLLR's integrations fall into four groups. Advertising & Analytics Pixels fire Meta, Google, LinkedIn, and Microsoft's own tracking events on every QR scan. Audience & Lead Sync pushes consented Lead Hub contacts into a Meta Custom Audience or sends branded email campaigns from your own domain. Developer access is a read-only REST API and an MCP server for AI agents like Claude. Automation is Webhooks, Slack, and Zapier — reacting to a scan or QR event the instant it happens instead of checking a dashboard. Pixels, Audience Sync, and Automation are all available on the Pro plan (₹4,999/month) and above; Developer access requires Premium (₹14,999/month) specifically. None of it requires installing a third-party app or going through an OAuth approval screen — every integration is a field, an ID, or a toggle inside SMLLR's own Settings.

Five platforms, one redirect page: Meta Pixel, Google Ads Conversion ID, GA4 Measurement ID, LinkedIn Insight Tag, and Microsoft Ads UET Tag. Enter each ID once as an account-wide default in Settings → Tracking Pixels, or override any subset per individual QR code, and SMLLR's redirect page fires the matching platform event automatically on every scan — no lead-capture form, no consent gate, just the same page-view-equivalent signal a website visit would send. This is the feature to reach for when the goal is retargeting audiences and conversion measurement inside ad platforms you already run campaigns from.

This group is narrower and more deliberate than pixels — it moves actual Lead Hub contacts, and only the ones who consented, into platforms you control. Meta Custom Audiences (/features/meta-sync) syncs consented contacts into a Custom Audience inside your own Meta Ads account with a manual 'Sync Now' action, so you can build a Lookalike audience from people who actually scanned and opted in — see what Meta Sync is for the full mechanics of how that differs from the passive Meta Pixel above. Your Own Sending Domain (/features/email-marketing) lets you verify your own domain and send branded campaigns to Lead Hub contacts with no third-party branding in the From address — see the complete Email Marketing guide for setup and Email Marketing Pricing for the cost breakdown. Both draw from the same shared credit wallet — one balance, spent on emails sent or Meta Sync contacts touched — covered in full in SMLLR Credit Wallet Explained.

The SMLLR REST API (/features/api-access) is a read-only reporting API — seven GET endpoints covering account summaries, QR codes, campaigns, and clients — for pulling scan analytics into your own dashboard, BI tool, or internal systems. The MCP Server wraps that same API as an MCP (Model Context Protocol) tool set, so Claude or any other MCP-compatible AI agent can query your SMLLR analytics directly in conversation, using the same API key. Both require the Premium plan (₹14,999/month) specifically — this is the one group on this page that Pro doesn't unlock. Neither one ever returns Lead Hub contact data, and neither one can create or edit a QR code — creation and editing stay dashboard-only. See SMLLR REST API & MCP Server Explained for the full endpoint list and setup.

Webhooks (/features/webhooks) register a URL and SMLLR POSTs a signed JSON payload to it the moment a QR is created or updated, a scan happens, or a redirect rule fires — six event types in total, real-time push instead of scheduled polling. Slack (/support/webhooks/slack-integration) posts the same events as pre-formatted messages to a Slack channel using a pasted Incoming Webhook URL — no app install, no OAuth. Zapier (/support/webhooks/using-zapier) needs nothing SMLLR-specific at all — point Zapier's own 'Webhooks by Zapier → Catch Hook' trigger at a generic SMLLR endpoint and you're wired into 6,000+ downstream apps. All three are bundled into the Pro plan at no extra charge — see Webhooks & Slack Pricing for exactly what's included where.

Everything in this table is a plan-level flag, not a per-integration add-on charge — once an account is on Pro or Premium, every integration in that row is available with no separate line item.

Very few accounts use exactly one integration in isolation — the four groups are designed to be combined, and a typical Pro or Premium setup layers several at once. A retail brand might run Meta Pixel and Google Ads on every QR code for baseline retargeting, Meta Sync as a separate, deliberate weekly action for its consented Lead Hub list, and a Slack endpoint subscribed to qr.scan_limit_reached so the ops team hears about a promo running out without checking a dashboard. None of these compete with each other for setup time or configuration — pixels fire passively on the redirect page, Meta Sync runs on its own manual schedule, and Webhooks/Slack push independently whenever their event happens. The only shared resource across any of them is the credit wallet, and only two integrations — Email Marketing and Meta Sync — draw from it at all; pixels, webhooks, Slack, Zapier, and the REST API/MCP server don't touch credits regardless of volume.

It's worth being upfront about the prerequisite on each side, since none of these integrations create an account for you on the other platform:

A few places these integrations show up in real workflows rather than in the abstract: a restaurant using webhooks for kitchen alerts, a retailer wiring restock alerts to a scan-limit webhook, an agency posting client notifications straight to Slack, and a head-to-head look at how SMLLR's webhook and Slack setup compares to Scanova and QR Tiger.

Pro (₹4,999/month) is the plan where SMLLR stops being just a QR/link platform and starts being an integration hub: all five ad pixels, Meta Custom Audiences, your own sending domain, and Webhooks/Slack/Zapier are all included, no per-integration fee. Premium (₹14,999/month) adds the REST API and MCP server on top, plus a larger monthly credit allowance (300 vs 100) for the two integrations — Email Marketing and Meta Sync — that spend from the shared wallet. There's no tier between Pro and Premium that unlocks only some of the developer group; API access is Premium or nothing.