Your website. Meet your flyer campaign.
The universal pixel, added with one script block on any site where you can edit the page head.
| 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 |
Set it up with your campaign in mind.
A pixel installation is the starting point. Event configuration, consent, and campaign attribution context determine what you can measure.
Prepare your pixel
Get the pixel configuration for your organization from the app. Confirm your plan includes the pixel, and decide which website events matter to your campaign.
- Pixel id
- Public. Starts with px_.
- Secret key
- Not needed for the snippet. Keep it on your server.
Install it on your site
Add the script block to the head of the pages you want to measure. Copy the exact block from the app, which fills in your script URL and pixel id. The placeholders here show the shape.
HTML, in the page head <script> !function(w,d,s,u){ if(w.turf)return; var t=function(){t.queue.push(arguments)}; t.queue=[];t.loaded=false;w.turf=t; var js=d.createElement(s);js.async=true;js.src=u; var f=d.getElementsByTagName(s)[0];f.parentNode.insertBefore(js,f); }(window,document,"script","YOUR_PIXEL_SCRIPT_URL"); turf('init', 'YOUR_PIXEL_ID'); </script>Report your conversion
Configure lead, booking or purchase events around the actions your site actually performs. Call track at the moment your site confirms the action. The amount shown is illustrative.
- Events
- ScanLanding, PageView, Lead, Booking, Purchase, Call
- Currency
- Defaults to CAD when left out
JavaScript, on your confirmation step turf('track', 'Booking', { value: 149.00, currency: 'CAD' });Check the whole journey
Test a campaign QR link through to your destination and a supported event. Verify attribution before relying on the campaign report.
- Scan a campaign code. The landing address should contain turf_scan and qr.
- Look for a first-party cookie named _turf_scan on your domain.
- Trigger your event. The request to the track endpoint should return 200.
- Read the response. attributed_to should say scan.
- Find the event on the campaign in the app before you rely on the report.
A little more detail
Does this track every customer?
No. Supported events must be configured, and attribution depends on campaign context, browser behavior, consent, and the customer journey.
Do I need to rebuild my website?
No. Keep your existing destination and checkout. Your ability to install scripts and report events depends on your platform and access.
Where can I learn how attribution works?
The Website attribution page explains how the QR redirect, pixel, and server-side conversion reporting fit together.
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