Salla app troubleshooting

Issue: If another app or your existing GTM setup is already sending ecommerce events, the Salla app may use identical event names. This can cause Web GTM tags to fire twice for a single action, resulting in inflated data reporting.

Solution: To resolve this, navigate to the Salla app's Data Layer tab and enable the Decorate dataLayer event name option. This will append _stape to Salla event names. You can then update your Stape tags and triggers to reference these unique names.

Issue: You have enabled Custom Loader or Cookie Keeper in the Salla app settings, but the features aren’t functioning correctly.

Solution: Simply enabling Custom Loader or Cookie Keeper within the app settings isn’t sufficient on its own. To ensure these features function correctly, first enable the corresponding power-up within your Stape container, and then activate it in the app settings.

Cookie Keeper and Custom Loader work only when the server container is hosted on Stape. Cookie Keeper also needs a paid Stape plan.

Issue: You’re noticing that tracking data fails to match across platforms like Google Ads or Merchant Center, despite the Salla app being configured.

Solution: The app generates the items array directly from your Salla product catalog. If your external platforms (such as Google Ads or Merchant Center) use different product identifiers, the tracking data can’t be synchronized. To resolve this, use the following method:

Create a Custom JavaScript Variable in Web GTM or a variable / transformation in sGTM to construct your required catalog format (for example, prefixing salla_ or using item_sku instead of item_id in your Google Ads / GA4 tags).