POAS Tracking Connector

In this guide, you will learn how to set up the POAS Tracking Connector, so your conversion tags report the profit of an order instead of its revenue.

The POAS Tracking Connector reads a product feed that contains cost price and regular price per product. When a purchase event reaches your server container, the tool looks up every item in the order, calculates the margin and returns the profit for that order as a single variable. You can then use that variable as the conversion value in Google Ads, Meta and, optionally, GA4.

Because the lookup happens entirely in the server container, cost prices and margins never reach the browser. The main practical difference with a client-side setup is that your margin data stays in your own infrastructure, while the ad platforms still receive a value they can bid on.

If you already maintain a product feed in Channable or a comparable feed tool, this is the fastest route to profit-based measurement. It reuses the feed you have, instead of requiring a separate database.
Prerequisites
  • A TAGGRS account with a configured server container.
  • A feed tool such as Channable, with your shop system as the source.
  • Cost price filled in per product in your shop system.
  • A purchase event that reaches the server container, including item data.
  • Google Ads and/or Meta conversion tags configured in the server container.
Consent Approval Graph misst die tatsächlichen Zustimmungssignale, die über Ihren Tracking-Stack übertragen werden. Anstatt sich auf Banner-Interaktionen zu konzentrieren, analysiert es
  • Connect your shop system (for example Shopify, WooCommerce or Magento) as the source in Channable or another feed tool.
  • Check that every product has a cost price filled in at the source.
Das bedeutet, dass Sie Folgendes sehen können:
Add at least these fields:
  • Der Prozentsatz des Traffics, der vollständig, teilweise gewährt oder verweigert wurde
  • Der Prozentsatz des Verkehrs, bei dem keine Zustimmungsentscheidung getroffen wurde
  • Wie sich die Einwilligung auf das Conversion-Tracking auswirkt.
Es bietet Einblicke auf Veranstaltungsebene darüber, wie sich Zustimmungsstatus auf die Übertragung von Werbe- und Analyseereignissen auswirken, und hilft Ihnen zu verstehen, wie sich dies auf Messung und Zuordnung auswirken kann.
  • Use the price excluding VAT and shipping costs.
Anstatt zu raten, erhalten Sie messbare Beweise.
The feed and the events sent to the advertising channels must speak about products in the same way.
  • Check which ID is used in the advertising channels.
  • In this example, the shopping feed works with a numeric ID, with SKU as the secondary identifier.
  • Make sure the Channable or other feed tool uses the same ID as Google Ads/Analytics.
Shopify exposes several identifiers (product ID, variant ID, SKU), and shopping feeds often use a different one than the data layer. Decide which identifier is leading, then align the feed to it.
  • Open the JSON feed and check that the fields are populated.
  • Pay particular attention to the product ID, price and cost fields.
Open the feed URL directly in your browser and inspect a handful of products, including a variant product and a discounted product. An empty or null cost price at this stage will surface later as a profit of 0 in your conversions.
  • Go to Integrations in TAGGRS and open Profit Tracking (POAS).
  • Feed URL: paste the URL of your public JSON product feed. TAGGRS saves it and resyncs the feed daily.
  • Once the feed is fetched, select the right keys from the dropdowns. You don't have to type field names.
  • Product ID field: the field in each feed item that matches the item_id in your GA4 events. Select your currency next to it.
  • Price field: the selling price excluding VAT and shipping costs. On a purchase, this value is replaced by the price from your GA4 event, so that price must also exclude VAT and shipping costs, with discounts already applied.
  • Cost fields: the fields that are subtracted from the price, such as cost price or handling costs. Click Add cost field to add more, up to 10. Don't add VAT here.
  • If TAGGRS can't fetch your feed, the dropdowns change into regular text fields. Type the exact key names from your feed instead.
  • Save the integration. TAGGRS generates a password automatically, which you can view after saving.
  • You will need this password later in Tag Manager.
The feed URL itself stays public, because TAGGRS needs to read it. The password protects the profit calculation in the TAGGRS backend, so only your server container can request it. You need this password when you configure the variable in step 7.
Create a new variable in the server container:
  • Name: for example, profit feed margin.
  • Product ID field: TAGGRS container identifier.
  • API secret field: the auto-generated password from step 5.
  • Event names field: all ecom events you want to use the variable on.
  • Ecommerce data fields: contains all ecom data, such as items, currency, transaction id and total order value.
Note: The ecommerce data fields can be left empty. The variable is designed to automatically pick up this data as long as the default GA4 datalayer structure is used.
  • Check in preview/debug which item_id is being sent.
  • Make sure this matches the ID in the profit feed.
  • Check that the item price in the event excludes VAT and shipping costs, with discounts applied.
Run a test purchase in preview mode and compare the item_id in the incoming event with the product ID in the feed, character for character.

A mismatch will return no margin, which is harder to spot than a broken tag.
  • The output of the variable is the profit per order.
  • Use that value in Google Ads conversions, Meta and, optionally, in GA4.
Set the variable as the conversion value parameter in the tags concerned. From that point on, the value the platform optimizes towards is margin, not turnover.
Open the feed integration in TAGGRS to check its configuration status.

Here, you can see:
  • Whether the feed is configured.
  • How many products have been synced.
  • When the integration settings were last updated.
If the product count is lower than expected, the feed or mapping need your attention.
DOCUMENTATION V1.5
Copyright © 2026 TAGGRS. All right reserved.