Integrations — channels, delivery & stack Run SMOC on landing pages, iframe embeds, and custom domains; send conversions to Meta, Google Ads, and LinkedIn; connect LinkedIn message flows via the v2 API; and sync outcomes through Zapier, REST API, or MCP.

Connect SMOC to channels, surfaces & your stack

Deliver flows on landing pages, website embeds, and LinkedIn; send conversions to Meta, Google Ads, and LinkedIn ads — then route qualified outcomes into the tools your team already uses.

Integrations in one sentence

SMOC connects in two directions: where flows run for prospects, and how outcomes sync back to your stack.

  • Delivery — SMOC landing pages, iframe embeds on your site, and custom domains for campaign URLs.
  • Paid ads — Meta Pixel, Google Ads (including Performance Max), and LinkedIn Insight Tag in Studio Head Tags, with conversion callbacks from conversation steps.
  • LinkedIn & messaging — proactive message flows with full access through the SMOC v2 API.
  • Stack sync — Zapier, REST API, and MCP for CRMs, data pipelines, and AI clients.

Step-by-step guides live at /eguides; common setup questions at /faq. For pricing, see /pricing.

Delivery

Landing pages, embeds & domains

Choose how prospects reach your flows — hosted SMOC pages, iframe embeds on your site, or your own custom domain.

Read the iframe & tracking guide → · Landing pages FAQ · Website embed FAQ · GTM tracking FAQ · Flow URL & domain FAQ

SMOC landing pages

Publish a flow in minutes and copy a campaign-ready link from Studio. Distribute across email, SMS, social, paid ads, and QR codes into the web conversation—add UTM parameters for channel-level tracking.

iFrame embeds

Embed flows directly on your website or in publisher ad units. Copy embed code from Studio, enable Iframe Mode in Settings → Embed, and pass UTM parameters through with the header script from the iframe guide.

Custom domains

Run flows on your own domain for brand-consistent campaign URLs instead of the default go2.smoc.ai host. Your SMOC contact helps with DNS setup; plan URL migrations when changing flow or company keys.

Paid ads

Meta, Google Ads & LinkedIn conversions

Load pixels in Studio Head Tags, then fire interaction, qualified, and lead events from conversation steps so engagement ads, Performance Max, and LinkedIn conversion ads can optimize.

Read the ad conversion guide → · Head Tags FAQ · Meta engagement ads FAQ · Google Ads / Performance Max FAQ · LinkedIn conversion ads FAQ · Empty-image callback FAQ · Ad conversion FAQ · GTM tracking FAQ · Landing pages FAQ

Meta engagement ads

Put the Meta Pixel in Settings → Head Tags. Fire ViewContent when the visitor starts the conversation, then Lead when contact is captured. Engagement campaigns should optimize on ViewContent — not a raw landing-page view.

Google Ads / Performance Max

Create one Google Ads conversion action per funnel step and call it from Head Tags with gtag. Performance Max needs those actions to bid — typically Lead as primary, interaction as a secondary signal. Use the SMOC Flow URL as the final URL.

LinkedIn conversion ads

Load the Insight Tag in Head Tags and fire lintrk conversion IDs from the same callbacks. These are paid ads that send people into the web flow — not SMOC LinkedIn message-flow outreach.

Messaging

LinkedIn & message flows

Run proactive conversational outreach in LinkedIn DMs — the native message-flow runtime alongside web flows.

Read the LinkedIn connection guide → · Digital channels FAQ

LinkedIn account connection

Connect sender accounts from Console (Sales Launch or Settings → LinkedIn) via hosted LinkedIn login. Optionally enable Sales Navigator, then set daily limits and use Inbox for human-in-the-loop replies.

Proactive message flows

Deploy message-style flows inside LinkedIn direct messages — personalized by persona, industry, and signal. The same agent logic extends from ads and landing pages into the inbox.

Full v2 API access

Programmatic access to messaging workflows, contact sync, and outcome routing through the SMOC v2 API. Build custom automations or connect messaging data into your CRM and data warehouse.

No-code

Connect via Zapier

Automate handoffs to 2,000+ apps without writing code.

Read the Zapier guide → · Zapier FAQ · Zapier authentication FAQ

New Contact trigger

Fire a Zap whenever SMOC creates or updates a contact. Select New Contact as the trigger event, test against existing contacts in your account, then map the fields SMOC delivers into your destination app.

API key authentication

Generate a key under Settings → Integrations → Zapier and paste it when Zapier prompts for a token — no email or password sign-in. Keys are company-scoped; generating a new one does not revoke existing keys.

2,000+ destinations

Route SMOC outcomes into CRMs, spreadsheets, messaging tools, and the rest of your stack through Zapier actions. Access to the SMOC Zapier app is invitation-based — the eGuide has the current setup steps and invite link.

Custom

Build with the REST API

Programmatic access for custom integrations, messaging workflows, and data pipelines.

Read the REST API guide → · REST API setup FAQ · REST API functions FAQ

Integration token

Generate a key under Settings → Integrations → API in SMOC Console and send it on each request — the same token pattern used for MCP and Zapier.

Company-scoped data

Retrieve contacts and interaction data for your company using your integration key. Every request stays scoped to your tenant — you only see data that belongs to you.

Flexible integration

Build sync jobs against GET /api/company/mongocontact to list contacts and lead/customer counts. Manual CSV export from the contacts section is also available for one-off extracts.

AI-native

Connect with MCP

Let AI clients read your SMOC data directly.

Read the MCP guide → · MCP setup FAQ · MCP data access FAQ

Read-only, company-scoped

Authenticate with an API key from Settings → Integrations → MCP. Access is read-only and confined to your company's contacts, companies, assets, analytics, inbox, and conversations — never another tenant's data.

AI client support

Connect from Claude Desktop (via mcp-remote), Claude Code, Cursor, VS Code, Windsurf, or other MCP-capable editors. The eGuide covers HTTP config and the local bridge setup for Claude Desktop.

Rich data access

Search contacts, read company assets and extraction results, explore flowcharts and recommendations, pull flow KPIs, and read LinkedIn inbox threads and message-flow conversations. Clients discover the right tool via mcp_capabilities and skills_search — or you can ask in plain language.

Related Guides

Continue learning with these related guides

Track conversions for Meta, Google Ads, and LinkedIn

Track conversions for Meta, Google Ads, and LinkedIn
IntegrationsDevelopersStudio

Connecting SMOC to Other Apps Using Zapier

Connecting SMOC to Other Apps Using Zapier
Integrations

Connecting SMOC with MCP to Claude or Any other AI based client

Connecting SMOC with MCP to Claude or Any other AI based client
IntegrationsDevelopers

View All Guides →

Stay close to the shift in AI sales

Get product updates and perspective on proactive AI agents, multichannel orchestration, and conversion—without the noise.

Product of the Year Weekly signal on proactive AI sales
Join the newsletter

Sign up

Enter your email below to get started with SMOC.AI

or