Integrations

Connect your funnel, end to end

Quarkad watches the full conversion path. Connect your sources and it lines up every change — across ads, landing pages, forms, and CRM — against the moment conversions move.

Installs anywhere

Website and form tracking is a single script tag, so it works on any platform where you can edit the page head. Quarkad gives you paste-in instructions for:

WordPressGoogle Tag ManagerShopifyCustom HTML

Why a single connection is never enough

Conversion drops are hard to diagnose for a structural reason: the cause and the symptom almost never live in the same tool. The symptom shows up at the end of the funnel, in lead count or conversion rate. The cause usually sits upstream, in a campaign edit, a page deploy, a changed form field, or a CRM integration that started rejecting records. Each of those lives in a different system, owned by a different person, with its own history that nobody thinks to check.

Connecting one source tells you a number moved. Connecting the path tells you what moved just before it. That is the whole design principle here: Quarkad is not trying to replace your ad platform, your analytics, or your CRM. It is trying to hold their change histories on one timeline so the question of what changed has an answer.

What each connection adds

  • Ad platforms. Meta Ads and Google Ads supply the change record for budget, status, and targeting, so a drop that followed a campaign edit is visible as exactly that rather than as a mystery.
  • Landing pages and forms. The page snippet supplies the funnel events and detects page edits; form monitoring turns raw lead counts into a submit rate, which is the only number that separates a traffic problem from a form problem.
  • CRM. HubSpot closes the last gap, where a form submits successfully and the record never arrives. Without it, a handoff failure is indistinguishable from a marketing problem.
  • Delivery. Slack alerts decide whether anyone acts on an incident within the hour or reads about it in next week’s report.

Frequently asked questions

What is the minimum I need to connect to get value?
The landing page snippet on its own is enough to start, because it gives Quarkad the funnel events it needs: visits, form views, and submits. Adding an ad platform tells you whether a drop followed a campaign change, and adding a CRM tells you whether submitted leads actually arrived. Each connection removes one category of cause you would otherwise have to check by hand.
Which permissions does Quarkad ask for on ad accounts?
Read access. Quarkad reads campaign, ad set, and budget state so it can record what changed and when. It does not create, pause, edit, or spend anything in your ad accounts.
Do I need a separate connection per client?
Yes, and that is deliberate. Each client sits in its own workspace with its own connected sources, so data never mixes across accounts and access can be granted per client rather than per agency.
Where does the snippet go and does it slow the page down?
It is a single script tag in the page head, so anywhere you can edit the head will work, including a tag manager. It loads asynchronously and does not block rendering.
What happens if a connection breaks?
That is itself something Quarkad watches. A connection health monitor raises an incident when a source stops reporting, because a silent integration failure looks exactly like a conversion drop on every dashboard downstream of it, and it is the one failure that would otherwise make the monitoring itself untrustworthy.

Related reading

One snippet, a couple of OAuth clicks, done.

Connect your sources and let Quarkad correlate changes against conversion drops for you.