Four platforms. Any shop.
What each platform receives and which consent it needs, exactly as the debugger shows it.
Platforms
Connect each one from the panel: a test event goes out before anything is saved.
Meta Conversions API
- Events
- PageView, ViewContent, Search, AddToCart, AddToWishlist, InitiateCheckout, AddPaymentInfo, Purchase, Lead, CompleteRegistration and custom events
- From
- The browser and the shop's server. A purchase goes out once, as the server copy; Meta matches it with your Pixel by event ID.
- Consent needed
- ad_storage and ad_user_data. Without ad_personalization the event is sent for measurement only. Under IAB TCF Meta also needs Google's Additional Consent for Meta.
- Refunds
- Not accepted by Meta. Shown as “refund not supported”.
- Setup
- Pixel ID and a Conversions API access token
TikTok Events API
- Events
- Pageview, ViewContent, Search, AddToCart, AddToWishlist, InitiateCheckout, AddPaymentInfo, Purchase, Lead, CompleteRegistration and custom events
- From
- The browser and the shop's server, deduplicated by event ID
- Consent needed
- ad_storage, ad_user_data and ad_personalization. With an IAB TCF banner TikTok gets no events: its Pixel and Events API are not a vendor on the IAB list.
- Refunds
- Not accepted by TikTok.
- Setup
- Pixel code and an Events API access token
GA4 Measurement Protocol
- Events
- purchase, refund and generate_lead. Page views and the rest stay with gtag in the browser, which keeps the session and traffic source.
- From
- The shop's server
- Consent needed
- analytics_storage. Hashed e-mail and phone only with ad_user_data.
- Refunds
- Sent as refund events with the transaction ID.
- Setup
- Measurement ID and an API secret
Google Ads
- Events
- Purchases as conversions of the conversion action you choose, through Google's Data Manager API
- From
- The browser and the shop's server, deduplicated by transaction ID
- Consent needed
- ad_storage and ad_user_data; under IAB TCF also consent for Google (vendor 755). Without ad_personalization the conversion is marked accordingly.
- Refunds
- The conversion value is lowered to what is left after the refund. The conversion itself stays.
- Setup
- Sign in with Google, pick the Ads account and the conversion action
Shop platforms
Install once. Orders are reported from your shop's backend from then on.
WooCommerce
- How
- A WordPress plugin. Pair it with a key from the panel; it adds the script from your own subdomain and reports paid orders and refunds from the server.
- Requires
- WordPress 6.4, WooCommerce 8.0 and PHP 7.4 or newer
- Extras
- Optional same-IP mode for longer cookie life in Safari
Shoper
- How
- An app from the Shoper App Store. It adds the script from your own subdomain once that subdomain is live, and reports paid orders from Shoper's webhook.
- Status
- Not in the Shoper App Store yet. Write to hello@tallyhost.io and we will tell you when it is.
- Consent
- Taken from the purchase the script sends on the thank-you page. If that page never loads within 30 minutes, the order is counted in the debugger but not sent to the platforms.
- Not yet
- Refunds: Shoper does not offer them to apps through a webhook.
InPost Pay
- What
- Orders a shopper places and pays in the InPost app. InPost's server creates them in your shop, so the browser's consent and ad click never reach the order on their own.
- WooCommerce
- The TallyHost plugin takes the shopper's consent from their browser when the cart is linked to the InPost app and on InPost's thank-you page, and reports the order from your server once it is paid.
- Shops without our plugin or app
- Connect InPost Pay in the panel with your shop's InPost API keys. We only read orders and transactions. InPost's documentation says not to share these keys with third parties, and InPost may block a shop's account for it, which would turn off InPost Pay in the shop, not only the conversions. The panel asks you to confirm that you accept this before it saves the keys.
- Consent
- Without proof of the shopper's consent the order is counted in the debugger but not sent. InPost's thank-you page shows before payment, so a browser purchase from InPost's standard thank-you page is not sent.
- Plans
- Every plan, at no extra charge.
- Status
- Preview. The test on InPost's sandbox is still ahead.
Other platforms
- How
- Point a subdomain of your shop at TallyHost with a few DNS records (A, AAAA and a TXT check), then paste the script from it into your pages. For purchases from your server, generate an Ed25519 key and send us the public key; we register it and return the key ID. Browser events work without it.
- Your platform
- Want a plugin for it? Write to hello@tallyhost.io.
Provider and platform names belong to their owners.
Connect your first platform
The panel sends a test event before it saves anything.