Keep your tools. Connect your fieldwork.
Your website already has a job to do. Connect it to your flyer campaigns with the universal pixel or Google Tag Manager, and explore what’s next on the connector roadmap.
- Works today with a snippet or Google Tag Manager
- Native connectors on the roadmap
- A way to request the one you need
Partly available. Native connectors are not available yet. The snippet works on any site that accepts a script.
| JS snippet, any site | Available |
|---|---|
| Google Tag Manager | Available |
| Shopify | Coming soon |
| WordPress | Coming soon |
| Squarespace | Coming soon |
| Calendly | Coming soon |
| Square Appointments | Coming soon |
| Stripe | Coming soon |
Find your connection. See what is real.
Two setup paths work on any site today. Native connectors are on the roadmap, and each has its own page that says so.
- Available
- 2
- Coming soon
- 6
- Categories
- 4
| Integration | Status | Category | Typical event | What it is | Page |
|---|---|---|---|---|---|
| JS snippet / any site | Available | Tag managers | Purchase | The universal pixel, added with one script block on any site where you can edit the page head. | Guide |
| Google Tag Manager | Available | Tag managers | Purchase | The same pixel, deployed as a Custom HTML tag in a container you already run. | Guide |
| Shopify | Coming soon | E-commerce | Purchase | A planned app that reports a Purchase when a checkout completes. | Details |
| WordPress | Coming soon | E-commerce | Lead | A planned plugin for WordPress and WooCommerce that reports leads and orders. | Details |
| Squarespace | Coming soon | E-commerce | Purchase | A planned setup path for measuring flyer-driven visits on a Squarespace site. | Details |
| Calendly | Coming soon | Booking | Booking | A planned connector that reports a Booking when a flyer scan becomes a scheduled appointment. | Details |
| Square Appointments | Coming soon | Booking | Booking | A planned connector that reports confirmed appointments from your booking calendar. | Details |
| Stripe | Coming soon | Payments | Purchase | A planned connector that reports Purchase events server-side from payment webhooks. | Details |
Showing 8 of 8. Coming soon means not built yet. None of those are one-click installs today.
Which path fits your site?
| If this is true | Use | Status | Link |
|---|---|---|---|
| You can edit your site's page head | JS snippet | Available | How |
| Your site already runs a Google Tag Manager container | Google Tag Manager | Available | How |
| Bookings or payments are confirmed on your own backend | Server-side conversion call | Available | How |
| Your platform does not let you add a script | A native connector | Coming soon | Join early access |
The two paths that work today.
They end in the same place. The difference is who touches the site and where the code lives.
| Aspect | JS snippet | Google Tag Manager |
|---|---|---|
| Best when | You or a developer can edit the site's HTML | Tags on your site are already managed in a container |
| Where the code goes | A script block in the head of each page | A Custom HTML tag that fires on all pages |
| Conversion events | A track call in your confirmation step | A second tag on your existing conversion trigger |
| Before going live | Scan a test code and watch the event arrive | Use the container's preview, then publish |
| Consent | Load the script after your own consent check | Use the container's consent settings on the tag |
| What you need | Pixel id, and a plan that includes the pixel | Pixel id, a plan that includes the pixel, publish rights |
- Same pixel underneath
- Both paths load the same script and call the same turf function.
- Six standard events
- ScanLanding, PageView, Lead, Booking, Purchase and Call.
- First-party storage
- The scan token is kept in a cookie on your own domain for 365 days.
- Your site stays yours
- Keep your existing destination and checkout. Nothing is rebuilt.
A little more detail.
Do I need a native connector?
Not necessarily. The universal pixel can be used on a site where you can install the script, either directly or through Google Tag Manager. Event setup still needs to match the actions you want to measure.
Are all these integrations available now?
No. The universal script and Google Tag Manager are listed as available. Native connectors are clearly marked coming soon. They should not be treated as live one-click installations.
Can I send events from my backend?
The conversion API supports server-side reporting. See the website attribution page for how campaign context and conversions fit together.
Will a connector track every customer?
No. Supported events must be configured, and attribution depends on campaign context, browser behavior, consent and the customer journey.
Keep the website you already have.
Join the beta with a snippet today, and tell us which connector you need next.
- Join the list
- Get your invite by email
- Walk your first street