We currently use gtag.js on the frontend and report conversions through the API Measurement Protocol. This setup works well for us in terms of conversion attribution, as conversions are correctly attributed.

We currently use gtag.js on the frontend and report conversions through the API Measurement Protocol. This setup works well for us in terms of conversion attribution, as conversions are correctly attributed.

We currently use gtag.js on the frontend and report conversions through the API Measurement Protocol. This setup works well for us in terms of conversion attribution, as conversions are correctly attributed.

We currently use gtag.js on the frontend and report conversions through the API Measurement Protocol. This setup works well for us in terms of conversion attribution, as conversions are correctly attributed.

We currently use gtag.js on the frontend and report conversions through the API Measurement Protocol. This setup works well for us in terms of conversion attribution, as conversions are correctly attributed.

We currently use gtag.js on the frontend and report conversions through the API Measurement Protocol. This setup works well for us in terms of conversion attribution, as conversions are correctly attributed.

We currently use gtag.js on the frontend and report conversions through the API Measurement Protocol. This setup works well for us in terms of conversion attribution, as conversions are correctly attributed.

We currently use gtag.js on the frontend and report conversions through the API Measurement Protocol. This setup works well for us in terms of conversion attribution, as conversions are correctly attributed.

We currently use gtag.js on the frontend and report conversions through the API Measurement Protocol. This setup works well for us in terms of conversion attribution, as conversions are correctly attributed.