ARBook a Demo
Developer documentation

KePixel for Salla

Install the source-specific Web GTM container shown in KePixel Setup. KePixel's managed Salla container reads supported Salla storefront signals and handles the downstream server connection for this source.

1 · Create / open Salla source
↓
2 · Copy Web GTM Container ID
↓
3 · Add it in Salla tracking / GTM settings
↓
4 · Trigger store events + verify

Implementation flow

Open the exact Salla source

Go to KePixel → Sources → your Salla store → Setup.

Wait for the managed container

When provisioning is complete, Setup exposes the source-specific Web GTM Container ID. If it still says Waiting, use Overview → Refresh source status.

Add the ID to Salla

Open the Salla store's tracking / Google Tag Manager settings, paste the exact container ID from KePixel, and save the storefront configuration.

Do not recreate the KePixel event map

The managed container contains KePixel's Salla event normalizer and source configuration. Do not add duplicate KePixel event tags unless the source Setup page specifically asks for a missing site-specific signal.

Verify real store actions

Test page/product/cart/checkout actions, then refresh the source status in KePixel.

KePixel → Sources → your Salla store → Setup

What appears in Setup

Web GTM Container ID

Copy the exact GTM-... ID shown for this Salla source. KePixel manages the Web container contents and downstream Server GTM/runtime connection.

Developer boundary

You do not need KePixel Server GTM credentials, destination tokens, a Server Tagging URL, template files, or a custom relay URL. The Salla customer-side handoff is the Web GTM container ID shown by KePixel.

Install in Salla

  1. Copy the Web GTM Container ID from KePixel Source Setup.
  2. Open the correct Salla store admin.
  3. Open the store tracking / Google Tag Manager configuration available for that storefront.
  4. Paste the exact ID and save.
  5. Publish/apply the storefront change using Salla's normal controls.
  6. Return to KePixel and refresh source status.

Never reuse another store's container

Each KePixel source is tenant/site scoped. A container from another source may carry different source IDs, runtime routing or attribution context.

Managed Salla event coverage

JourneyExamples normalized by the managed Salla container
Browsingpage_view, search, view_item_list, select_item, view_item
Cartview_cart, add_to_cart, remove_from_cart
Checkoutbegin_checkout, add_shipping_info, add_payment_info
Outcome / accountpurchase, login, sign_up

The container maps supported Salla/dataLayer aliases to canonical KePixel names. Exact coverage still depends on the signals the storefront actually exposes.

Purchase quality

Browser completion is not automatically proof of payment

A browser-side Salla order/checkout completion can be a purchase candidate, but confirmed revenue must preserve stable transaction evidence and should be reconciled with a verified order/payment source when available. Do not create a second unrelated transaction ID for the same order.

For a high-quality purchase signal keep accurate transaction ID, currency, value and product items. Do not infer purchase from a generic thank-you page or button click alone.

Attribution and consent

The managed Salla Web container can preserve approved campaign context such as UTM and recognized ad click IDs when they actually exist. It must not fabricate them. Advertising identifiers remain consent/policy controlled; do not add credentials or customer secrets to Salla browser configuration.

Testing checklist

  1. Confirm the exact KePixel Salla Web GTM ID is installed on the intended store.
  2. Open a storefront page and verify GTM loads.
  3. View a product and add it to cart.
  4. Enter checkout and inspect the actual event path.
  5. If testing purchase, use a real/safe test order and verify transaction/value/currency/items.
  6. Return to KePixel → Overview → Refresh source status.