Connect the tools you already use
Measure your ads, send leads to other apps and let your own agent work in your team.
What works with Shingle
Measure
- Google Analytics, with your measurement ID
- Google Tag Manager, on your own domain
- Meta Pixel
- Google Ads, counting each form sent as a conversion
- Google Search Console, through its HTML tag
Send
- Webhooks for each new form submission
- Zapier, through a catch hook
- Make, through a custom webhook
- Your own app, with signed requests
Your own agent
- A key an admin makes on the Agents page
- Claude Code, Cursor or any agent that takes an MCP server
- Reads your team, and drafts, takes notes and builds as you
- Asks for your OK before it publishes, sends or deletes
Show on a page
- YouTube and Vimeo videos
- Calendly booking calendars
- Typeform forms
Your own code
- Code in every page's head, or at the end of every page
- Chat widgets and other services' tags
- Runs only on your own domain
What visitors are asked
Tracking tools set cookies and send what visitors do to other companies, and in the EU and the UK visitors have to agree first. Turn on the cookie banner and each tool waits for the right answer. Google Analytics waits for Statistics. Google Ads and the Meta Pixel wait for Marketing. Embedded videos and forms show a Show content button until the visitor allows them.
When someone sends one of your forms, the tools that are running hear about it. Google Analytics and Tag Manager get a generate_lead event, the Meta Pixel gets a Lead event, and Google Ads counts a conversion if you added a label. They're told which form was sent, and never what anyone wrote in it. Browsers that send Do Not Track or Global Privacy Control get none of these tools, banner or not.
Your site's privacy page names the tools you added and what each is for. Tag Manager and your own code run only on your own domain, because every shinglesites.site address shares one domain with other people's sites, and code there could reach them. Shingle doesn't check code you paste, so add only what you trust.
Mostly a paste and a publish
Tracking codes
Paste the ID, or a whole snippet and Shingle keeps the ID. They run on your live site and never on previews.
Webhooks
Paste the other app's web address under Forms, then press Send test to match its fields.
Embeds
Ask for one in your site's chat with its link, for 5 credits. Changing the link later is free.
Custom code
Paste it in Widgets and choose when it runs. It needs your own domain, on the plan.
What isn't built yet
Your agent asks for each OK one at a time. Webhooks send submissions out.
One OK for one request
You answer each thing your agent asks to publish, send or delete. A standing yes isn't built yet.
Only submissions go out
Webhooks cover new form submissions. Bookings, sites and comments don't send anything yet.
No listed Zapier app
Shingle isn't listed as an app in Zapier yet, so you start from a catch hook.
No Search Console sign-in
Search Console connects by a pasted tag, so its reports stay in Google and don't show in the app.
Common questions
Can't find your answer? Read Shingle Help or email [email protected].
Google Analytics, Google Tag Manager, Meta Pixel, Google Ads and Google Search Console for measuring. Webhooks for sending form submissions to Zapier, Make or your own app. YouTube, Vimeo, Calendly and Typeform for embedding. And custom code on your own domain. Your own agent can work in your team with a key, through Shingle's MCP server.
Yes. An admin makes a key on the Agents page, and an agent such as Claude Code or Cursor connects to Shingle's MCP server with it. It reads your sites, customers, deals and more as the person who made the key, under their role, and does the team's own work at once, such as drafts, notes, deals and builds. Before it publishes, sends or deletes anything, it asks, and a person says OK in Shingle. Billing, people and keys stay a person's.
Yes, through webhooks. Start a Zap with Webhooks by Zapier and Catch Hook, or a Make scenario with a Custom webhook, paste its address into Forms and press Send test. Only new form submissions go this way, and Shingle isn't a listed app in Zapier's directory.
A Tag Manager container can run anything you put in it. Every shinglesites.site address sits on one shared domain, so code there would run beside other people's sites. On your own domain it can't reach them. Your other tracking codes still work at your Shingle address.
Not in the page itself. Only YouTube, Vimeo, Calendly and Typeform can be embedded, and Shingle links to anything else, such as an Instagram post. On your own domain, you can paste another service's code into Custom code, which runs on every page.
Mostly no. Saving tracking codes, a Search Console tag or custom code is free, and so is adding a webhook. Asking Shingle to place an embed is a change, which uses 5 credits, and changing its link afterward is free. They all work on a live site, so you'll need the plan.
Read next
- Website formsForms that email you and send each lead where you work.
- WidgetsCookie banner, age check, chat button, bar and popup.
- Website analyticsVisitor stats without cookies, and taps to call.
- Tracking codesAdd Google Analytics, Tag Manager, a Meta Pixel or Google Ads.
- Videos and embedsShow a YouTube or Vimeo video, a Calendly calendar or a Typeform.
- Custom codeAdd a chat widget or other code to your site on your own domain.
Build your first site
Start from a Google listing or a few notes. Demos usually take 5–15 minutes.
7 days for $1, then $49 a month. Cancel any time.