Your website. Meet your flyer campaign.

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.

1. 1

   Prepare your pixel

   Get your organization's pixel configuration from the app. Decide which supported website actions you want to report.

   Pixel id

   Public. Starts with px_.

   Container access

   You need permission to add tags and publish.

2. 2

   Add the loader as a Custom HTML tag

   Create a Custom HTML tag in your container and paste your pixel block into it. Set it to fire on all pages, and configure its consent behavior for your website.

   <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>

3. 3

   Add a second tag for your conversion

   Create another Custom HTML tag that calls track, and attach it to the trigger you already use for a thank-you page or a form submit. Replace the illustrative amount with your own value.

   <script>
     turf('track', 'Booking', {
       value: 149.00,
       currency: 'CAD'
     });
   </script>

4. 4

   Preview before publishing

   Use your container's preview workflow to verify the script and supported events. Publish only after checking the data and campaign context.

   • 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

How website attribution works